Do something interesting with a Wasm-hosted, Wasm-targeting Clang/LLD?

I now provide exactly that at @yowasp/clang. The JavaScript package has a little bit of cursed glue code that uses -### to work around the inability to spawn subprocesses, but other than that the build is pure-WASI, and isn't dependent on JavaScript. If you are fine with invoking the linker manually then you do not need this glue code.

I plan to upstream the remaining changes to LLVM but haven't done so yet.

I recall there being some interest among the general BA folks in such a compiler, but unfortunately I cannot recall from whom, where, and for what purpose. The obvious option would be to bootstrap the entire WASI SDK with it, which I haven't done because the last 14 continuous hours of watching LLVM build make me sick if I think about it. But maybe there are some accessibility / outreach type things possible now too, like a Wasm playground?

Anyway, please have fun, and feel free to close the issue whenever you feel it's been taken into consideration.

Start by reviewing the @yowasp/clang package and its JavaScript glue around -###, then consider the pure-WASI Clang/LLD setup described in the issue. The issue does not define a specific change or acceptance criteria, so a concrete use case and scope would need to be established before implementation.