Sam Clegg

Hmm .. that does look wrong. Note that WASI SDK versioning is independent of llvm/clang versioning so that fact that wasi-sdk-13 is supposed to contain llvm-13.0.0 is just a coincidence....

d32170dbd5b0d54436537b6b75beaf44324e0c28 is indeed the revision which is tagged as llvmorg-10.0.0 so this is not just clang being confused about which version it is.

Interesting. I guess we need to choose between declare functions that don't exist at link time (we do this for raise() for example, although that is probably an oversight) and...

I still think `-Wl,--trace-symbol=__wasi_fd_close` is going to be your best starting point. It should tell you which object file is causing that symbol to be include. If you build with...

Out of interest is there some fundamental reason why you don't use those `wasi_snapshot_preview1` imports? It is just code size or are you trying to target an environment that doesn't...

We are always open to ideas on how to shrink the output binaries. If you want to help with that effort there are tools out there such as https://github.com/rustwasm/twiggy and...

Most likely the majority the space is the overhead of using C++ streams which I believe transitively bring in a lot of stuff.

For some background the waterfall is single python script that pulls in llvm (both upstram and fastcomp), v8, wasi-sysroot, libc++, libc++abi, compiler-rt, binaryen, emscripten, wabt all from ToT and tries...

Can you see where those imports are being called from if you look at the disassembly? You should able to track down the reason they are needed that way. You...

Yes it looks like the indirect calls. This are pulled in by usage of stdin/stdout/stderr. See: https://github.com/WebAssembly/wasi-libc/blob/a78cd329aec717f149934d7362f57050c9401f60/libc-top-half/musl/src/stdio/stdout.c#L5-L18 And also fdopen (although I suspect is a stdout/stderr reference in this case):...