cuda.compute: Fix struct comparison (ordering matters)#7451
Merged
shwina merged 1 commit intoNVIDIA:mainfrom Feb 2, 2026
Merged
cuda.compute: Fix struct comparison (ordering matters)#7451shwina merged 1 commit intoNVIDIA:mainfrom
shwina merged 1 commit intoNVIDIA:mainfrom
Conversation
NaderAlAwar
approved these changes
Feb 2, 2026
oleksandr-pavlyk
approved these changes
Feb 2, 2026
Contributor
🥳 CI Workflow Results🟩 Finished in 1h 19m: Pass: 100%/56 | Total: 18h 23m | Max: 55m 21sSee results here. |
fbusato
pushed a commit
to fbusato/cccl
that referenced
this pull request
Feb 19, 2026
Co-authored-by: Ashwin Srinath <shwina@users.noreply.github.com>
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
3 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.
Description
Fixes a bug that leads to examples failing in CI (depending on whether two particular tests are run on the same worker).
For posterity, a reliable reproducer of the issue was:
Since these two tests create structs with the same members (but different order), and the first struct would be incorrectly retrieved from a cache during the execution of the second test.
Checklist