Is there any plan to support --target=wasm64-wasi ?

[renxuqiang]

when --target=wasm64-wasi will be supported?

[vshymanskyy]

Duplicate of #185

[sunfishcode]

Yes, everything in LLVM's wasm support and wasi-libc was written with wasm64 in mind, so it's just a matter of hooking up the pieces and making sure things actually work.

[AnatolyBuga]

Nooby question: building a code which uses f64s to wasm32-wasi - Would that lead to errors/unexpected behaviour or is that fine?

[sunfishcode]

f64 is perfectly fine with wasm32-wasi. i64 is fine too.

[abrown]

wasm64-wasi in wasi-sdk could use some help: if anyone is interested in working on this feel free to pick this up.

[sunfishcode]

The guidance from the WASI Subgroup is that wasm64-wasi should now target WASI 0.2, so the path forward here now looks like:

• Support for 64-bit pointers and lengths in the Canonical ABI. I'm optimistic this will happen fairly soon.
• Implement the 64-bit Canonical ABI in wit-bindgen.
• Support for WASI 0.2 in wasi-libc, which is underway (Update bindings and dependencies to WASI 0.2.0 wasi-libc#471 and others).
• Once the above are done, add a wasm64-wasi target to wasi-libc.

[lum1n0us]

Support for 64-bit pointers and lengths in the Canonical ABI.

Could u share more about that? It seems there are no new comments in WebAssembly/component-model#22 for monthes.

[sunfishcode]

The CanonicalABI change will be conceptually straightforward; things like the size function need to be aware that a list has a pointer and a length, and so on.

bytecodealliance/wit-bindgen#870 gets wit-bindgen a step closer to memory64 support. Beyond this, its size/etc. functions also need to know that a list has a pointer and a length.