Fix a bug where reordering tf.Transpose is not done correctly #47084
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.
When reordering tf.Transpose (downwards) and the original transpose must be preserved, the insertion point is off-by-one.
As demonstrated in attached test, this scenario is not handled properly:
Will get
operand #0 does not dominate this use
error from IR verifier, indicating a value is used before its def.cc: @huangkang-chn