It is definitely not "just" a JIT compiler. For example, you can't just copy QEMU's JIT solution and hope that it works. So I'm interested in your solution. Fo

It is definitely not "just" a JIT compiler. For example, you can't just copy QEMU's JIT solution and hope that it works. So I'm interested in your solution. For example, do you compile each code block (from jump to jump instruction) into a separate WebAssembly module? If yes, then I wonder how many millions of small WebAssembly modules a browser can handle, how well the foreign function interface between JavaScript and WebAssembly actually performs and how much of the time the Browser JIT spends in compiling your generated code. How do you handle machine code manipulation during execution for example? How do you mark already compiled memory pages as dirty. I will definitely look at your code :-) > WRT speed advantage: compared to what? The speed advantage between interpreted and JIT compiled execution.