-
Notifications
You must be signed in to change notification settings - Fork 14.3k
[LAA] Use computeConstantDifference() #103725
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
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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.
Off topic - but this is essentially simplifying a three way compare. We've recently added three way compares to IR, and we've got analogous simplification logic inside SCEV for min/max. Should we maybe have an interface on SCEV which does the 3 way compare, and returns either the result or a SCEVCouldNotCompute?
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.
Off topic, but in a slightly different way... It looks like the sole user of this is addPointer. I can't see any reason that the Min and Max can't simply be the SCEV expressions for the min and max of all pointers. We'd need to cost whether generating such a group is profitable, but that's distinct from legality. One concern is that I think the current logic is relying on the min/max simplification to fail when two pointers are based on different underlying objects. We'd need to explicitly handle that. There may also be a profitability concern about forming "too large" a group if the offsets are runtime values with non-overlapping ranges.
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 think taking a normal SCEV min/max would be fine in terms of correctness, but as you say, profitability is less clear. I also suspect that the logic used here may be stronger than what SCEV does for this particular case. SCEV only uses isKnownViaNonRecursiveReasoning to simplify min/max expression. (Of course, it can also be weaker in other respects...)