Luke Gorrie

@tst2005 You are welcome to experiment with preprocessing and/or metaprogramming features on a branch and make that available for other people to merge :) The nearest example that I can...

Thanks for the great comment @dormando! I'll respond soon and use this as input for the next README overhaul that is probably due about now.

> How you you embed raptorJIT into a C app? Just answering this directly now. It's not covered in the README but we do this in Snabb and the Makefile...

> Compilers have gotten a bit better and computers have gotten better at running bad code, so the C VM doesn't seem too scary. My only problem here is these...

@nico-abram Support for more platforms and architectures should follow naturally once we have finished ported the VM from assembler to C (wip on #254.) Help on that would be great,...

Great case study and write-up!

Just fwiw, the simplified way that I read examples like this is to say: - The JIT will compile each inner loop separately. - Called functions are effectively copy-pasted (inlined)...

The XL710 is a sore point at the moment. Everybody wants it, quite a few people are willing to put some work into the development, we have plenty of hardware...

Current status is that the VM can reach the REPL since f6c1012. This only exercises one bytecode (`FUNCC`) and a few primitives like `vm_call()`, `vm_cpcall()`, `vm_return()`, and `vm_cpuid()`. This code...

Hey hey hey! The [C VM code in lj_vm.c](https://github.com/raptorjit/raptorjit/blob/479caf36450b012b7c3796958b2a0a0dad35d78c/src/lj_vm.c) is really starting to come along! I'm now able to run a really trivial program: ``` $ raptorjit -e 'for i...