Sam Clegg

One difference between wasm-libc and other/normal software that you might want to package is that it is designed to be used only within the sysroot of a cross compiler. I...

Fair enough! Sounds like you have interesting alternative to the traditional notion of a sysroot (I can't say I understand how it all fits together but it sounds interesting).

It makes sense to me to leave them for possible future use. Since these modules can be thought of as emulating POSIX I can't see why we wouldn't one day...

We have libc++ and libc++abi are easy enough to build on top of wasi-libc. I don't think they have any requirements that clang and wasi-libc don't already have: See https://github.com/CraneStation/wasi-sdk/blob/master/Makefile

Won't wasi-libc ever want to combine errno values from different proposal into a single value? i.e. will proposal not share error codes at the libc level?

You are correct about the default memory layout. That was chosen deliberately in order to give static address very small absolute values in order to minimize code size (the `i32.const...

> A followup question (or perhaps feedback): how could I have discovered the `stack-first`, `stack-size` and `initial-memory` flags outside of searching issues? https://webassembly.org/ has a number of links to reference-level...

This sounds to my like it is not really a WASI question at all. WASI provides a non-POSIX capability-based filesystem API. wasi-libc provides emulation of a more traditional POSIX filesytem...

It looks like support for user defined custom sections is only implemented in https://reviews.llvm.org/D45297. However there is no support for this at the clang / C / C++ layer. Using...

Isn't the solution to remove the functions/headers so this becomes a compile error rather than a link error?