Hi Pierrick, thank you for the feedback. > first, congrats for this work! > It would be really nice to have this available upstream, starting with a > modest TCI port, before having the tcg backend also.
Sure, I'll split the patch series, starting with the TCI port. > Do you have recent information about wasm64? It seems to be something > that has been discussed for several years, without really seeing any > progress. According to the adoption status [1], wasm64 is supported by recent versions of Chrome and Firefox. Emscripten also supports wasm64 [2]. However, it is not yet supported by Safari or libffi [3], and I haven't found a roadmap for the adoption. [1] https://webassembly.org/features/ [2] https://emscripten.org/docs/tools_reference/settings_reference.html#memory64 [3] https://github.com/libffi/libffi/blob/6a99edb8082f75e523e0d6ebaba42218b80e10c8/README.md#supported-platforms > As Philippe said, we can't really revert that (it's now an assumption > for our softmmu implementation, and would break code if we enabled it > again now.) > > That said, we can always have a first version supporting only 32 bits > targets. And later, when wasm64 will be available, we can extend this to > all remaining ones. The main challenge I'm seeing is that I couldn't find a clear timeline for wasm64 adoption so it's difficult to predict when it will be widely available. Regarding the revert, the wasm backend supports 64-bit words, so the revert introduced in patch 06/10 is partial, as also pointed out by Paolo.
