Remove note stating SSE 4.1 is required for WASM SIMD #7231
+1
−1
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
|
Thanks! |
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.
WASM is just a specification. Nothing in it requires any features from the host CPU; you can always emulate complex WASM features using simpler CPU instructions.
The PR that originally added this note (#7167) referenced a discussion in Wasmtime: bytecodealliance/wasmtime#3809. However, nothing in that issue means that it's impossible to implement WASM SIMD without SSE 4.1. It just means that Wasmtime specifically didn't want to at the time, because it's harder. In fact, according to bytecodealliance/wasmtime#3810 they do now support SIMD instructions on CPUs without any optional extensions.
I haven't investigated whether any browsers or runtimes other than Wasmtime impose CPU requirements to use WASM SIMD. But if they do, such notes should probably go on the browser and not on the feature.