-
Notifications
You must be signed in to change notification settings - Fork 13.6k
[GlobalISel][AMDGPU] Fix handling of v2i128 type for AND, OR, XOR #138574
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+844
−6
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
af2fdcc
[GlobalISel][AMDGPU] Fix handling of v2i128 type for AND, OR, XOR
chinmaydd ca16db8
[GlobalISel][AMDGPU] Fix formatting
chinmaydd 4027444
[GlobalISel][AMDGPU] Address comments
chinmaydd 475de1d
[GlobalISel][AMDGPU] Update tests
chinmaydd 73137e3
[GlobalISel][AMDGPU] Update tests
chinmaydd File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see why this was wrong. Why was the rule wrong? Is this just papering over a bug in LegalizerHelper
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I dont believe so.
A
2xi128
vector is wider than 64 bits which satisfies the predicate here. Once thefewerElements
action is chosen, the mutation at fewerEltsToSize64Vector chooses a vector of type0xs128
to break it down. This eventually causes an FPE in LegalizerHelper::getNarrowTypeBreakdown.I think
fewerEltsToSize64Vector
was not written with vectors of element types wider than 64 bits in mind.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@arsenm sorry for the ping. Thoughts ?