[pypy-svn] r18507 - pypy/extradoc/sprintinfo/paris

[tismer at codespeak.net]

Author: tismer
Date: Wed Oct 12 19:33:41 2005
New Revision: 18507

Modified:
   pypy/extradoc/sprintinfo/paris/stackless-workplan.txt
Log:
status of the group

Modified: pypy/extradoc/sprintinfo/paris/stackless-workplan.txt
==============================================================================
--- pypy/extradoc/sprintinfo/paris/stackless-workplan.txt	(original)
+++ pypy/extradoc/sprintinfo/paris/stackless-workplan.txt	Wed Oct 12 19:33:41 2005
@@ -5,19 +5,23 @@
 People:
 -------
 
+    Christian, Armin 
+    Valentino, Amaury 
+    Adrien, Anders 
+
 
 
 improving / refactoring
 -----------------------
 
-- (Valentino, Amaury, Armin) move stack check out of stackless.h, let it
+- DONE (Valentino, Amaury, Armin) move stack check out of stackless.h, let it
   either unwind or raise RuntimeError
   
-- (Valentino, Amaury, Armin) always use automatic stack check detection
+- DONE (Valentino, Amaury, Armin) always use automatic stack check detection
   by default, and test:
   
-  - test_annotated.test_recursion_detection()
-  - pypy-c running CPython´s test_builtins.py
+  - DONE test_annotated.test_recursion_detection()
+  - (progressing) pypy-c running CPython´s test_builtins.py
 
 - DONE (Valentino, Amaury) make Stacklessness a translate_pypy option
 
@@ -25,24 +29,31 @@
   a stand-alone target (which is not obvious)
   
   - done by adding some comment into targetrpystonedalone.py.
-    Where else should we put this information?
+    Where else should we put this information? 
+    targetnopstandalone.py too.
 
 performance evaluation
 ----------------------
 
-- merge stackless support and exception handling
+- (thinking) merge stackless support and exception handling
   to produce just one if clause. Use small test
   programs to measure the effect (see below).
 
-- (Anders, Chris) write smaller stand-alone applications
+- DONE (Anders, Chris) write smaller stand-alone applications
   (rpystone, richards), provide benchmark
   
-- check the effect of false branch predicition
+- DONE (Adrien) check the effect of false branch predicition
   (if slp_frame_stack_bottom etc.)
+
+  - the result appears to be identical, regardless how we
+    spell the conditionals :-(
+
+::
+    if(!RPyExceptionOccured()) {} else FAIL();
   
-- instrument generated code to provide statistics
+- (progressing) instrument generated code to provide statistics
 
-  - do some source ordering by frequency. See thoughts about
+  - (waiting) do some source ordering by frequency. See thoughts about
     this in the chapter to come, below.