-
Notifications
You must be signed in to change notification settings - Fork 554
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
Mark all kernels with internal linkage #5764
Mark all kernels with internal linkage #5764
Conversation
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.
Is there a reason you decided not to add a macro like CUDF_KERNEL
here?
No, will revise to use a common macro |
5f730c2
to
53d3d0b
Compare
53d3d0b
to
c33e56b
Compare
Co-authored-by: Bradley Dice <bdice@bradleydice.com>
This should be good to go once the documentation fix finishes running CI and we get an ops approval. I'll pre-emptively merge this. |
/merge |
Downstream consumers of static built versions of RAPIDS C++ projects have encountered runtime issues due to multiple instances of the same kernel existing in different DSOs.
To resolve this issue we need to ensure that all CUDA kernels in all RAPIDS libraries need to be have internal linkage ( static for projects using whole compilation, attribute((visibility("hidden"))) for header libraries / separable compilation ).
This updates all cuml kernels to have internal linkage, and adds a CI job to verify that no new kernels are added with external linkage.