Sam Clegg

I think if you don't want debug info in your binary you probably want to either link with `-Wl,--strip` or run `strip` (`llvm-strip` really) on the final binary. The alternative...

I don't have a strong opinion. It does main that anyone who builds a debug binary won't be able to step into any system functions, but maybe that fine/normal/expected?

> > It does main that anyone who builds a debug binary won't be able to step into any system functions > > Note that `wasi-libc` is already built sans...

Really? I thought that point of `RelWithDebugInfo` was that it was the same as `Release` in terms of opt level but with debug into? Maybe I'm wrong?

We should probably be consistent about shipping debug info or not for all libraries. Being consistent about optimization levels isn't critical I think, but it should be done deliberately. There...

I would hope its not too much work. I imagine most things will just work. The biggest change is likely that would we would need to start shipping all of...

I guess it depends how much we really case about module size in these types of cases. IIUC such modules don't contains any calls to these functions, they just occupy...

Do you actually have wasm2c running in production on s390x? Or is this just for CI/testing?

I that case I suggest we simply declare s390x and unsupported architecture for wasm2c.

I think its fine to say that wasm2c is only fully functional (spec conforming) on a fixed set of known/tested architectures. I don't see any reason to try to grow...