Andrew Brown

This issue is open for anyone to work on: from what I can tell, it would involve modifying the CI workflow, the CI scripts, and (perhaps) the Makefile.

For [wasi-sdk-21](https://github.com/WebAssembly/wasi-sdk/releases/tag/wasi-sdk-21), I thought about this a bit: on the one hand, whatever scripts are out there have probably adapted to this inconsistency so "fixing" it might actually break other...

I think what is going on here is that the `version.sh` script is appending an `m` to the version because the Git directory is changed: https://github.com/WebAssembly/wasi-sdk/blob/c891cd2036d5630e67826f70aec9c0ba117c67e9/version.sh#L4 I don't know why...

Yeah, that would be great! (cc: @yamt or @eloparco who had a similar comment about this recently, IIRC).

This is pretty cool!

For the threads-related code, you might need to use the `wasm32-wasi-threads` target and the wasi-sdk-20+threads pre-release.

I don't see anyone working on this too closely at the moment: are you interested in adding support for `wasm64-wasi`?

There's been some work already on that in https://github.com/WebAssembly/wasi-libc/pull/444 but there are concerns about how that is implemented so I think some discussion is needed. @loganek is also interested in...

@sbc100, do you think this is still an issue?

Yeah, I think leaving it open as a feature request is fine.