-
Notifications
You must be signed in to change notification settings - Fork 15.2k
[VectorCombine] Apply InstSimplify in scalarizeOpOrCmp to avoid infinite loop #153069
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
4 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
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
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.
Sorry for the delay with the review.
After thinking about this for a bit, I think
scalarizeOpOrCmpshould only scalarize iff the base vectorNewVecCcan be folded.I think that's what the original code in 0d2a0b4 kind of assumed. It's probably never profitable to do the scalarization if the base vector doesn't go away.
And whenever I was last working on
scalarizeOpOrCmp, my only motivation was to scalarize scalable splats, which are inserts into poison vectors that are constant foldable anyway.If we change
TargetFoldertoInstSimplifyFolderin this PR to minimize the regressions, and do something likethen we can get rid of the early out in
foldInsExtBinop, and also this bit below:I think the only regression we would be left with is that we can't constant fold n-ary intrinsics at the moment, but this is something that we should fix in
IRBuilderFolder. This would basically undo #138406, but I'm happy to take those regressions for now if we want this fix to land in for LLVM 21.What do you think? cc @RKSimon
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've opened up #153743 to track folding n-ary intrinsics
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.
It sounds reasonable to me if there is no possible profitability. And I think
simplifyInstruction(Instruction *I, const SimplifyQuery &Q)inInstSimplifywould resolve your concern about n-ary intrinsics.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.
Or
ConstantFoldInstOperandsmay be simpler.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.
simplifyInstWithOperandsrequires distinguishing intrinsics among the operators. Thus, I implement bysimplifyCmpInst,simplifyUnOp, etc., case by case.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.
Oh perfect, great to see we could avoid the regression. Thanks!