Update wasi-sdk used in CI/releases#152183
Open
alexcrichton wants to merge 1 commit intorust-lang:mainfrom
Open
Update wasi-sdk used in CI/releases#152183alexcrichton wants to merge 1 commit intorust-lang:mainfrom
alexcrichton wants to merge 1 commit intorust-lang:mainfrom
Conversation
rustbot
added
A-CI
Collaborator
|
r? @jieyouxu rustbot has assigned @jieyouxu. Use Why was this reviewer chosen?The reviewer was selected based on:
|
rustbot
added
the
T-libs
This comment has been minimized.
This comment has been minimized.
This is similar to prior updates such as 149037 in that this is just updating a URL. This update though has some technical updates accompanying it as well, however: * The `wasm32-wasip2` target no longer uses APIs from WASIp1 on this target, even for startup. This means that the final binary no longer has an "adapter" which can help making instantiation of a component a bit more lean. * In 147572 libstd was updated to use wasi-libc more often on the `wasm32-wasip2` target. This uncovered a number of bugs in wasi-libc such as 149864, 150291, and 151016. These are all fixed in wasi-sdk-30 so the workarounds in the standard library are all removed. Overall this is not expected to have any sort of major impact on users of WASI targets. Instead it's expected to be a normal routine update to keep the wheels greased and oiled.
alexcrichton
force-pushed
the
update-wasi-sdk
branch
from
247fb85 to
8e26944
Compare
Collaborator
|
The job Click to see the possible cause of the failure (guessed by this bot) |
Contributor
rust-bors
bot
added
S-waiting-on-bors
Contributor
|
⌛ Testing commit 8e26944 with merge 55bfca7... Workflow: https://github.com/rust-lang/rust/actions/runs/21750399200 |
rust-bors bot
pushed a commit
that referenced
this pull request
Feb 6, 2026
Update wasi-sdk used in CI/releases This is similar to prior updates such as #149037 in that this is just updating a URL. This update though has some technical updates accompanying it as well, however: * The `wasm32-wasip2` target no longer uses APIs from WASIp1 on this target, even for startup. This means that the final binary no longer has an "adapter" which can help making instantiation of a component a bit more lean. * In #147572 libstd was updated to use wasi-libc more often on the `wasm32-wasip2` target. This uncovered a number of bugs in wasi-libc such as #149864, #150291, and #151016. These are all fixed in wasi-sdk-30 so the workarounds in the standard library are all removed. Overall this is not expected to have any sort of major impact on users of WASI targets. Instead it's expected to be a normal routine update to keep the wheels greased and oiled.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is similar to prior updates such as #149037 in that this is just updating a URL. This update though has some technical updates accompanying it as well, however:
The
wasm32-wasip2target no longer uses APIs from WASIp1 on this target, even for startup. This means that the final binary no longer has an "adapter" which can help making instantiation of a component a bit more lean.In std: Use more
unix.rscode on WASI targets #147572 libstd was updated to use wasi-libc more often on thewasm32-wasip2target. This uncovered a number of bugs in wasi-libc such as std: Don't uselinkaton thewasm32-wasi*targets #149864, std: Useusleeptemporarily on WASI targets #150291, and fix: WASI threading regression by disabling pthread usage #151016. These are all fixed in wasi-sdk-30 so the workarounds in the standard library are all removed.Overall this is not expected to have any sort of major impact on users of WASI targets. Instead it's expected to be a normal routine update to keep the wheels greased and oiled.