input language (frequently c/c++) -> wasm -> VM. All modern browsers have a jitting VM availble. Once loaded into the VM, usually, but not a requirement, a jitting VM then compiles it into native code. The WASM itself is not well optimized as it assumes the VM target will itself compile and optimize it into native code.
For my own use, I have used clang C++ -> WASM -> custom/compress WASM -> Custom WASM VM interpreter, for an embedded target. Thus no jitted VM.
Fascinating do you think it's actually viable to make a native / cross browser app in c++? or does c in the browser through webassembly have too many significant limitations?
I know good performance is possible but as my experience is far outside of browsers I can't speak to your expectations.
(post is archived)