bernhard added a comment.
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 :-)
Can we get clang not to automatically call wasm-opt if it is called without
`-X
bernhard added a comment.
> Would it work to increase the memory size, and then put your data in the new
> space this creates at the end of memory?
> `__data_end` and `__heap_base` aren't things you can move around once the
> linker has defined them. Their values can be baked in elsewhere in
bernhard added a comment.
> 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?
> Clang and wasm-ld are free to do anything wasm-opt
bernhard added a comment.
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-
