Use NVRTC for compiling kernels calling cupyx.jit.cub APIs
#7869
Conversation
This file contains 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
Merged
1 task
1 task
leofang
changed the title
cupyx.jit.cub APIscupyx.jit.cub APIs
|
/test mini |
|
/test mini |
|
@asi1024 this should be ready for review |
This was referenced Oct 5, 2023
|
/test full |
|
Did the 2 CIs fail due to glitches? |
|
Seems GCP was too crowded. Retriggered manually. |
|
All CIs are green! |
asi1024
approved these changes
Oct 11, 2023
|
LGTM! Thanks! |
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.
Blocked by #7851.Follow-up of #7851.
CUB (only block/warp) & libcudacxx headers can be compiled by NVRTC + Jitify, but not Thrust headers. So, in this PR a clean-up is done to allow CUB/libcudacxx functions compiled by NVRTC. The old workarounds to supply std libraries is no longer needed.