wasi-libc
wasi-libc copied to clipboard
WASI libc implementation for WebAssembly
This is a follow-up to https://github.com/WebAssembly/wasi-libc/pull/356 * `_POSIX_THREAD_PROCESS_SHARED`: Functions part of Thread Process-Shared Synchronization option like `pthread_barrierattr_getpshared` are defined when threads is enabled, so define it. * `_POSIX_THREAD_SAFE_FUNCTIONS`: "thread-safe functions"...
I work on a Swift testing library, swift-testing (https://github.com/apple/swift-testing). I'm looking at adding Wasm/WASI support using the SwiftWasm toolchain (https://www.swiftwasm.org/). One of the things we do when starting a test...
# Summary This is a proposal to add [wasi-sockets](https://github.com/WebAssembly/wasi-sockets) support to `wasi-libc` as a first step towards full WASI Preview 2 support. This includes adding a new `wasm32-wasi-preview2` build target...
I understand that a great thing about Makefile (versus CMake) is less dependencies. However, I see it comes with its own limitations, like not great Windows support, lack of ninja...
I need to make changes to the "c_header.rs" file because there are numerous instances where "size_t" is mistakenly identified as "uint32_t," which is incompatible with wasm64.
recent wasi-libc is broken if you put main in a library. test case: https://github.com/yamt/garbage/tree/d422b1073125b3fc8f843ce4b12280ab3982fb84/c/main_in_lib ``` spacetanuki% ./build-native.sh spacetanuki% ./a.out this is foo spacetanuki% WASI_SDK=/opt/wasi-sdk-20.0 ./build-wasi.sh spacetanuki% toywasm --wasi a.out this...
The `munmap` is supposed to do this, but also `msync` is completely missing.
The apis are still assuming they are 32 bit apis. How are you going to support them?
in posix, `openat(dirfd, "../b", ...)` should work. however, in wasi, O_RESOLVE_BENEATH behavior is unconditionally applied. (at least in popular implementations. i don't know if it was well documented for preview1....
This document outlines how wasi-libc can manage the changes to WASI 0.2.0 as well as future 0.2.x releases. It's meant as a starting point for collaboration; I'm interested in your...