I had an application crash with optimizations enabled, so I wanted to keep the debug info but the automatic wasm-opt kept removing it and I lost another 30 minutes to this, so I'm back :-)
May 2 2020
Apr 23 2020
Would it work to increase the memory size, and then put your data in the new space this creates at the end of memory?
It's for users who want smaller wasm binaries. It's not currently documented, though yes, it would be nice to document it.
But how would a user even end up with wasm-opt in the same directory of clang binaries?
Are there plans to offer a way to disable this behavior (or have it optional in the first place)?
We'd like to run some custom processing between wasm-ld and wasm-opt which can't happen after the latter due to some of its one-way destructive optimizations (i.e. memory-packing or simplify-globals passes).
The only way now is to tell our users to place wasm-opt somewhere where clang can't find it. Or instead of using one clang super-command to manually call -cc1 and wasm-ld separately which is disappointing.