diff options
| author | DaniPopes <57450786+DaniPopes@users.noreply.github.com> | 2025-02-27 23:07:50 +0100 |
|---|---|---|
| committer | DaniPopes <57450786+DaniPopes@users.noreply.github.com> | 2025-02-27 23:10:54 +0100 |
| commit | 775cb23dbc58f991f300cea5d3f66b088a3950d0 (patch) | |
| tree | 495401f0c23116566f4e57e9a287d9974d93234b | |
| parent | 96cfc75584359ae7ad11cc45968059f29e7b44b7 (diff) | |
| download | rust-775cb23dbc58f991f300cea5d3f66b088a3950d0.tar.gz rust-775cb23dbc58f991f300cea5d3f66b088a3950d0.zip | |
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.
| -rw-r--r-- | src/doc/rustc/src/platform-support/wasm32-wasip1-threads.md | 2 | ||||
| -rw-r--r-- | src/doc/rustc/src/platform-support/wasm64-unknown-unknown.md | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/src/doc/rustc/src/platform-support/wasm32-wasip1-threads.md b/src/doc/rustc/src/platform-support/wasm32-wasip1-threads.md index 994c0f4bbb3..1b0a312ca9c 100644 --- a/src/doc/rustc/src/platform-support/wasm32-wasip1-threads.md +++ b/src/doc/rustc/src/platform-support/wasm32-wasip1-threads.md @@ -100,7 +100,7 @@ This target is not a stable target. This means that there are a few engines which implement the `wasi-threads` feature and if they do they're likely behind a flag, for example: -* Wasmtime - `--wasm-features=threads --wasi-modules=experimental-wasi-threads` +* Wasmtime - `--wasi threads` * [WAMR](https://github.com/bytecodealliance/wasm-micro-runtime) - needs to be built with WAMR_BUILD_LIB_WASI_THREADS=1 ## Building the target diff --git a/src/doc/rustc/src/platform-support/wasm64-unknown-unknown.md b/src/doc/rustc/src/platform-support/wasm64-unknown-unknown.md index 6932e6a5764..a717f5dad79 100644 --- a/src/doc/rustc/src/platform-support/wasm64-unknown-unknown.md +++ b/src/doc/rustc/src/platform-support/wasm64-unknown-unknown.md @@ -36,7 +36,7 @@ which implement the `memory64` feature and if they do they're likely behind a flag, for example: * Nodejs - `--experimental-wasm-memory64` -* Wasmtime - `--wasm-features memory64` +* Wasmtime - `--wasm memory64` Also note that at this time the `wasm64-unknown-unknown` target assumes the presence of other merged wasm proposals such as (with their LLVM feature flags): |