-
Notifications
You must be signed in to change notification settings - Fork 915
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
Fix nvcc-imposed UB in constexpr
functions
#17534
Fix nvcc-imposed UB in constexpr
functions
#17534
Conversation
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
/ok to test |
…vuule/cudf into remove-constexpr-with-cudf_fail
/ok to test |
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.
Wow, that is some unexpected weirdness.
Perhaps this is related to #7795 |
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 also suspect #7795 and mentioned that on Slack :)
There's definitely some overlap with #7795, but, AFAIK, that issue is related to device functions that include a throw. |
constexpr
functions
/merge |
ba3ed57
into
rapidsai:branch-25.02
Description
nvcc does not support
constexpr
functions that are not well-defined to call from the device. This is UB even when the function is not called from the device.Throwing an exception is one such operation. This PR cleans up error handling for functions that are called from device, and removes
constexpr
from the ones that are not actually used from the device, or in the constexpr context.Checklist