[ENHANCEMENT]: Make cuco code NVRTC-compatible
@0z5a is already working on this.
Since Sep 18, 2026.
- Dominant language
- Cuda
- Stars
- 667
- Forks
- 120
- Avg merge
- 7d 5h
- Merged PRs (30d)
- 4
Description
Is your feature request related to a problem? Please describe.
Related to https://github.com/NVIDIA/cccl/issues/4305
Make sure cuco is JIT or NVRTC compatible.
Describe the solution you'd like
To enable cuco code to be used in JIT kernels, we need to ensure that no thrust algorithms are used in cuco implementations. When available, we will replace the two existing uses of thrust algorithms with their cuda::std:: equivalents.
https://github.com/NVIDIA/cuCollections/blob/e3aec271627a5d482cf2c720c6e2ec6e15cae06c/include/cuco/detail/open_addressing/open_addressing_ref_impl.cuh#L1269
https://github.com/NVIDIA/cuCollections/blob/e3aec271627a5d482cf2c720c6e2ec6e15cae06c/include/cuco/detail/open_addressing/open_addressing_ref_impl.cuh#L1257
As a simpler initial task, we can start by replacing thrust utilities such as pair, tuple, and equal_to with their corresponding cuda::std:: equivalents, which are already available for use.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.