Iteratively determine ops that are only used in backward remat slice#9245
Merged
Conversation
neildhar
force-pushed
the
iterative-single-use
branch
from
ea22f4c to
b7c17d3
Compare
neildhar
force-pushed
the
iterative-single-use
branch
from
b7c17d3 to
04c101a
Compare
peterbell10
approved these changes
Feb 16, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Replace the current recursive
isOpSingleUsehelper with an iterative traversal that starts from the ops used directly outside a slice and propagates to their operands. This simplifies the code and makes the handling of block arguments explicit. This is an incremental step towards properly handling block arguments (at least for for-loops) in #9201.