[Java] Make cudaGetDeviceProperties compatible with CUDA 12 and 13 based on symbol presence#1323
Merged
rapids-bot[bot] merged 1 commit intorapidsai:branch-25.10from Sep 11, 2025
Conversation
Contributor
|
/ok to test 4a680a0 |
mythrocks
approved these changes
Sep 9, 2025
Contributor
mythrocks
left a comment
There was a problem hiding this comment.
This is definitely the preferable way to address this.
cudaGetDeviceProperties compatible with CUDA 12 and 13 based on symbol presencecudaGetDeviceProperties compatible with CUDA 12 and 13 based on symbol presence
Contributor
|
/merge |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In #1273 we addressed a signature change in CUDA 13 by binding different symbols based on a environment variable,
RAPIDS_CUDA_MAJOR. That works, but forces users of cuvs-java with CUDA 12 to define this environment variable.This PR improves on it by making the symbol lookup dynamic, looking for the CUDA 13 symbol name, and falling back to the CUDA 12 exported name if we fail to locate the first.