-
Notifications
You must be signed in to change notification settings - Fork 267
Closed
Labels
cubFor all items related to CUBFor all items related to CUBfeature requestNew feature or request.New feature or request.good first issueGood for newcomers.Good for newcomers.help wantedRequest for input or help from the communityRequest for input or help from the communitylibcu++For all items related to libcu++For all items related to libcu++thrustFor all items related to Thrust.For all items related to Thrust.
Description
Is this a duplicate?
- I confirmed there appear to be no duplicate issues for this request and that I agree to the Code of Conduct
Area
General CCCL
Is your feature request related to a problem? Please describe.
With cub, thrust and libcu++ being three different libraries we have a ton of duplicated code.
We want to incrementally move that code into common headers, so that we do not need to repeat it and also only have one pace to fix if changes need to be made
One glaring occurrence of that duplication is the way we determine which host / device compiler is used.
With the #531 we are getting a unified config that we can use in all libraries and also convenient definitions for
_CCCL_COMPILER_{GCC, CLANG, MSVC, NVHPC, NVRTC}
Describe the solution you'd like
We should clean up all existing uses of
_LIBCUDACXX_COMPILER_{GCC, CLANG, MSVC, NVHPC, NVRTC}
THRUST_HOST_COMPILER_{GCC, CLANG, MSVC, INTEL}
CUB_HOST_COMPILER_{GCC, CLANG, MSVC, INTEL}
Describe alternatives you've considered
No response
Additional context
No response
gevtushenko
Metadata
Metadata
Assignees
Labels
cubFor all items related to CUBFor all items related to CUBfeature requestNew feature or request.New feature or request.good first issueGood for newcomers.Good for newcomers.help wantedRequest for input or help from the communityRequest for input or help from the communitylibcu++For all items related to libcu++For all items related to libcu++thrustFor all items related to Thrust.For all items related to Thrust.
Type
Projects
Status
Done