Properly use an if constexpr to guard segemented CUB algorithms#1067
Merged
cliffburdick merged 2 commits intoNVIDIA:mainfrom Oct 14, 2025
Merged
Properly use an if constexpr to guard segemented CUB algorithms#1067cliffburdick merged 2 commits intoNVIDIA:mainfrom
if constexpr to guard segemented CUB algorithms#1067cliffburdick merged 2 commits intoNVIDIA:mainfrom
Conversation
cliffburdick
approved these changes
Oct 13, 2025
Collaborator
|
/build |
1 similar comment
Collaborator
|
/build |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
We are currently only using a plain
ifto check whether we can use the segmented algorithms.However, this breaks, because
Data()andIsContiguous()is only defined for tensorsDrive by fix a warning about an uninitialized variable