[Mosaic TPU] Relax offset alignment requirement during mask generation for packed types in SingleRowVRegBounds.
#34585
+36
−13
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
copybara-service
bot
force-pushed
the
test_859825926
branch
from
e1cfdfd to
6504b0b
Compare
…n for packed types in `SingleRowVRegBounds`. Allow the `stop_offset_` to be unaligned with sublane boundaries. The `start_offset_` must still be aligned to prevent over complication. In this case, we can still easily track down where the actual data is located. PiperOrigin-RevId: 859825926
copybara-service
bot
force-pushed
the
test_859825926
branch
from
6504b0b to
e89c1a3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
[Mosaic TPU] Relax offset alignment requirement during mask generation for packed types in
SingleRowVRegBounds.Allow the
stop_offset_to be unaligned with sublane boundaries. Thestart_offset_must still be aligned to prevent over complication. In this case, we can still easily track down where the actual data is located.