Sam Clegg

> Thank you for your tips. > > > What runtime are you using to try to run your binary? I looks like that runtime is not providing the necessary...

I also have a patch to upstream the fix we made in emscripten: https://reviews.llvm.org/D74885

No really, I guess we should push on it?

Looks like we are moving forward with https://reviews.llvm.org/D31413. I'm hoping we even get it into llvm 11 which is about to be released.

Interesting, I hadn't realized the `-save-temps` caused the MC layer not only output the assembler but also try to re-parse it. That makes full `.s` file round-tripping more critical than...

This is bug in the llvm itself and the `.s` assembly file handling. Can you open bug at bugs.llvm.org, and if possible attach the failing input file if you could?...

I believe you can either add `__attribute__((export_name("foo")))` to the functions you want to export or build with `-Wl,--export=foo`

Also, if just want to experiment with SDK you can download the existing mingw SDK from the releases page: https://github.com/WebAssembly/wasi-sdk/releases.

This is quite easily reproducible with: ``` $ echo "#include " > test.c $ ./bin/clang --sysroot share/wasi-sysroot/ -std=c90 test.c In file included from test.c:1: In file included from share/wasi-sysroot//include/sys/socket.h:5: In...

Yup, or just dropping c90 (since c11 is the default). But still we need to fix the actual issue in the SDK.