-
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
Update to CCCL 2.7.0-rc2. #17233
Merged
Merged
Update to CCCL 2.7.0-rc2. #17233
Changes from 6 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
3b1d74d
Two of the patches that we need for thrust cannot be applied CCCL 2.6…
miscco 39e1655
Build with CCCL 2.7.0-rc2.
bdice f6d6441
Merge remote-tracking branch 'upstream/branch-24.12' into cccl-2.7.0-rc2
bdice e231fa3
Merge branch 'adopt_cccl_patches_2_6' into cccl-2.7.0-rc2
bdice 732040f
Drop cccl_symbol_visibility patch.
bdice ce7e991
Remove patch for 64-bit dispatching.
bdice f3b6a49
Revert "Remove patch for 64-bit dispatching."
bdice 7a9c04a
Merge branch 'branch-24.12' into cccl-2.7.0-rc2
bdice 53e93c4
Merge branch 'branch-25.02' into cccl-2.7.0-rc2
bdice e6c98b1
Merge remote-tracking branch 'upstream/branch-25.02' into cccl-2.7.0-rc2
bdice 650ab50
Revert testing changes.
bdice File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file was deleted.
Oops, something went wrong.
25 changes: 0 additions & 25 deletions
25
cpp/cmake/thirdparty/patches/thrust_disable_64bit_dispatching.diff
This file was deleted.
Oops, something went wrong.
This file contains 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
This file contains 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
Oops, something went wrong.
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.
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.
@robertmaynard I'd appreciate your eyes on this. There was an upstream change in CCCL in NVIDIA/cccl#2310 that made it possible to force CCCL to only compile kernels with 32-bit offsets when
THRUST_DISPATCH_TYPE
is set to"Force32bit"
. However, I do not know how to forward this argument throughrapids_cpm_cccl
. If I were usingrapids_cpm_find
I think I could useOPTIONS
. What's the best approach?Secondly, I am wondering if CCCL should be using
FORCE
here: https://github.com/NVIDIA/cccl/blob/264b587d0621ee2c6bec27aa015078056cb5f021/thrust/CMakeLists.txt#L38Does that override my ability to set the variable ahead of time, or not since it's marked as
CACHE
?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.
Yes the
FORCE
means that we can't overwrite as each time CMake is invoked the value will be reset toForce32bit
.As for passing this down from
rapids_cpm_cccl
you would dorapids_cpm_cccl(CPM_ARGS OPTIONS "THRUST_DISPATCH_TYPE Force32bit")
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.
NVIDIA/cccl#2844 exposed the dispatch mode in
thrust_create_target
but I don't see how we are calling that in rapids-cmake. For now I am going to try and move forward with2.7.0-rc2
as-is rather than trying to backport this with a patch. We can adopt that dispatch option in a later CCCL update.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.
Reverted ce7e991 for now.