wasi-threads
wasi-threads copied to clipboard
In a discussion yesterday with @sbc100 and @sunfishcode, we considered whether it might be necessary to add a second API call to the `wasi-threads` proposal to support early exit from...
the description of `wasi_thread_spawn` says: ``` instantiate the module again — this child instance will be used for the new thread ``` it isn't obvious to me which module "the...
I came across below from [rust-lang making a triple wasm32-wasi-preview1-threads](https://github.com/rust-lang/rust/pull/112922#issuecomment-1632394649) > That's not right, [wasi-threads](https://github.com/WebAssembly/wasi-threads) is an extension to the Wasi Preview 1 specification which adds support for threads. That...
When I run `build.sh`, I see the following errors: ``` $ ./build.sh Compiling testsuite/thread_spawn-simple.c testsuite/thread_spawn-simple.c:3:10: fatal error: 'wasi/api.h' file not found #include ^~~~~~~~~~~~ 1 error generated. testsuite/wasi_thread_spawn.S:5:2: error: unknown directive...
I was wondering what the plans are for thread-local variable destructors in Wasi, is this in scope at all? Typically something like `__cxa_thread_atexit` would be necessary.
Thread IDs are a design mistake and many OSes are moving away from them (e.g. pidfd on Linux, HANDLE on Windows). The main issue is that the lifetime of a...
currently it's just said: ``` When instantiating a module which is expected to run with `wasi-threads`, the WASI host must first allocate shared memories to satisfy the module's imports. ```...
For some algorithms, in order to partition work on several threads, we need to know how many threads are available. WebAssembly hosts may decide to limit the amount of parallelism...
Because `thread-spawn` can fail, we use return value to communicate error code. We also use return value to communicate success and pass thread id to the user. This usecase nicely...
See https://github.com/WebAssembly/wasi-threads/pull/26 and https://github.com/WebAssembly/wasi-threads/issues/29