News for hackers. Stuff that matters.
Re:PyPy 2.0 Released by cglace on Thursday May 09, 2013 @04:46PM (#5682847)
Do you mean can you save the state of the JIT for future use?
Re:PyPy 2.0 Released by rubinelli on Thursday May 09, 2013 @05:08PM (#5682955)
Yeah. Can you? Considering CPython already generates .pyc and checks timestamps, keeping some kind of JIT cache around wouldn't be a stretch.
Re:PyPy 2.0 Released by kingkilr on Thursday May 09, 2013 @05:39PM (#5683138)
No, the state of the JIT cannot be saved between executions.
Re:PyPy 2.0 Released by gcr on Thursday May 09, 2013 @09:36PM (#5684043)
I can't speak for python, but I do know that the impact of translating code for Racket's JIT (provided by GNU lightning, not LLVM) is negligable (ie. takes less time than the time you gain by JITting