[pypy-svn] rev 1318 - pypy/trunk/doc/funding
tismer at codespeak.net
tismer at codespeak.net
Tue Sep 16 13:17:47 CEST 2003
Author: tismer
Date: Tue Sep 16 13:17:46 2003
New Revision: 1318
Modified:
pypy/trunk/doc/funding/B6.wp04_bootstrapping_pypy.txt
Log:
going to split this one into two working packages.
There are two major tasks which have little to do with
each other.
Modified: pypy/trunk/doc/funding/B6.wp04_bootstrapping_pypy.txt
==============================================================================
--- pypy/trunk/doc/funding/B6.wp04_bootstrapping_pypy.txt (original)
+++ pypy/trunk/doc/funding/B6.wp04_bootstrapping_pypy.txt Tue Sep 16 13:17:46 2003
@@ -21,46 +21,21 @@
Title: Bootstrapping PyPy
- Putting interpreter (WP01_, WP02_) and translator (WP03_) together.
-
-- Ability to translate arbitrary RPython source code (e.g.
- the one produced in WP01_ into low-level code (C, Pyrex, Java, others).
-- Creation of a stand-alone, not-PyPy-related tool for general
- optimization of arbitrary but suitably restricted Python application or
- parts thereof.
+- Enhancing the PyPy Design.
**Description of work**
-
-
-**Deliverables**
-
-
-
-**Milestones and Expected Result**
-
-*XXX: This check-in is just temporary*
-
-The interpreter is written as an RPython program. The translator
-has to translate this program into some low-level language.
-The resulting program then needs to be supported by a special
-runtime library. The work-flow of WP04_ is repetitive,
-since it will not be possible to "get it right" in the
-first attempt. Analysis and redesign will have to be
-repeated until the result is satisfactory.
**Part a): Specific Analysis and Redesign**
-The global translation of PyPy is going to raise particular
-problems, other than more general RPython programs do.
-Since translation of RPython is the core idea of the
-bootstrap process and the main target of the translator,
-we need to investigate and isolate the
-particular problems, and redesign specific parts of PyPy
-to support translation, code generation and optimzation
-better. This will also include a re-iteration of the interface
-design between application level and interpreter level
-until we reach overall convergence.
+- Investigate the particular problems that the
+ global translation of PyPy is going to raise.
+- Enhance and redesign parts of PyPy as needed
+ to give best support to the translation of RPython.
+- Re-iterate this until we agree to have reached
+ an optimum solution.
+
**Part b): Low Level PyPy Runtime**
@@ -75,3 +50,11 @@
If producing C code is a target, important
parts can be directly re-used from CPython.
+
+
+**Deliverables**
+
+
+
+**Milestones and Expected Result**
+
More information about the Pypy-commit
mailing list