WebAssembly
Shipping progress
This issue is meant to track which projects have updated their implementation to match the final proposal and have shipped by default, if applicable.
| Project | status |
|---|---|
| V8 | released in 9.1.54 |
| SpiderMonkey | |
| LLVM | Updated upstream, will be released in 13.0 |
| Binaryen | released in 101 |
| WABT | released in 1.0.22 |
| wasmparser.rs | released in 0.76.0 |
| wasdk/wasmparser | released in 5.0.1 |
| CodeMirror | in trunk; to be released in 5.59.5 |
| Emscripten | |
| Rust | intrinsics available on nightly, stable in 1.54.0+ (2021-07-29 release date) |
| Chrome | released in Chrome 91 |
| Firefox | in nightly; Firefox 89 on x86/x64 |
| Node | released in 16.4.0 |
| WAMR | |
| Wasmtime | |
| Lucet | |
| WAVM | in trunk |
| SSVM | |
| Wasmer | on master |
Can we add WAMR, Wasmtime, and Lucet to that list? Perhaps WAVM and SSVM as well?
(Should we update the implementation status document for those runtimes as well?)
Now that the proposal is finalized, the more fine-grained status documents aren't as useful IMO because support has become more or less binary.
Can we add https://github.com/wasdk/wasmparser too? (note this is not the .rs one, this is used by Chrome DevTools iiuc)
For authors of tools, https://github.com/ngzhian/simd-opcodes might be handy, it's just a csv of opcodes (in int and hex) and names of instructions (and also signature, if it takes a memarg, and how many immediates they take). This might be useful for tools to use to generate whatever they need to in order to update their opcodes/add new opcodes.
@tlively I just realized that CodeMirror is missing from the list above. Without CodeMirror support (in the wast mode), SIMD instructions syntax highlighting will be wrong/confusing to developers in their DevTools.
wasdk/wasmparser has the changes in 5.0.1 (see https://github.com/wasdk/wasmparser/pull/92#issuecomment-790311183)
V8 update just got merged in https://crrev.com/c/2728432, it will be in version 9.1.54 (once I know the Chrome Canary version I'll share it here.)
CodeMirror is updated https://github.com/codemirror/CodeMirror/pull/6613 (should be in 5.59.5, based on numberings so far).
Chrome canary supports SIMD on by default as of 91.0.4442.4 on Linux, and 91.0.4441.0+ on other platforms (Windows, Mac, Android).
I updated LLVM's status. All operations LLVM supports have the correct names and numbers, but it does not yet support all the new operations. wasm_simd128.h also has not yet been updated, but its planned changes are discussed in #342.
Firefox 89 (now in Nightly) on x86/x64 is believed to have all instructions with final opcode assignments.
Wasmer now supports the final SIMD opcodes (with all spectests passing) for x86 and aarch64 in master 🚀
More info: https://github.com/wasmerio/wasmer/pull/2156
The Rust language support for the simd proposal is in the home stretch and things are about to become stable and much more difficult to change after that point. A high-level summary of Rust's support is:
- Check here to see what's becoming stable
- nightly documentation of intrinsics
- If everything proceeds apace support will be in stable Rust 1.54, to be released on July 29th 2021
If anyone is curious feel free to check out the APIs and/or naming and such. Always willing to hear feedback on that! The tracking issue is in "FCP" as of this moment. This means that there's another week or so for any final concerns to be raised. If no concerns are raised then these will become stable on the nightly channel for Rust and will get released as part of Rust 1.54.
Once this all lands the std::arch::wasm32 module in Rust's standard library (and the corresponding core::arch::wasm32 module) will have all the necessary functions/intrinsics/types to generate wasm binaries that use this proposal.
Node.js now supports the final SIMD opcodes as of version 16.4.0, since V8 was updated to 9.1.269.36 (https://github.com/nodejs/node/pull/38273).
