Tracing the Meta-Level: PyPy's Tracing JIT Compiler

More documents

Recommendations

Info

Implementation Issues I ◮ JIT should not be integrated, but added during C translation ◮ interpretation of language interpreter is bad → double-interpretation overhead ◮ instead run language interpreter as a C program ◮ on nding a hot loop in user program start tracing ◮ use current state to trace bytecode representation ◮ needs machine- and bytecode version in executable of VM
Implementation issues II ◮ on failing a guard, fall back to normale interpretation ◮ problem: hard to rebuild state in the middle of execution ◮ fallback deep in the code needs a deep C stack ◮ solution: use fallback interpreter ◮ ◮ ◮ variant of langugage interpreter without tracing run until a safe point is reached where it is easy to resume operation in C version happens after at most one bytecode operation
Page 1 and 2: Tracing the Meta-Level: PyPy's Trac
Page 3 and 4: Introduction What We want to do ◮
Page 5 and 6: The PyPy project Advantages for wri
Page 7 and 8: Tracing JIT compilers ◮ initially
Page 9 and 10: Tracing JIT compilers What should b
Page 11 and 12: Tracing JIT compilers Tracing JIT P
Page 13 and 14: Applying a Tracing JIT to an Interp
Page 23: Improving the Result II ◮ if oper
Page 27 and 28: Evaluation PyPy ◮ PyPy with JIT i
Page 29 and 30: Related Work Piumarta and Riccardi
Page 31 and 32: Related Work Partial Evaluation ◮
Page 33 and 34: Related Work Dynamic Partial Evalua

Tracing the Meta-Level: PyPy's Tracing JIT Compiler

Create successful ePaper yourself

Delete template?

Save as template?