[triton] Avoid propagating slice layouts across broadcast. #97350
Conversation
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
b4668bd to
85f7f3e
Compare
6af2f74 to
ab3aca1
Compare
This can cause massive register pressure, and it's better to convert to blocked before the broadcast. The current state of RemoveLayoutConversion relies on slice layouts being pushed up in the second (hoisting) phase on top of broadcasts again, but this fails for the softmax pattern. PiperOrigin-RevId: 786179698
ab3aca1 to
94dba73
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.
[triton] Avoid propagating slice layouts across broadcast.
This can cause massive register pressure, and it's better to convert to blocked before the broadcast. The current state of RemoveLayoutConversion relies on slice layouts being pushed up in the second (hoisting) phase on top of broadcasts again, but this fails for the softmax pattern.