Andrew Brown

This issue is probably out of date by now; we can reopen if we want to revisit it but what is included in wasi-sdk has been stable-ish for the last...

Things have changed: over the last few months, several of us have added a `wasm32-wasi-threads` target to wasi-libc which is now available as a pre-release in the [`wasi-sdk-20+threads`](https://github.com/WebAssembly/wasi-sdk/releases/tag/wasi-sdk-20%2Bthreads) artifacts. More...

wasi-sdk has upgraded its LLVM tree since this issue; this is likely resolved. We can reopen if it is not.

@alexcrichton, I rebased this PR on top of all of the previous Wiggle work (https://github.com/bytecodealliance/wasmtime/pull/5225, https://github.com/bytecodealliance/wasmtime/pull/5229, https://github.com/bytecodealliance/wasmtime/pull/5264) since Wiggle seems safe enough at this point. Optionally, we could merge this...

@ArtBlnd, I believe the CI failure here is due to some rustc changes between when this PR was open and now. Can you rebase this PR and see if that...

It seems like this should be an upstream issue on LLVM. @sunfishcode opened https://github.com/llvm/llvm-project/issues/64909 to track this. I'll close this here and we can continue the discussion there.

@haraldh, I think this has been superseded by https://github.com/bytecodealliance/wasmtime/pull/5239; should we close this PR?

@haraldh, you should now be able to run the applicable benchmarks with something like `cargo bench wasi/` from the top-level project directory.

This review got auto-assigned to me but I think @fitzgen and @alexcrichton have the right context for the review here.

The last time we talked about this, there were two "roadblocks" to starting to work on this issue: 1. _Benchmarking_: adding `RwLock`s (e.g.) to various fields of the WASI context...