[pypy-svn] r68802 - pypy/branch/gc-dump-heap/pypy/doc/jit

fijal at codespeak.net fijal at codespeak.net
Wed Oct 28 09:20:23 CET 2009

Author: fijal
Date: Wed Oct 28 09:20:21 2009
New Revision: 68802

Leave a couple of XXXs. optimization phase is not complete

Modified: pypy/branch/gc-dump-heap/pypy/doc/jit/pyjitpl5.txt
--- pypy/branch/gc-dump-heap/pypy/doc/jit/pyjitpl5.txt	(original)
+++ pypy/branch/gc-dump-heap/pypy/doc/jit/pyjitpl5.txt	Wed Oct 28 09:20:21 2009
@@ -32,6 +32,7 @@
 longer suitable.  can_enter_jit goes at the end of a application level loop.  In
 the Python interpreter, this is the JUMP_ABSOLUTE bytecode.  The Python
 interpreter defines its hints in pypy/module/pypyjit/interp_jit.py.
+XXX by overloading default frame behavior from pyframe
 The interpreter wishing to use the PyPy's JIT must define a list of *green*
 variables and a list of *red* variables.  The *green* variables are loop
@@ -98,6 +99,8 @@
 contain values that may change during the running of a loop.  There are three
 kinds of normal boxes: BoxInt, BoxPtr, and BoxFloat, and four kinds of constant
 boxes: ConstInt, ConstPtr, ConstFloat, and ConstAddr.
+XXX ConstAddr is only a hack for translation not to translate pointers,
+XXX nothing more
 The meta-interpreter starts interpreting the JIT bytecode.  Each operation is
 executed and then recorded in a list of operations, called the trace.

More information about the Pypy-commit mailing list