Update wasi-sdk used in CI/releases#152183
Merged
Merged
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.