Jeff Parsons (Jan 20 2026 at 02:40): Jeff Parsons (Jan 20 2026 at 02:40):Hi there,
I'm working on a "WASI-native" programming language with pervasive suspension (and structured concurrency with cleanup guarantees to make that not a nightmare), targeting bleeding edge draft specs for various Wasm proposals. I based my concurrency story on the stack switching proposal, and then realised it's currently only implemented for x86_64.
Is an implementation for aarch64 or Pulley on anyone's radar? I'm just trying to decide whether to write my own hacks or wait until I can try stack switching on my own machine.
Thanks! :sparkling_heart:
Ralph (Jan 20 2026 at 09:09):radar, absolutely.
Jeff Parsons (Jan 20 2026 at 09:33):Maybe I should ask "is anyone funded to work on it within the next few quarters, or expecting to be?"
Chris Fallin (Jan 20 2026 at 16:37):at least from my point of view, unfortunately no (too many other priorities). IIRC, stack switching on x86-64 still needs a bit more work (there's at least one missing opcode, resume_throw) too. If you or anyone else has the ability to put work into it, that'd be much appreciated!
Jeff Parsons (Jan 21 2026 at 00:51):Thank you, that is very helpful information.
Re me getting involved, I'll take a look but I suspect it'll be a lot more than I can manage at the moment. (My discretionary "programming" currently looks like ideation on the train on days I'm working then handing off to Claude between getting the kids to sleep and passing out myself. I don't think you want that sort of code in Cranelift or Wasmtime... :sweat_smile:)
Paul Osborne (Jan 28 2026 at 22:32):While I did a spike on stack switching last year, it isn't currently at the top of my priorities at the moment either. I do hope to, in the relative near term, land some final bits that never to add additional test coverage that never landed with the original set of patches but otherwise don't think it will be a focus area for me in the next several months.
Last updated: Jan 29 2026 at 13:25 UTC