Open
Conversation
Bumping CCCL version to use latest changes in rapidsmpf
Contributor
|
We only adopt CCCL release branches, not |
Contributor
We have been pinned to commits from |
bdice
approved these changes
Apr 17, 2026
Contributor
|
I'd like to wait to merge this until we land the RMM CCCL memory resource migration (starting merges tomorrow). That will come with a number of build breaking changes that are disruptive on their own. We can merge this after that migration settles. |
Contributor
Author
|
@bdice I think so. |
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.
Description
This PR updates CCCL to the latest 3.4.0 pre-release commit.
Comparison of CCCL commits: NVIDIA/cccl@c5594eb...2685474
We specifically need these features/fixes for RAPIDS projects:
constexprportability issue in__basic_anyNVIDIA/cccl#8353Checklist
cmake-format.jsonis up to date with these changes.include_guard(GLOBAL))