Use 128-bit data loading #326
Merged
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
|
@botbw Can you take a look to this PR? |
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.
For 128-bit vectorized load operations, we should use AutoVectorizingCopyWithAssumedAlignment<sizeof(uint128_t)*8> instead of AutoVectorizingCopyWithAssumedAlignment<sizeof(uint128_t)>. This is because the AutoVectorizingCopyWithAssumedAlignment template parameter expects the alignment value in bits, whereas sizeof(uint128_t) returns 16 bytes. Passing the byte value directly would mistakenly make the template use 16-bit alignment, resulting in actual operations using uint16_t for data loading rather than the intended 128-bit vectorized loading.