Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wasm SIMD support is missing or broken #40

Open
Ameobea opened this issue Jan 5, 2021 · 1 comment
Open

Wasm SIMD support is missing or broken #40

Ameobea opened this issue Jan 5, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@Ameobea
Copy link

Ameobea commented Jan 5, 2021

Describe the Bug

wasm-snip fails to parse Wasm that contains SIMD instructions such as v128:

error: failed to parse code section
  caused by found type v128
  caused by expected type i32
  caused by The input WebAssembly is invalid

Steps to Reproduce

  1. Take a Wasm file that uses SIMD instructions (example: https://ameo.link/u/8oc.wasm)
  2. Use it as input for wasm-snip: wasm-snip 8oc.wasm

Additional Context

This might just be a matter of bumping the wasm parsing libraries. However, some other Wasm tooling I use wasm-opt and wasm2wat both require special command line arguments to be passed in order to deal with SIMD.

@Ameobea Ameobea added the bug Something isn't working label Jan 5, 2021
@sagacity
Copy link

I've rebased wasm-snip on top of Walrus 0.19.0 and that seems to work. However, I'm not sure if this project is currently active or not, since this issue has been open for so long, so I don't know whether I should prepare a pull request or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants