-
Notifications
You must be signed in to change notification settings - Fork 15.2k
[InstCombine] Add test for freeze of GEP with recurrence offset (NFC) #145541
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
david-arm
merged 5 commits into
llvm:main
from
c-rhodes:instcombine-phi-gep-phi-offset-precommit-test
Jun 26, 2025
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
b32e341
[InstCombine] Add test for freeze of GEP with recurrence offset (NFC)
c-rhodes ded4097
update CHECK-LABEL
c-rhodes 2ca19f1
address comments
c-rhodes a82060e
add test for GEP that can produce poison
c-rhodes b251c12
address comments
c-rhodes 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
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.
If I understand correctly the freeze could be moved here too if we strip
inboundsfrom the gep and push the freeze up to the pointer%i? The offset%off.nextis still guaranteed not to be poison or undef I think.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.
Yes I think so.
I don't believe so,
%nneeds to be markednoundeffor that? I think this example is what you're referring to: https://godbolt.org/z/e8rGsz66W. Whereas Nikita wanted a test where the GEP can produce poison.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.
Both variants probably have value. One requires just stripping poison, the other requires freezing an additional value.
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.
ok, I've also added a test for the inbounds GEP + noundef offset variant