Author: Armin Rigo <ar...@tunes.org>
Branch: 
Changeset: r53975:8ae92dbdda48
Date: 2012-03-25 14:23 +0200
http://bitbucket.org/pypy/pypy/changeset/8ae92dbdda48/

Log:    Complete.

diff --git a/pypy/doc/you-want-to-help.rst b/pypy/doc/you-want-to-help.rst
--- a/pypy/doc/you-want-to-help.rst
+++ b/pypy/doc/you-want-to-help.rst
@@ -58,10 +58,15 @@
 
 * Just-in-Time Compiler (JIT): `we have a tracing JIT`_ that traces the
   interpreter written in RPython, rather than the user program that it
-  interprets.  As a result it applies to any interpreter, i.e. any language.
-  But getting it to work correctly is not trivial: it requires a small
-  number of precise "hints" and possibly some small refactorings of the
-  interpreter.
+  interprets.  As a result it applies to any interpreter, i.e. any
+  language.  But getting it to work correctly is not trivial: it
+  requires a small number of precise "hints" and possibly some small
+  refactorings of the interpreter.  The JIT itself also has several
+  almost-independent parts: the tracer itself in ``jit/metainterp``, the
+  optimizer in ``jit/metainterp/optimizer`` that optimizes a list of
+  residual operations, and the backend in ``jit/backend/<machine-name>``
+  that turns it into machine code.  Writing a new backend is a
+  traditional way to get into the project.
 
 .. _`we have a tracing JIT`: jit/index.html
 
_______________________________________________
pypy-commit mailing list
pypy-commit@python.org
http://mail.python.org/mailman/listinfo/pypy-commit

Reply via email to