Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Be more selective in terms of clang version when using a flag in CUB compilation #25930

Merged
merged 2 commits into from
Sep 11, 2024

Conversation

e-kayrakli
Copy link
Contributor

@e-kayrakli e-kayrakli commented Sep 11, 2024

#25918 added -Wno-error=deprecated-builtins when compiling the runtime's CUB wrappers. However, that flag is not supported in some older clangs. Specifically, we added that to enable builds with clang 18, but clang 14 doesn't have that flag. This PR adds the problematic flag only if the clang version supports it.

Test:

  • build proceeds on a system with the same issue

@e-kayrakli
Copy link
Contributor Author

@jabraham17 -- are you OK with me proceeding with this "fix", or is it too lazy? :)

@jabraham17
Copy link
Member

I prefer checking for the clang version, which is what we do for all of the other -Wno-error flags that we have for compilation.

Signed-off-by: Engin Kayraklioglu <[email protected]>
Copy link
Member

@jabraham17 jabraham17 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, just make sure to update the PR title and message

@e-kayrakli e-kayrakli changed the title Turn an unknown flag error into a warning for CUB compilation Be more selective in terms of clang version when using a flag in CUB compilation Sep 11, 2024
@e-kayrakli e-kayrakli merged commit 958af5e into chapel-lang:main Sep 11, 2024
7 checks passed
@e-kayrakli e-kayrakli deleted the gpu-cub-unknown-flag-no-error branch September 11, 2024 23:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants