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

[tismer at codespeak.net]

Author: tismer
Date: Tue Sep 16 18:24:59 2003
New Revision: 1329

Added:
   pypy/trunk/doc/funding/B6.wp06_several_obj_impl.txt
   pypy/trunk/doc/funding/B6.wp08_integrate_technology.txt
Modified:
   pypy/trunk/doc/funding/B6.1_plan_introduction.txt
   pypy/trunk/doc/funding/B6.wp07_translator_optimisations.txt
   pypy/trunk/doc/funding/crossreferences.asc
Log:
Added and (hopefully) finished WP08.

Modified: pypy/trunk/doc/funding/B6.1_plan_introduction.txt
==============================================================================
--- pypy/trunk/doc/funding/B6.1_plan_introduction.txt	(original)
+++ pypy/trunk/doc/funding/B6.1_plan_introduction.txt	Tue Sep 16 18:24:59 2003
@@ -175,8 +175,7 @@
 to use reference counting together with garbage collection,
 or whether to go for garbage collection, only.
 
-For each issue, work on **several solutions** when no one is obviously
-better than the other ones. The meta-programming underlying WP07_
+The meta-programming underlying WP07_
 -- namely the work on the translator instead of on the resulting code -- is
 what gives us the possibility of actually implementing several very
 different schemes. The outcome of this effort is of course not unique,
@@ -187,7 +186,6 @@
 
 - optimization towards minimal code size for embedded systems.
 
-*add a lot more about this*
 
 WP08_: Integration of Existing Technology
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -212,12 +210,8 @@
 Stackless Python and should enable PyPy for load-balancing
 between different machines.
 
-Rewrite each one as a meta-component that hooks into the
-translator plus a dedicated run-time component (WP05_). Further
-develop these technologies based on the results gathered in WP07_,
-e.g. identify when these technologies would guide specific
-choices among the solutions developed in WP05_ and studying
-several solutions in WP06_.
+Both will be rewritten as a meta-component that hooks into the
+translator plus a dedicated run-time component (WP05_).
 
 
 *XXX The following paragraph is not clear to me,

