about summary refs log tree commit diff
path: root/compiler/rustc_codegen_cranelift/src
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2024-04-17 21:05:48 +0000
committerbors <bors@rust-lang.org>2024-04-17 21:05:48 +0000
commitbecebb3158149a115cad8a402612e25436a7e37b (patch)
tree1f3aa2e9e3dab93a5e2244e26b5bd3a9851c694a /compiler/rustc_codegen_cranelift/src
parent38104f3a8838f8662ad3cccc4d7262a96bf9724e (diff)
parent8bb9d30a02552cb04fe9d7f7b57ee378fbe6f246 (diff)
downloadrust-becebb3158149a115cad8a402612e25436a7e37b.tar.gz
rust-becebb3158149a115cad8a402612e25436a7e37b.zip
Auto merge of #123978 - alexcrichton:update-wasi-toolchain, r=Mark-Simulacrum
Update how WASI toolchains are used in CI and bootstrap

This commit updates how the WASI targets are configured with their toolchain. Long ago a `config.toml` option of `wasi-root` was added to enable building with the WASI files produced by wasi-libc. Additionally for CI testing and release building the Rust toolchain has been using a hard-coded commit of wasi-libc which is bundled with the release of the `wasm32-wasip1` target, for example.

Nowadays though the wasi-sdk project, the C/C++ toolchain for WASI, is the go-to solution for compiling/linking WASI code and contains the more-or-less official releases of wasi-libc. This commit migrates CI to using wasi-sdk releases and additionally updates `bootstrap` to recognize when this is configured. This means that with `$WASI_SDK_PATH` configured there's no further configuration necessary to get a working build. Notably this also works better for the new targets of WASI as well, such as `wasm32-wasip2` and `wasm32-wasip1-threads` where the wasi-sdk release now has libraries for all targets bundled within it.
Diffstat (limited to 'compiler/rustc_codegen_cranelift/src')
0 files changed, 0 insertions, 0 deletions