wasi-sdk-30 release

[alexcrichton]

wasi-sdk-29 was tagged on Nov 14 last year, so we're coming up on ~3 months and it's around the right time for another wasi-sdk release. The current list of changes includes:

• A wasm-component-ld update
  • Handling more flags to forward to wasm-ld
  • A wasm-tools update
    • Support for dedicated imports for unit futures/streams in wasip3
• A wasi-libc update
  • New wasi/version.h header file
  • Refactored wasi/api.h header file (only defines the WASI version for that target)
  • New __wasi_sdk_{major,minor}__ defines
  • Sysroot now has __wasip{1,2,3}__ defines
  • Fix for nanosleep on WASIp2
  • New error code for pthread_create's stub implementation
  • The wasm32-wasip2 target no longer has any dependency on WASIp1 (startup goes through WASIp2, not WASIp1)

The only non-included change I know of in this update is the upgrade to LLVM 22.1.0. That's scheduled for release on February 24.

I'm personally a bit wary of bundling too much in one update to avoid a logjam situation where upgrades for one feature are blocked on a regression for something totally different. Given that I'd personally lean towards doing wasi-sdk-30 before LLVM 22, and then maybe wasi-sdk-31 once LLVM 22 is released.

I wanted to open this issue though to see if others had thoughts too!

[pchickey]

I agree with your judgement that we should get a release out with these changes, which are quite substantial, and not wait to include more. The libc changes, in particular, are major enough that this release feels "risky" in terms of needing bugfixes for the p2 target, compared to most releases.

[cpetig]

I'm generally in favor of more frequent releases!

You didn't mention the underlying libc migration to cmake, that change alone earns a release.

Given that many other bytecodealliance projects migrated to a more automated release process, perhaps the cost for doing an SDK release can be decreased to a negligible level as well.

---- Regarding sdk-31 -----

Concerning wasip3, I think everyone will correctly assume that a current release will be binary incompatible with the final specification because of the pre-release date on the WIT interfaces. But I am concerned if there ever will be a p3 release with the final WIT version it should also include the stack pointer semantic change by Sy on llvm.

In short: Please don't release sdk-31 with an unmodified LLVM 22 (i.e. globals instead of context-get for SP/TLS) and a potential non-dated 0.3.0 WASI. Because such a version would be binary incompatible with any future p3 version in a very non-obvious way.

[alexcrichton]

Ok I've published pre-release artifacts here -- https://github.com/WebAssembly/wasi-sdk/releases/tag/wasi-sdk-30 -- and if no one objects I'll move that to an foficial release in the next day or so.

[alexcrichton]

Published now.

[alexcrichton]

Oh also, @cpetig we should get some folks in a room to chat about the ABI business with wasip3 and LLVM 22 at some point. Or, better yet, actually I'll write up an issue on that soon.