[Codegen] Refactor RemoveSingleIteratinLoop to use ValueBoundsOpInte… #19678
+197
−276
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.
…rface
Now, RemoveLingleIterationLoop uses the same ValueBoundsOpInterface logic as IREELoopInvariantCodeMotion, unifying the two passes and getting rid of a half-baked implementation of that constraint analysis.
In order to preserve existing functionality,
PropagateDispatchSizeBounds is updated to correctly propagate constant sizes to constants.
Also, add a test to make sure that the eliminator now understands the constraints imposed by delinearize and linearize.