[XLA:GPU] move instruction renaming to a separate pass from priority fusion #23930
Conversation
This file contains 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
![copybara-service[bot]](https://avatars.githubusercontent.com/in/44061?s=60&v=4){kind=small}
copybara-service
bot
force-pushed
the
test_738384795
branch
3 times, most recently
from
e40a4dd to
053a951
Compare
…fusion Why: 1. Smaller function. 2. Previously priority fusion pass claimed that it has not modified the HLO while it at least renamed the instructions. PiperOrigin-RevId: 738775070
copybara-service
bot
force-pushed
the
test_738384795
branch
from
053a951 to
dc6e97a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
[XLA:GPU] move instruction renaming to a separate pass from priority fusion
Why:
Smaller function.
Previously priority fusion pass claimed that it has not modified the HLO while it at least renamed the instructions.