close
Skip to content

Tags: qdrvm/binaryen

Tags

1.38.28-patch.4

Toggle 1.38.28-patch.4's commit message
[fix] `cmake_minimum_required` version

1.38.28-patch.3

Toggle 1.38.28-patch.3's commit message

1.38.28-patch.2

Toggle 1.38.28-patch.2's commit message

1.38.28-patch.1

Toggle 1.38.28-patch.1's commit message
Performance fixup

version_102

Toggle version_102's commit message
fix version_102 for kagome

version_101

Toggle version_101's commit message
fix version_101 for kagome

version_67

Toggle version_67's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Strip the producers section in --strip-producers (WebAssembly#1875)

WebAssembly/tool-conventions#93 has a summary of emscripten's current thinking on this. For Binaryen, we don't want to do anything to the producers section by default, but do want it to be possible to optionally remove it. To achieve that, this PR

 * creates a --strip-producers pass that removes that section.
 * creates a --strip-debug pass that removes debug info, same as the old --strip, which is still around but deprecated.

A followup in emscripten will use this pass by default.

version_66

Toggle version_66's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
wasm-emscripten-finalize: Emit illegal dynCalls, and legalize them (W…

…ebAssembly#1890)

Before this, we just did not emit illegal dynCalls. This was wrong as we do need them (e.g. if a function with a setjmp call calls a function with an i64 param - we'll have an invoke with that signature there). We just need to legalize them. This fixes that by first emitting them, and second by running legalization late, after dynCalls have been generated, so it legalizes them too.

version_65

Toggle version_65's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Handle EM_ASM/EM_JS in LLVM wasm backend O0 output (WebAssembly#1888)

See emscripten-core/emscripten#7928 - we have been optimizing all wasms until now, and noticed this when the wasm object file path did not do so. When not optimizing, our methods of handling EM_ASM and EM_JS fail since the patterns are different.

Specifically, for EM_ASM we hunt for emscripten_asm_const(X, where X is a constant, but without opts it may be a get of a local. For EM_JS, the function body may not just contain a const, but a block with a set of the const and a return of a get later.

This adds logic to track gets and sets in basic blocks, which is sufficient to handle this.

1.38.25

Toggle 1.38.25's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
More misc ASAN fixes (WebAssembly#1882)

* fix buffer overflow in simple_ast.h printing.
* check wasm binary format reading of function export indexes for errors.
* check if s-expr format imports have a non-empty module and base.

Fixes WebAssembly#1876
Fixes WebAssembly#1877
Fixes WebAssembly#1879