Closed
Description
openedon Dec 8, 2023
This is a tracking issue for updates of RAPIDS to CCCL 2.2.0.
There are two phases: adding compatibility so that libraries can build with CCCL 2.2.0, and then actually doing the upgrade. I am opening separate PRs for each phase to minimize the diff that we have to keep in sync with ongoing library development.
High-Level Tasks
Some of this work is being done in parallel, following the RAPIDS dependency tree.
- Open PRs for compatibility phase.
- Test compatibility PRs locally.
- Merge compatibility PRs.
Then:
- Open PRs for version updates.
- Test version update PRs (requires use of conda artifacts from upstream PRs).
- Merge version update PRs.
Compatibility
PRs adding compatibility with CCCL 2.2.0 (e.g. by adding cuda::proclaim_return_type around device lambdas):
- rmm (not needed)
- cuCollections (Proclaim more return types for CCCL 2.2.0 compatibility. NVIDIA/cuCollections#405)
- cudf (Use cuda::proclaim_return_type on device lambdas. cudf#14577)
- raft (Use cuda::proclaim_return_type on device lambda. raft#2048)
- cugraph-ops. No changes needed, it seems.
- cugraph (Update for CCCL 2.x cugraph#3862)
- cumlprims_mg. No changes needed, it seems.
- cuml (Use cuda::proclaim_return_type on device lambdas. cuml#5696)
- cuspatial (Use cuda::proclaim_return_type on device lambdas. cuspatial#1314)
- cuopt. No changes needed, it seems.
Version Updates
PRs updating to use rapids_cpm_cccl:
- rmm (Update to CCCL 2.2.0. rmm#1404)
- cuCollections (Update to CCCL 2.2.0. NVIDIA/cuCollections#404)
- cudf (Update to CCCL 2.2.0. cudf#14576)
- raft (Update to CCCL 2.2.0. raft#2049)
- cugraph-ops (https://github.com/rapidsai/cugraph-ops/pull/580)
- cugraph (Update to CCCL 2.2.0. cugraph#4052)
- cumlprims_mg (https://github.com/rapidsai/cumlprims_mg/pull/162)
- cuml (Update to CCCL 2.2.0. cuml#5702)
- cuspatial (Update to CCCL 2.2.0. cuspatial#1315)
- cuopt (https://github.com/rapidsai/cuopt/pull/1597)
Activity