Stream: wasi

Topic: Is `wasm32-wasi` retired in preference for `wasm32-wasip1`?


view this post on Zulip Brett Cannon (Aug 15 2024 at 18:38):

I currently have https://peps.python.org/pep-0011/ listing CPython's support for wasm32-wasi, but I'm starting to wonder if I should clarify it to be wasm32-wasip1? Is the association of wasm32-wasi always going to be as wasm32-wasip1? And when did the wasm32-wasip1 target become available in the WASI SDK (a quick search at https://github.com/WebAssembly/wasi-sdk/releases didn't show anything)?

This PEP documents how an operating system (platform) becomes supported in CPython, what platforms are currently supported, and documents past support.
WASI-enabled WebAssembly C/C++ toolchain. Contribute to WebAssembly/wasi-sdk development by creating an account on GitHub.

view this post on Zulip Dave Bakker (badeend) (Aug 15 2024 at 18:44):

https://blog.rust-lang.org/2024/04/09/updates-to-rusts-wasi-targets.html

Empowering everyone to build reliable and efficient software.

view this post on Zulip Dave Bakker (badeend) (Aug 15 2024 at 18:44):

To summarize:

wasm32-wasip1 is an effective rename of the existing wasm32-wasi target, freeing the target name up for an eventual WASI 1.0

view this post on Zulip Dave Bakker (badeend) (Aug 15 2024 at 18:45):

To answer your question:

Is the association of wasm32-wasi always going to be as wasm32-wasip1?

No. wasm32-wasi will eventually mean WASI1.0. At least in the Rust world.

view this post on Zulip Brett Cannon (Aug 15 2024 at 19:09):

What about the WASI SDK world?

view this post on Zulip Dave Bakker (badeend) (Aug 15 2024 at 19:24):

Don't know. I assume the intention is to keep them in sync.

when did the wasm32-wasip1 target become available in the WASI SDK

The earliest I can track it down is to: https://github.com/WebAssembly/wasi-libc/commit/c9c7d0616e0f7fe4d0d0fa54372b6d1f5689f91d

I'm starting to wonder if I should clarify it to be wasm32-wasip1?

The commit above mentions "the wasm32-wasi target should transition to wasm32-wasip1", so I'd guess: Yes.

* Start renaming preview1 to p1 and preview2 to p2 This is an initial start at renaming the "preview" terminology in WASI targets to "pX". For example the `wasm32-wasi` targ...

view this post on Zulip Brett Cannon (Aug 15 2024 at 23:01):

Thanks for the links! That suggests wasm32-wasip1 came in as part of WASI SDK 22 which came out mid-April.


Last updated: Dec 23 2024 at 13:07 UTC