-
Notifications
You must be signed in to change notification settings - Fork 75
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
Pass alpaka_ENABLE_WERROR
from environment to CMake
#2107
Conversation
The change looks good. But no test job passed. I believe there is a lot to do 😬 |
57a8dbe
to
17256ac
Compare
17256ac
to
45a7f7c
Compare
45a7f7c
to
77a279c
Compare
77a279c
to
01d980b
Compare
@@ -10,7 +10,6 @@ if(alpaka_ACC_GPU_CUDA_ENABLE AND (CMAKE_CUDA_COMPILER_ID STREQUAL "NVIDIA")) | |||
if(alpaka_ENABLE_WERROR) | |||
list(APPEND alpaka_DEV_COMPILE_OPTIONS "$<$<COMPILE_LANGUAGE:CUDA>:SHELL:--Wreorder>") | |||
list(APPEND alpaka_DEV_COMPILE_OPTIONS "$<$<COMPILE_LANGUAGE:CUDA>:SHELL:--Wdefault-stream-launch>") | |||
list(APPEND alpaka_DEV_COMPILE_OPTIONS "$<$<COMPILE_LANGUAGE:CUDA>:SHELL:--Wmissing-launch-bounds>") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed this warning since it warns about an optional CUDA feature (enforcing a compile-time grid / block size) we do not make use of.
01d980b
to
3cbb037
Compare
3cbb037
to
5d29547
Compare
Since so many warnings occur in the code generated by nvcc, I wonder why we need to enable |
The changeset of this PR is also included in #2163. If that PR gets merged, this PR becomes obsolete. |
Superseded by #2163. |
In #1977 I forgot to ensure that
alpaka_ENABLE_WERROR
is also passed to CMake in the generation step. This PR fixes this oversight.