Dan Gohman

The other major factor here is static linking, since WASI doesn't yet support dynamic linking -- though it is [planned](https://github.com/WebAssembly/module-linking/blob/master/proposals/module-linking/Explainer.md#shared-everything-dynamic-linking). For comparison, on a native toolchain, `clang++ -Oz -static` with...

Another thing that might help is LTO; https://github.com/WebAssembly/wasi-sdk/pull/89 implements LTO in wasi-sdk in a way that includes libcxx and libc, which should enable more aggressive dead-code elimination. That PR is...

I do hope to finish #89 at some point, but don't have a specific timeline.

This is now rebased on top of #106, so the changes are much clearer now.

I guess this comes from libc++'s terminate handler, which does `fprintf(stderr, ...)`. Unfortunately, I don't know of an easy way to tell libc++ not to link in this code.

Looks like `LIBCXXABI_BAREMETAL` may be pretty close to what we want already; would it make sense to enable that in wasi-sdk builds?

clang doesn't use target prefixes, as far as I'm aware; that arose from GCC needing to be compiled separately for each target. There's already been a lot of confusion over...

Ah, I didn't know that clang picked up a default target from argv[0]. TIL. I'd be curious to know how people use that. Would one install wasm32-wasi-clang in the same...

@cfallin: Sysroots contain libraries and headers that are "shipped with the OS" in a sense. Some includes and libraries are expected to be "shipped with the compiler" and are not...

Ah, also: > Finally, do you think such a "wrap an existing clang" distribution could/should exist as part of this wasi-sdk repo? Yes. wasi-sdk applies no clang patches, so it...