Add wasm32-wasip2 target support #639
Open
+255
−114
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.
Rework of #532 by @nickrum, addressing review feedback from @Darksonn
and @Thomasdezeeuw:
code review feedback)
eliminating 11+ scattered cfg gates (per @Darksonn's concern)
Opt-in cfg patterns use
all(target_os = "wasi", not(target_env = "p1"))to match how the libc crate gates WASI p2 socket support. Opt-out
patterns use bare
target_os = "wasi"for features unavailable on anyWASI version.
WASI tests run in CI with wasmtime (27/27 pass). Tests for unsupported
socket options are gated out with references to the relevant WASI spec
issues (SO_BROADCAST, SO_LINGER, IPV6_V6ONLY).
Closes #268
Based-on: #532
Co-authored-by: Nicola Krumschmidt [email protected]