[Python-Dev] A new JIT compiler for a faster CPython? (original) (raw)
Alex Gaynor alex.gaynor at gmail.com
Fri Jul 20 17:01:56 CEST 2012
- Previous message: [Python-Dev] A new JIT compiler for a faster CPython?
- Next message: [Python-Dev] A new JIT compiler for a faster CPython?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
That's not, strictly speaking, true. Mozilla added a method-JIT (Jaegermonkey) and then added another one (IonMonkey) because their tracing JIT (Tracemonkey) was bad. There's no fundamental reason that tracing has to only cover loops, indeed PyPy's tracing has been generalized to compile individual functions, recursion, etc. And any profiling JIT, in practice, needs a compile heuristic for how many calls must occur before a unit is compiled, even the Hotspot JVM has one.
Alex
- Previous message: [Python-Dev] A new JIT compiler for a faster CPython?
- Next message: [Python-Dev] A new JIT compiler for a faster CPython?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]