Conversation
abrown
approved these changes
Aug 14, 2025
Collaborator
abrown
left a comment
There was a problem hiding this comment.
Thanks! I've been fuzzing this, comparing output of the scalar and SIMD versions, and things seem to check out. I'll also note that just enabling __wasm_simd128__ (without this logic) seemed to do some amount of vectorization — something to compare against later.
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.
Continuing #580.
memrchris mostly used to implementstrrchr, so that's what I test.It has the advantage that we know the length and can access the entire buffer, so no undefined behavior for this one. I does do unaligned reads, however, so
wasm_v128_loadis used to dereference the pointer. It uses SIMD while there are 16 or more bytes to read, then fallback to scalar.The only other notable feature is using
clzrather thanctz.