JIT should write bytes more efficiently, allow machine code deallocation, allow growing code buffer #841
Labels
bugzilla
Issues migrated from bugzilla
enhancement
Improving things as opposed to bug fixing, e.g. new or missing feature
mcjit
slow-compile
Extended Description
I'm using LLVM as a JIT engine, from a simple C++ driver (interpreter, actually).
It creates lots of code, and I recently clocked it at ~10,000 cycles per byte
of code generated. This is just a place-holder for now (sorry for the noise) but
I'll add concrete figures/profiling data as I get around to doing proper tests.
I also intend to hack up a simple benchmark that I can port across LLVM, Parrot
and libjit, just to see how they compare (in terms of MB/sec of x86 emitted for
some simple test case)
I'd appreciate it if anyone in the know would brain-dump any odd JIT
performance-related TODOs here. I'm aware of other bugzilla enteries, but I'll
kick off yet another entry here with a comment from Chris the other day:
we were just talking today about how the MachineCodeEmitter interface
needs to be changed to not use a virtual method dispatch per byte
Will paypal $1 to whoever fixes this. How's that for incentive! ;)
10,000 clocks is a lot you guys... ;)
The text was updated successfully, but these errors were encountered: