Measure: JIT compilation time

[GoogleCodeExporter]

We should measure how long execution blocks for when sending a code object
to be compiled/optimized by LLVM. This will be useful for proving that
offloading compilation/optimization to worker threads is valuable.

- These times should be stored in a vector and statistics displayed at
Python-shutdown.
- This should be a special build (ie, controlled by #ifdef's).
- Timing done using TSCs?

Original issue reported on code.google.com by collinw on 30 May 2009 at 1:39

[GoogleCodeExporter]

As a side-effect of working on the function call overhead timings (issue 46), I
managed to get that data.  I compute it and then subtract it from the time it 
took to
call the function, because that drives up the average function call overhead so 
much
I need to take it out.

Original comment by reid.kle...@gmail.com on 4 Jun 2009 at 6:48

[GoogleCodeExporter]

Original comment by collinw on 4 Jun 2009 at 6:50

• Changed state: Started

[GoogleCodeExporter]

Fixed in r611.

Original comment by collinw on 5 Jun 2009 at 7:23

• Changed state: Fixed