[pypy-svn] rev 2635 - pypy/trunk/doc/overview

jacob at codespeak.net jacob at codespeak.net
Sat Dec 20 12:01:15 CET 2003


Author: jacob
Date: Sat Dec 20 12:01:14 2003
New Revision: 2635

Removed:
   pypy/trunk/doc/overview/RPy-translation-overview.txt
Log:
Removed original RPython translation chapter.

Deleted: /pypy/trunk/doc/overview/RPy-translation-overview.txt
==============================================================================
--- /pypy/trunk/doc/overview/RPy-translation-overview.txt	Sat Dec 20 12:01:14 2003
+++ (empty file)
@@ -1,22 +0,0 @@
-RPython translation overview
--------------------------------
-
-Translation of RPython code of PyPy works on bytecode as found in the
-interpreter functions object after the PyPy system has been loaded and
-initialized. These bytecodes will be abstractly interpreted using the
-PyPy interpreter itself with a specific Object Space, the Flow Object
-Space, plugged in. The Flow Object Space drives the execution in such
-a way that all paths in the code are followed. As a side-effect it
-produces flow graphs, that means graph capturing the control flow of
-the code, nodes there are basic blocks of logged Object Space
-operations executed sequentially, how values flow is also encoded.
-
-These flow graphs can then be fed as input to the Annotator. Under the
-constraints of RPython, the Annotator given entry point types infers
-the types of values that flow through the program variables.
-
-In the last phase the type annotated flow graphs are visited by the
-Translator, which out of the types annotation, the basic block listed
-operations and control flow information encoded in the graphs, emits
-"low-level" code. Our first target will probably be Pyrex code, which
-is then translated to compilable C by Pyrex itself.


More information about the Pypy-commit mailing list