[pypy-svn] rev 1312 - pypy/trunk/doc/funding

tismer at codespeak.net tismer at codespeak.net
Mon Sep 15 20:34:34 CEST 2003


Author: tismer
Date: Mon Sep 15 20:34:34 2003
New Revision: 1312

Added:
   pypy/trunk/doc/funding/B6.wp03_translation_of_rpython.txt
Log:
Added new working package.

Added: pypy/trunk/doc/funding/B6.wp03_translation_of_rpython.txt
==============================================================================
--- (empty file)
+++ pypy/trunk/doc/funding/B6.wp03_translation_of_rpython.txt	Mon Sep 15 20:34:34 2003
@@ -0,0 +1,58 @@
+.. include:: crossreferences.txt
+
+Workpackage Description
+========================
+
+================================ ==========================
+**Workpackage number**            03
+-------------------------------- --------------------------
+**Start date or starting event**    0
+================================ ==========================
+
+================================= ======= ======= ======= ======= ======= ======= ======= =======
+**Participant id**                   X       Y    
+--------------------------------- ------- ------- ------- ------- ------- ------- ------- -------
+**Person-months per participant**    3        3   
+================================= ======= ======= ======= ======= ======= ======= ======= =======
+
+
+**Objectives**
+
+Title: Translation of RPython
+
+- 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.
+
+
+**Description of work**
+
+**Part a): Code Analysis**
+
+- Analyse code to produce the relevant typing information.
+- Investigate whether we can use the annotation object space
+  only or if additional AST-based control flow analysis is needed.
+- Give a formal definition of RPython.
+
+**Part b): Code Production**
+
+- Produce low-level code out of the data gathered in Part a).
+- Again investigate how this is best done (AST-guided translation or
+  reverse-engeneering of the low-level control flow gathered by the
+  annotation object space).
+- Compare different low-level environments that
+  we could target (C, Pyrex, others?).
+- Provide some measure for the efficiency of the generated
+  code, in comparison to Standard Python.
+
+**Deliverables**
+
+- DL02: Stand-alone Python Interpreter
+- DL03: Tool for Analysis of restricted Python Programs
+
+**Milestones and Expected Result**
+
+- Initial Complete Self-COntained PyPy Interpreter
+- Initial Measures of Efficiency


More information about the Pypy-commit mailing list