%0 Conference Paper %1 Bolz:2009:TMP %A Bolz, Carl Friedrich %A Cuni, Antonio %A Fijalkowski, Maciej %A Rigo, Armin %B Proceedings of the 4th Workshop on the Implementation, Compilation, Optimization of Object-Oriented Languages and Programming Systems %D 2009 %I ACM %K JIT MetaTracing PyPy Python RPython compiler %P 18--25 %R 10.1145/1565824.1565827 %T Tracing the Meta-level: PyPy's Tracing JIT Compiler %X We attempt to apply the technique of Tracing JIT Compilers in the context of the PyPy project, i.e., to programs that are interpreters for some dynamic languages, including Python. Tracing JIT compilers can greatly speed up programs that spend most of their time in loops in which they take similar code paths. However, applying an unmodified tracing JIT to a program that is itself a bytecode interpreter results in very limited or no speedup. In this paper we show how to guide tracing JIT compilers to greatly improve the speed of bytecode interpreters. One crucial point is to unroll the bytecode dispatch loop, based on two kinds of hints provided by the implementer of the bytecode interpreter. We evaluate our technique by applying it to two PyPy interpreters: one is a small example, and the other one is the full Python interpreter. %@ 978-1-60558-541-3

@inproceedings{Bolz:2009:TMP, abstract = {We attempt to apply the technique of Tracing JIT Compilers in the context of the PyPy project, i.e., to programs that are interpreters for some dynamic languages, including Python. Tracing JIT compilers can greatly speed up programs that spend most of their time in loops in which they take similar code paths. However, applying an unmodified tracing JIT to a program that is itself a bytecode interpreter results in very limited or no speedup. In this paper we show how to guide tracing JIT compilers to greatly improve the speed of bytecode interpreters. One crucial point is to unroll the bytecode dispatch loop, based on two kinds of hints provided by the implementer of the bytecode interpreter. We evaluate our technique by applying it to two PyPy interpreters: one is a small example, and the other one is the full Python interpreter.}, acmid = {1565827}, added-at = {2014-01-14T14:50:03.000+0100}, author = {Bolz, Carl Friedrich and Cuni, Antonio and Fijalkowski, Maciej and Rigo, Armin}, biburl = {https://www.bibsonomy.org/bibtex/2cf89f436e7185e839253cb2e720de7e9/gron}, booktitle = {Proceedings of the 4th Workshop on the Implementation, Compilation, Optimization of Object-Oriented Languages and Programming Systems}, description = {Tracing the meta-level}, doi = {10.1145/1565824.1565827}, interhash = {03ec6ed22d7f3dd5cca0f193f225b775}, intrahash = {cf89f436e7185e839253cb2e720de7e9}, isbn = {978-1-60558-541-3}, keywords = {JIT MetaTracing PyPy Python RPython compiler}, location = {Genova, Italy}, numpages = {8}, pages = {18--25}, publisher = {ACM}, series = {ICOOOLPS '09}, timestamp = {2014-01-14T14:50:03.000+0100}, title = {Tracing the Meta-level: PyPy's Tracing JIT Compiler}, year = 2009 }