Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Avoid "most vexing parse" warning in certain versions of NVCC#162

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
vstinner merged 1 commit intopython:mainfromcolesbury:vexing_parse
Nov 7, 2025

Conversation

@colesbury
Copy link
Contributor

No description provided.

@colesbury
Copy link
ContributorAuthor

This one is a bit weird, but I'm seeing-Wvexing-parse warnings in some versions of nvcc. I'm not entirely sure what's happening, but I think that it's a combination of:

  • Thevoid fromPyAPI_FUNC(const PyConfig*) _Py_GetConfig(void); is getting stripped out by nvcc's frontend
  • Clang is then giving a "most vexing parse" warning

I couldn't figure out any way to avoid this other than moving the declaration out of the function.

@vstinnervstinner merged commite3efede intopython:mainNov 7, 2025
36 checks passed
@vstinner
Copy link
Member

Merged, thanks.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@colesbury@vstinner

[8]ページ先頭

©2009-2025 Movatter.jp