Alon Zakai

Interesting... this is slow mainly on `simplify-locals` and `code-folding`. The former is a pass I've never seen slow before... profiling shows the issue there is effect computation as it tries...

`--code-folding` may be getting stuck on a single function, `$374`. It looks like ```wat (func $374 (param $0 i32) (result funcref) (block $block12186 (block $block12185 .. br_table .. (return (ref.func...

Oh, and you can skip `code-folding` for now using `--skip-pass=code-folding`. On my four-core machine, the speed is then much better, faster than naive `-O1` actually, using ``` wasm-opt test3.wasm -all...

Thanks for the details about the codegen here, very interesting! > I think they are not actually the same? Oh, sorry, I was reading the partially-optimized code - basically the...

The minimal testcase here looks like it should have worked in the past - I mean that it is so minimal, that given things used to work in general, it...

If bisection doesn't work, another option is to debug this in depth using Binaryen's instrumentation, comparing wasm and wasm2js builds. Specifically, we can instrument the builds so that every single...

@elpiel > Fatal: error: modules with multiple tables are not supported yet. Does wasm-bindgen emit multiple tables? If so hopefully there is a way to disable that.

IIUC, the relevant wasm2js output code is ```js var buffer = new ArrayBuffer(65536); function __wasm_memory_grow(pagesToAdd) { [..] var newBuffer = new ArrayBuffer(Math_imul(newPages, 65536)); var newHEAP8 = new Int8Array(newBuffer); newHEAP8.set(HEAP8); HEAP8...

I won't have time to work on this myself, I don't expect, but in general * Find out exactly how wasm-bindgen code is using the exported Memory, and how the...

The error is ``` error: library_pthread.js: library_pthread.js:23: #error "EVAL_CTORS is not compatible with pthreads yet (passive segments)" ``` which is correct, I think. The ctor-evaller would need to support passive...