[LoopBoundSplit] Check if latch is operand of PHI induction variable #167227
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.
A problem occurs when conditionally comparing the PHI derived variable from the outer loop with ICmp in the inner loop of a nested loop. This is because the latch in the inner loop is not an operand of the outer loop PHI, causing an assert to occur when
getIncomingValueForBlockis called.The issue is resolved by verifying whether the latch is an operand of the current PHI.
Fixed: #156793, #61655