binaryen

binaryen copied to clipboard

miss-optimization for continuous add

2

These assemblyscript code ```ts (func $assembly/index/_start (result i32) global.get $assembly/index/a0 global.get $assembly/index/a1 i32.add global.get $assembly/index/a2 i32.add global.get $assembly/index/a3 i32.add global.get $assembly/index/a4 i32.add global.get $assembly/index/a5 i32.add global.get $assembly/index/a6 i32.add return )...

HerrCai0907

Are there plans for Rust bindings?

6

I am not qualified to write rust bindings for the C apis. But I want to write my language AST to WebAssembly and Binaryen seemed perfect for it. There is...

clacladev

If you can't host the files for your source map, you can put their contents in the `sourcesContent` field of your source map JSON file https://tc39.es/source-map/#sourcescontent When emscripten runs wasm-emscripten-finalize...

verhovsky

Support 5 segment source mappings

3

Support 5-segment source mappings. Reference: https://github.com/tc39/source-map/blob/main/source-map-rev3.md#proposed-format

osa1

Support cross-module calls properly in the interpreter

2

Right now some things like function and tag literals store a name. The Literal for a RefFunc stores the name of the function, for example. That means we may refer...

kripken

WasmBinaryReader: Consistent internal naming

3

For defined functions/globals/tables/memories use `f1`, `t2`, `m3` etc. This matches the longer names used for imports such as `fimport$1`, but keeps the names nice and short by avoiding the embedded...

sbc100

Use explicit names for elements creating using `Builder::make_` methods

1

In all the cases I could find the `make_xx` helper method were called with meaningful names that are useful in the name section. See #6496 and #6806

sbc100

Start publishing signature files for binaryen artifacts

9

# Request Start publishing armored signature files for binaryen artifacts. E.g. for `binaryen-version_118-aarch64-linux.tar.gz` add `binaryen-version_118-aarch64-linux.tar.gz.asc` file so that the origin of this artchives can be validated. # Reasoning Today releases...

liutikas

GCC maybe-uninitialized failure

3

I'm trying to compile binaryen 118 with gcc 14.1.0 and run into this error ``` [ 30%] Building CXX object third_party/llvm-project/CMakeFiles/llvm_dwarf.dir/DWARFDebugAbbrev.cpp.o cd /usr/src/sbo_tmp/binaryen-version_118/build/third_party/llvm-project && /usr/libexec/icecc/bin/c++ -I/usr/src/sbo_tmp/binaryen-version_118/src -I/usr/src/sbo_tmp/binaryen-version_118/third_party/llvm-project/include -I/usr/src/sbo_tmp/binaryen-version_118/build -O2 -fPIC...

pprkut

Now custom sections can be placed at the end of module with `WasmBinaryWriter::writeLateCustomSections`.

HerrCai0907