Sam Clegg

At the risk of going off topic, I assume there is no appetite for providing something like `uname` or `User-Agent` that might allow client code to know on what platform...

The wask-sdk does not support setjmp or other non-local control flow concepts (such as C++ exceptions) yet because WebAssembly does not yet support such things. There are several proposals in...

Apologies, on re-reading this does look like something that could probably be fixed. Most likely the correct solution is to patch libc++ headers to avoid including `c++/v1/setjmp.h`. We should also...

Its sounds like you are asking for some kind of virtual root directory to be created by wasi-libc... and in the case where `/` is actually included in the pre-opens...

Yes, musl code is written in C99 so it not surprising they don't use C11 atomics. Its does look like the assumption is that loads (and stores?) to `volatile` are...

That sounds reasonable. If you come up with a proposed musl patch, perhaps you could also sent it to emscripten's fork of musl too?

Musl's atomic macros typically work via inline assembly. While its true they could use C11 atomics where available, there is no need move to C11 just to implement `a_load`. The...

Agreed, although auditing all the access locations and adding `a_load` macros seem more in keeping with the musl coding style, and might even be upstream-able? Could it also be that...

> I just realized the open(2) is too complicated on wasm and even this syscall is too complicated https://github.com/trcrsired/wasi-libc/blob/c8352f8c145fe1fc21db79893f45ed7aa4d9eef2/libc-bottom-half/sources/__wasilibc_real.c#L437 > > There are no reasons to be so complicated tbh....

New clang warnings come along fairly rarely, don't they? I think we can just fix them or add `-Wno-missing-field-initializers` when we find these issues?