Skip to content

Commit 775cb23

Browse files
committed
doc: update Wasmtime flags
Wasmtime's `--wasm-features` and `--wasi-modules` flags have been renamed since these docs were initially written. Additionally, from my testing I don't believe `--wasm threads` is needed if `--wasi threads` is passed already.
1 parent 96cfc75 commit 775cb23

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

Diff for: src/doc/rustc/src/platform-support/wasm32-wasip1-threads.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ This target is not a stable target. This means that there are a few engines
100100
which implement the `wasi-threads` feature and if they do they're likely behind a
101101
flag, for example:
102102

103-
* Wasmtime - `--wasm-features=threads --wasi-modules=experimental-wasi-threads`
103+
* Wasmtime - `--wasi threads`
104104
* [WAMR](https://github.com/bytecodealliance/wasm-micro-runtime) - needs to be built with WAMR_BUILD_LIB_WASI_THREADS=1
105105

106106
## Building the target

Diff for: src/doc/rustc/src/platform-support/wasm64-unknown-unknown.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ which implement the `memory64` feature and if they do they're likely behind a
3636
flag, for example:
3737

3838
* Nodejs - `--experimental-wasm-memory64`
39-
* Wasmtime - `--wasm-features memory64`
39+
* Wasmtime - `--wasm memory64`
4040

4141
Also note that at this time the `wasm64-unknown-unknown` target assumes the
4242
presence of other merged wasm proposals such as (with their LLVM feature flags):

0 commit comments

Comments
 (0)