ejpbruel

4 ms·

1. 1.▲
   by ejpbruel 2y ago

   Stitch lazily compiles each wasm function to a form of threaded code in which each instruction has multiple variants, depending on where it loads its operands from. Each operand is either stored on the stack (s), a virtual register (r), or
2. 2.▲
   by ejpbruel 2y ago

   That’s a good point! I did’t even think about that. For Stitch to become self hosting, we’d either have to implement those instructions, or implement a fallback mode using an interpreter loop with a trampoline. The latter would negate most
3. 3.▲
   by ejpbruel 2y ago

   I haven’t tried this, but Stitch should technically be able to run itself if we gave it a C-like API that you could export from a Wasm module. Would be fun to try at some point :-)
4. 4.▲
   by ejpbruel 2y ago

   I'm the author of Stitch. Rik is somewhat overpromising: Stitch is only faster than Wasm3 on Windows (by about 15%). On Mac and Linux, it is about as fast. It does get within 4x of Wasmtime (which is the JIT I've compared it again