Sam Clegg

PTAL, I think this is good to land. Once it rolls in we can look at landing the emscripten side of this, followed by a tidy up here once that...

Actually I'm working on writing some tests.. not quite ready for review yet.

This change is less intrusive now. A new option was added that will cause the pass to use existing exports instead of imports. This will likely only ever be used...

I don't think we should do this. I think wabt should support all the testsuite features that are present in the amalgamated testsuite repo (https://github.com/WebAssembly/testsuite) and no others. If we...

> @sbc100 I'm using `wasm-c-api` to run wasm codes in my project. And AFAIK `wabt` is the only wasm engine built by c/c++ that fully supports the `wasm-c-api` standard. >...

I assume that `easywasm.wasm` is built using emscirten's SIDE_MODULE or MAIN_MODULE commands? The format of the `dylink` section using in emscripten (the output of `wasm-ld -shared` and `wasm-ld -pie`) changed...

BTW if you using emscripten's SIDE_MODULE to try to build a portable wasm file you probably want to switch to using the `STANDALONE_WASM` option which was designed for this purpose.

wasm-ld can combine object files using `-r/--relocatabe`. Sadly there is no support in binaryen for wasm object files (wasm files with relocations) so binaryen is probably not going to a...

BTW if the crash is in the bitcode compiler then wasm object files should be not relevant. The bitcode compile just takes as input bitcode/LTO files.

The only inputs the bitcode compiler are bitcode files, so whenever there is a crash in the bitcode compiler there should be set of pure-bitcode files that can reproduce it....