[pypy-svn] r3538 - pypy/trunk/doc/funding
hpk at codespeak.net
hpk at codespeak.net
Tue Mar 30 22:49:05 CEST 2004
Author: hpk
Date: Tue Mar 30 22:49:04 2004
New Revision: 3538
Modified:
pypy/trunk/doc/funding/B6.7.wp05_translation.txt
Log:
- largely reworked WP05 because the EU is dubious
about the amount of man-month we spent for core
packages.
- *much* more empahsis on research results and publications
- after all they said they don't want to just fund some
opensource developers and we *are* researching new ways
of doing language implementations ...
Modified: pypy/trunk/doc/funding/B6.7.wp05_translation.txt
==============================================================================
--- pypy/trunk/doc/funding/B6.7.wp05_translation.txt (original)
+++ pypy/trunk/doc/funding/B6.7.wp05_translation.txt Tue Mar 30 22:49:04 2004
@@ -36,13 +36,16 @@
Create a code analysis tool for a subset of the Python
language (RPython). Coordinate the definition of RPython
-with WP04_, being the implementation language of the core.
+with WP04_, being the implementation language for most
+of the core. At the core of this task lies the research and
+implementation of full "abstract interpretation" by reusing
+the unmodified PyPy interpreter with a special object space.
**Task 2**
Produce a tool chain, capable of extracting the RPython
byte code from the core, translating it into low-level
-code (C, ...), and compiling it.
+code (with C beeing the primary target) and compiling it.
Use the data gathered in Task 1 to drive the translation
process.
@@ -59,23 +62,31 @@
**Deliverables**
-- D05.1 Tool chain for translating and compiling arbitrary RPython programs
-- D05.2 Release a compiled, self-contained modular version of PyPy
-- D05.3 Publish solved and remaining problems regarding RPython and
+- D05.1 Publish a report about translating a very-high-level description
+ of a language into low level code by building on "abstract interpretation" and
+ PyPy's design in particular.
+- D05.2 Release a compiled, self-contained modular version of PyPy.
+- D05.3 Publish solutions and open challenges regarding the implementation of
memory management/threading models as translation aspects.
+- D05.4 Publish an overview paper about the success of encapsulating low level
+ language aspects as well defined parts of the translation phase.
.. include:: wp-tableend.asc
.. include:: wp-tablebegin.asc
**Milestones and Expected Result**
-- Complete implementation of Python, conforming to the language
- definition and passing all language compliancy [*]_ tests of the official Python test suite.
-
-.. [*] CPython contains some tests that depend on implementation
- details. The exact line between a language feature and an implementation detail
- might at times be hard to draw precisely, but in all cases this only concerns a
- minority of the tests. In case of doubt the original python developers will be
- consulted.
+- Complete implementation of the Python language, conforming to the
+ language definition and passing all language compliancy [*]_ tests of
+ the official Python test suite.
+
+- Research Results on encapsulating low level language aspects as parts
+ of a translation from very-high-level into low-level code.
+
+.. [*] Some of the the many hundred CPython language tests actually test
+ implementation details like e.g. memory management. The exact line
+ between a language feature and an implementation detail is at times
+ hard to draw. In case of doubt the original CPython developers will
+ be consulted for clarification.
.. include:: wp-tableend.asc
More information about the Pypy-commit
mailing list