[XLA:GPU] Fix RaggedAllToAllDecomposer when input and output buffers have different sizes. #23256
+121
−21
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_732101740
branch
4 times, most recently
from
eb189af to
666faa5
Compare
…have different sizes. We were doubling the size of the buffer to be able to use dynamic-update-slice, because by HLO semantics, if the update goes out of bound of the result, the update is not applied at all. The correct solution is to pad to `input_size + output_size`. PiperOrigin-RevId: 732239941
copybara-service
bot
force-pushed
the
test_732101740
branch
from
666faa5 to
0c04616
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] Fix RaggedAllToAllDecomposer when input and output buffers have different sizes.
We were doubling the size of the buffer to be able to use dynamic-update-slice, because by HLO semantics, if the update goes out of bound of the result, the update is not applied at all. The correct solution is to pad to
input_size + output_size.