[LLVMbugs] [Bug 469] NEW: JIT benchmark ho-humming / just how deep is the LLVM rabbit-hole

[bugzilla-daemon at cs.uiuc.edu]

http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=469

           Summary: JIT benchmark ho-humming / just how deep is the LLVM
                    rabbit-hole
           Product: libraries
           Version: trunk
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Common Code Generator Code
        AssignedTo: unassignedbugs at nondot.org
        ReportedBy: duraid at octopus.com.au


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:

<Chris> 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... ;)



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.