-
Notifications
You must be signed in to change notification settings - Fork 5
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
Suppress asserts in the GPU code, unless GPU_DEBUG is defined #186
Suppress asserts in the GPU code, unless GPU_DEBUG is defined #186
Conversation
Validation summaryReference release CMSSW_10_2_5 at a8a031d
|
#define NDEBUG | ||
#endif // NDEBUG | ||
#endif // GPU_DEBUG | ||
#endif // __CUDA_ARCH__ |
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.
Somehow it would feel nice to abstract this piece to a common place, but I'm not sure if, in the end, it would ask more trouble than it would help.
I agree.
I am worried about moving it to an include file, because we may forget to
include it, and the compiler would not tell us.
A possibility could be to use a different name for "assert", e.g.
"cuda_assert", but that might be confusing for __host__ __device__
functions.
Also, I think the order of the #include directives would matter, as we
would need to include the one defining the macro before including assert.h
/ cassert, or anything that includes it.
I'm open to suggestions !
|
OK, both on Linux and on OS X |
Validation summaryReference release CMSSW_10_2_5 at a8a031d
|
No description provided.