Added: pypy/trunk/doc/funding/B6.wp06_several_obj_impl.txt
==============================================================================
--- (empty file)
+++ pypy/trunk/doc/funding/B6.wp06_several_obj_impl.txt	Tue Sep 16 18:24:59 2003
@@ -0,0 +1,58 @@
+.. include:: crossreferences.asc
+
+Workpackage Description
+========================
+
+================================ ==========================
+**Workpackage number**            06
+-------------------------------- --------------------------
+**Start date or starting event**    0
+================================ ==========================
+
+================================= ======= ======= ======= ======= ======= ======= ======= =======
+**Participant id**                   X       Y    
+--------------------------------- ------- ------- ------- ------- ------- ------- ------- -------
+**Person-months per participant**    2       2   
+================================= ======= ======= ======= ======= ======= ======= ======= =======
+
+
+**Objectives**
+
+Title: Several Object Implementations
+
+- Providing several object implementations for
+  - general optimisation
+  - application specific alternatives
+
+
+**Description of work**
+
+The following objects are mostly independent from any particular low-level run-time 
+environment.
+
+* Implement dictionaries as hash-table vs. plain (key, value) lists vs. b-trees, 
+  or with string-only or integer-only keys. Dictionaries with specific 
+  support for "on-change" callbacks (useful for Psyco).
+
+* Implement strings as plain immutable memory buffers vs. immutable but more 
+  complex data structures (see functional languages) vs. internally 
+  mutable data structures (e.g. Psyco's concatenated strings)
+
+* Implement ints as machine words vs. two machine words vs. internal longs vs. 
+  external bignum library (investigate if completely unifying ints and
+  longs is possible in the Python language at this stage).
+
+* Consider further objects and do multiple implementations of them.
+
+* Run various performance tests on the above, check for an
+  overall improvement or application dependency.
+  
+* Create reports and merge the results back into the optimization effort.
+  As of general interest, submit the reports as publication.
+
+**Deliverables**
+
+DL??? to be defined. Publication.
+
+**Milestones and Expected Result**
+

Modified: pypy/trunk/doc/funding/B6.wp07_translator_optimisations.txt
==============================================================================
--- pypy/trunk/doc/funding/B6.wp07_translator_optimisations.txt	(original)
+++ pypy/trunk/doc/funding/B6.wp07_translator_optimisations.txt	Tue Sep 16 18:24:59 2003
@@ -46,6 +46,9 @@
   
 * Run various performance tests on the above, check for an
   overall improvement or application dependency.
+
+* For each issue, work on **several solutions** when no one is obviously
+  better than the other ones. 
   
 * Create reports and merge the results back into the optimization effort.
   As of general interest, submit the reports as publication.

Added: pypy/trunk/doc/funding/B6.wp08_integrate_technology.txt
==============================================================================
--- (empty file)
+++ pypy/trunk/doc/funding/B6.wp08_integrate_technology.txt	Tue Sep 16 18:24:59 2003
@@ -0,0 +1,66 @@
+.. include:: crossreferences.asc
+
+Workpackage Description
+========================
+
+================================ ==========================
+**Workpackage number**            08
+-------------------------------- --------------------------
+**Start date or starting event**    0
+================================ ==========================
+
+================================= ======= ======= ======= ======= ======= ======= ======= =======
+**Participant id**                   AR      CT      X 
+--------------------------------- ------- ------- ------- ------- ------- ------- ------- -------
+**Person-months per participant**    4       2       2
+================================= ======= ======= ======= ======= ======= ======= ======= =======
+
+
+**Objectives**
+
+Title: Integration of Existing Technology
+
+- Integration of Psyco's technology into PyPy.
+  - Optimization by Creating Specialized Machine Code at Run-time.
+  - Adressing new Processor Architectures
+- Integration of Stackless's technology into PyPy.
+  - Enable Massive Parallelism in a Single Thread
+  - Allow Pickling of a running Program
+
+
+**Description of work**
+
+
+- Determine which parts of Psyco need to be written in RPython.
+
+- Design Psyco as a meta-component
+  that hooks into the translator (WP03_)
+
+- Implement Psyco partially in RPython, partially in Python,
+  favoring the latter.
+  
+- Implement a dedicated run-time component (WP05_) for Psyco.
+
+
+
+- Determine which parts of Stackless need to be written in RPython.
+
+- Design Stackless as a meta-component
+  that hooks into the translator (WP03_)
+
+- Implement Stackless partially in RPython, partially in Python,
+  favoring the latter.
+  
+- Implement a dedicated run-time component (WP05_) for Stackless.
+
+- Further develop these technologies based on the results gathered in WP07_, 
+  e.g. identify when these technologies would guide specific choices among the 
+  solutions developed in WP05_ and studying several solutions in WP06_.
+
+
+**Deliverables**
+
+DL??? to be defined. Speed boost, architectures, green threads, pickling.
+
+**Milestones and Expected Result**
+

Modified: pypy/trunk/doc/funding/crossreferences.asc
==============================================================================
--- pypy/trunk/doc/funding/crossreferences.asc	(original)
+++ pypy/trunk/doc/funding/crossreferences.asc	Tue Sep 16 18:24:59 2003
@@ -4,6 +4,5 @@
 .. _WP04: B6.wp04_bootstrap_redesign.html
 .. _WP05: B6.wp05_bootstrap_runtime.html
 .. _WP06: B6.wp06_several_obj_impl.html
-.. _WP07: 
-.. _WP08: 
-.. attention:: **2 files missing: WP07 WP08**
+.. _WP07: B6.wp07_translator_optimisations.html
+.. _WP08: B6.wp08_integrate_technology.html