Skip to content
This repository has been archived by the owner on Dec 22, 2021. It is now read-only.

Opcode renumbering progress tracking #216

Closed
tlively opened this issue May 1, 2020 · 12 comments
Closed

Opcode renumbering progress tracking #216

tlively opened this issue May 1, 2020 · 12 comments
Labels

Comments

@tlively
Copy link
Member

tlively commented May 1, 2020

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.

  • ✅ V8: merged and available from jsvu
  • ✅ LLVM: merged upstream
  • ✅ Binaryen: merged upstream
  • ✅ WABT: released in 1.0.15
  • ✅ Emscripten: released in 1.39.15
  • ✅ wasmparser.rs: released in 0.52
  • ✅ Chrome: released to Stable in 84
  • ✅ Firefox Nightly
  • ✅ Node: Released in 14.6.
  • 📝 Rust: LLVM PR merged, rust-lang/rust PR to follow
  • ❔ ImplementationStatus.md, BinarySIMD.md, and tests in this repo
@abrown
Copy link
Contributor

abrown commented May 1, 2020

Can we add wasmparser.rs?

@tlively
Copy link
Member Author

tlively commented May 1, 2020

Sure, what's its status right now?

@abrown
Copy link
Contributor

abrown commented May 1, 2020

WIP

@zeux
Copy link
Contributor

zeux commented May 2, 2020

Would be great to also track binary releases and dependent tools:

  • Enscripten latest
  • jsvu/v8 nightly (this might be ready? Unsure)
  • Chrome Canary
  • Chrome Stable (this will take time obviously)
  • node nightly
  • node stable (this will take time, as well as one above)

@dtig
Copy link
Member

dtig commented May 4, 2020

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.

@yurydelendik
Copy link

wasmparser.rs changed the encoding in 0.52

@zeux
Copy link
Contributor

zeux commented May 5, 2020

Just wanted to confirm that the current status makes SIMD work end-to-end, see zeux/meshoptimizer#141:

  • Built using emscripten tot (available as a binary release via emsdk install tot, no need to build anything manually)
  • Tested in CI using node-v8 lkgr Linux build
  • Also works in Chrome Canary on Windows

Which was basically painless :)

dtig added a commit to dtig/wasm-feature-detect that referenced this issue May 12, 2020
Roll forward the Wabt version to include the SIMD opcode renumbering changes as reflected in the tracking issue - WebAssembly/simd#216.
@zeux
Copy link
Contributor

zeux commented Jul 25, 2020

node.js 14.6 supports new opcode encoding now.

@zeux
Copy link
Contributor

zeux commented Jul 25, 2020

And so does Chrome 84 (which is a release build)

@tlively
Copy link
Member Author

tlively commented Jul 25, 2020

Thanks! Updated the opening post.

@lars-t-hansen
Copy link
Contributor

FWIW, so does Firefox (still Nightly-only).

@tlively
Copy link
Member Author

tlively commented Jan 8, 2021

Closing this because I am not aware of further work that needs to be done here.

@tlively tlively closed this as completed Jan 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

6 participants