[triton] Avoid propagating slice layouts across broadcast. #97350
+29
−0
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.