cqwrteur

@abrown Hi. Could you explain why CI is not automatic but needs action from the maintainers?

I have removed all signal apis from the upstream file and regenerated api.h and __wasi_realfile.c.

Add CI for wasm64-wasi + wasm64-wasi-threads Add noexcept to all apis.

> This PR would effectively create a new wasm64 preview1 ABI, as well as a new wasi-threads ABI. Those are major new interfaces, that could eventually impact a large number...

 This works now. 

changed to _wasm64 based on feedback

https://github.com/WebAssembly/wasi-libc/blob/a796d874f8c47641c410746a3d4bd6a85d2baac2/libc-bottom-half/sources/preopens.c#L169 This is too complicated and not thread safe probably

No