This perl5 jitter is super-simple, and modeled after B::CC
The compiled perl5 optree is a linked list in memory in non-execution order,
wide-spread jumps. Additionally the calls are indirect. The jitter properly
aligns the run-time calls in linear linked-list "exec" order, so that the CPU
can prefetch the next instructions, and it inlines some simple ops.
op_next targets (returned by false condit
v0.03 2010-08-09 rurban
Start with amd64/x86_64
Include seperate CPU threaded/non-threaded c files
Create run-jit.c and run-jit.o with .stabs when DEBUGGING
Refactor (maybranch) into jit_chain which runs twice to
support branches eventually - ops which do not return op_next
seperate tests, only 1.t works
v0.02 2010-08-06 rurban
Found the i386 call bug with rafl's help - "use stepi"