[pypy-svn] r71157 - pypy/trunk/pypy/doc/jit

[benjamin at codespeak.net]

Author: benjamin
Date: Mon Feb  8 03:20:17 2010
New Revision: 71157

Modified:
   pypy/trunk/pypy/doc/jit/pyjitpl5.txt
Log:
kill some xxxs

Modified: pypy/trunk/pypy/doc/jit/pyjitpl5.txt
==============================================================================
--- pypy/trunk/pypy/doc/jit/pyjitpl5.txt	(original)
+++ pypy/trunk/pypy/doc/jit/pyjitpl5.txt	Mon Feb  8 03:20:17 2010
@@ -31,8 +31,8 @@
 the JIT to bail back to the interpreter in case running machine code is no
 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
+interpreter defines its hints in pypy/module/pypyjit/interp_jit.py in a few
+overriden methods of the defaut interpreter loop.
 
 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,9 +98,8 @@
 for optimization purposes, are also stored in constant boxes.  Normal boxes
 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
+boxes: ConstInt, ConstPtr, ConstFloat, and ConstAddr.  (ConstAddr is only used
+to get around a limitation in the translation toolchain.)
 
 The meta-interpreter starts interpreting the JIT bytecode.  Each operation is
 executed and then recorded in a list of operations, called the trace.