-
Notifications
You must be signed in to change notification settings - Fork 43
Opcode renumbering progress tracking #216
Comments
Can we add wasmparser.rs? |
Sure, what's its status right now? |
WIP |
Would be great to also track binary releases and dependent tools:
|
This is available in the V8 nightly version from 8.4.268 onwards, and the Chrome Canary version 84.0.4133.0 on Windows, Mac and Android (Linux, iOS still catching up). It should eventually be released to stable on Chrome 84. It looks like the latest node update was to V8 8.1.307.31, so it will take some time, but depending on ABI compatibility, it might be possible to have 8.4 in Node.js 14. Another place to try this out in Node is node-v8 which is an automatically updated experimental version of Node.js with the V8 lkgr. |
wasmparser.rs changed the encoding in 0.52 |
Just wanted to confirm that the current status makes SIMD work end-to-end, see zeux/meshoptimizer#141:
Which was basically painless :) |
Roll forward the Wabt version to include the SIMD opcode renumbering changes as reflected in the tracking issue - WebAssembly/simd#216.
node.js 14.6 supports new opcode encoding now. |
And so does Chrome 84 (which is a release build) |
Thanks! Updated the opening post. |
FWIW, so does Firefox (still Nightly-only). |
Closing this because I am not aware of further work that needs to be done here. |
We have started upating projects to use the new opcodes proposed in #209 according the process described in #129. This issue tracks the progress of the update for various projects. Feel free to comment on the progress of the update for any additional projects you may know about.
The text was updated successfully, but these errors were encountered: