Skip to content
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

Draft
wants to merge 6 commits into
base: branch-24.12
Choose a base branch
from
Draft

Conversation

bdice
Copy link
Contributor

@bdice bdice commented Nov 1, 2024

This PR updates to CCCL 2.7.0-rc2. Do not merge until all of RAPIDS is ready to update.

Part of rapidsai/build-planning#115.

miscco and others added 2 commits August 27, 2024 14:18
… due to code changes in thrust.

This adopts those patches to apply with CCCL 2.6.

Should only be merged when updating the CCCL version
@bdice bdice added non-breaking Non-breaking change improvement Improvement / enhancement to an existing function labels Nov 1, 2024
@github-actions github-actions bot added the CMake CMake build issue label Nov 1, 2024
@github-actions github-actions bot added the libcudf Affects libcudf (C++/CUDA) code. label Nov 13, 2024
Comment on lines +37 to +39
# TODO: Does this work correctly? Is there a better way to set this? Should
# CCCL be setting THRUST_DISPATCH_TYPE with "FORCE"?
set(THRUST_DISPATCH_TYPE "Force32bit" STRING "Thrust offset type dispatch")
Copy link
Contributor Author

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 through rapids_cpm_cccl. If I were using rapids_cpm_find I think I could use OPTIONS. 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#L38
Does that override my ability to set the variable ahead of time, or not since it's marked as CACHE?

Copy link
Contributor

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 to Force32bit.

As for passing this down from rapids_cpm_cccl you would do rapids_cpm_cccl(CPM_ARGS OPTIONS "THRUST_DISPATCH_TYPE Force32bit")

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CMake CMake build issue improvement Improvement / enhancement to an existing function libcudf Affects libcudf (C++/CUDA) code. non-breaking Non-breaking change
Projects
Status: In Progress
Development

Successfully merging this pull request may close these issues.

3 participants