Faster UTF-32 to UTF-16 on Westmere - #708
Merged
WojciechMula merged 1 commit intoMar 23, 2025
Merged
Conversation
WojciechMula
force-pushed
the
westmere-utf32-to-utf16
branch
2 times, most recently
from
March 20, 2025 17:45
9a8a785 to
870d4c5
Compare
Collaborator
Author
|
As usual, I'd like to update other targets gradually. |
WojciechMula
marked this pull request as ready for review
March 20, 2025 18:09
Use vectorized handling of surrogates. The lookup tables for this are not that big.
WojciechMula
force-pushed
the
westmere-utf32-to-utf16
branch
from
March 21, 2025 20:42
870d4c5 to
bee2c75
Compare
lemire
approved these changes
Mar 21, 2025
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
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.
Use vectorized code to handle surrogate pairs generation. For now in Westmere kernel.
Result for:
There are no performance regressions for the common case (no surrogates path), the vectorized building surrogate pairs is really fast. It cost us
2*16*16bytes = 0.5kB additional lookup tables.Ryzen
Skylake-X
IceLake