[thrust] Fix thrust::transform test for gcc-15#8691
Merged
Conversation
Contributor
bernhardmgruber
left a comment
There was a problem hiding this comment.
Can you try whether annotating the function where the GCC error happens with THRUST_DISABLE_BROKEN_GCC_VECTORIZER?
0e6b31f to
736091c
Compare
Contributor
Author
Works, thanks for the suggestion! |
bernhardmgruber
approved these changes
Apr 27, 2026
Contributor
🥳 CI Workflow Results🟩 Finished in 2h 02m: Pass: 100%/68 | Total: 2d 08h | Max: 1h 50m | Hits: 85%/134388See results here. |
shwina
pushed a commit
to shwina/cccl
that referenced
this pull request
Apr 30, 2026
Contributor
|
I am backporting this to 3.3 because of NVBug 6166900 |
Contributor
|
/backport branch/3.3.x |
Contributor
|
Successfully created backport PR for |
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
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.
According to the comment, this looks like an issue we've dealt before. I've found out that this test is problematic only when
Tissigned char, so I've just disabled this test for that type.