binaryen
binaryen copied to clipboard
Optimizer and compiler/toolchain library for WebAssembly
As of right now, the current outward facing API (C, JS/TS, etc) allows you to enumerate all exports in a WASM module. These can be further introspected to get more...
To the point where I haven't been patient enough for it to finish locally and I've temporarily deleted it to unblock running the rest of the test suite. Did something...
If I take a simple SIMD test from emscripten and build with `MEMORY64=2` (lowering) I get errors like this one: ``` $ wasm-opt --memory64-lowering --strip-producers in.wasm -o out.wasm -g --mvp-features...
I'm seeing this with quite a lot of wasm64 tests in emscripten: ``` wasm-opt: /usr/local/google/home/sbc/dev/wasm/binaryen/src/wasm.h:715: T *wasm::Expression::cast() [T = wasm::Const]: Assertion `int(_id) == int(T::SpecificId)' failed. emcc: error: '/usr/local/google/home/sbc/dev/wasm/binaryen-out/bin/wasm-opt --memory64-lowering --strip-producers...
This was originally posted as an Emscripten issue ([#13150](https://github.com/emscripten-core/emscripten/issues/13150)) but it really involves a change to Binaryen so I'm reposting it here. An app I'm porting has 3000 instrumented functions...
tinygo build -o fib-tiny.wasm -target=wasm ./main.go Unknown option '--version' no usable wasm-opt found, update or run "make binaryen" /Users/liuyong/go/src/bin/wasm-opt: exit status 1
Fuzzer found this: ``` (module (type $v128_=>_v128 (func (param v128) (result v128))) (func $0 (param $0 v128) (result v128) (i32x4.dot_i8x16_i7x16_add_s (v128.const i32x4 0x00000000 0x00000000 0x00000000 0x00000000) (v128.const i32x4 0x30181f08 0xffffff96...
I'm reading https://github.com/WebAssembly/binaryen/wiki/binaryen.js-API and I noticed literally none of the SIMD types available (available in the latest version on npm) are documented. Could this be resolved so I'm not just...
web-gphoto2 builds with pthreads, Asyncify, exceptions and LTO, and I'm not sure which combo is specifically problematic here, but the end result is that it crashes when trying to switch...
Heya, reporting an apparently unsupported build configuration. Noticed this when attempting to update Emscripten to latest at Unity. Our CI gives at CMake time: ``` [15:06:45.499 Information] Cloning into '/home/bokken/build/output/Unity-Technologies/emscripten-builder/emsdk/binaryen/main'......