[pypy-svn] r18530 - pypy/extradoc/sprintinfo

cfbolz at codespeak.net cfbolz at codespeak.net
Fri Oct 14 11:33:05 CEST 2005

Author: cfbolz
Date: Fri Oct 14 11:33:03 2005
New Revision: 18530

work planning for today

Modified: pypy/extradoc/sprintinfo/paris-2005-planning.txt
--- pypy/extradoc/sprintinfo/paris-2005-planning.txt	(original)
+++ pypy/extradoc/sprintinfo/paris-2005-planning.txt	Fri Oct 14 11:33:03 2005
@@ -14,9 +14,26 @@
 from 1pm, so if somebody wants to work in the afternoon, he has to
 go to one of the small rooms)
-pairing wednesday
+pairing friday
+Compiler issues: adrien, arre
+ootypes: boris, michael, bert, (arre), (armin), (samuele)
+LLinterpreter requirements + plan: carl, holger, (armin), (samuele)
+compliancy testing on compiled PyPy, getting py.test to run on compiled PyPy:
+    anders, {christian}, [armin]
+- (improve refcounting)
+implementing the socket module: amaury, valentino
+working on an RPython Numeric module: ludovic, andrew
+experiment with callgraph analysis to reorder source code: Christian
 stackless/cps:   (same group continues, "re-"pairing inside)
     christian, armin 

Modified: pypy/extradoc/sprintinfo/paris-2005-possible-tasks.txt
--- pypy/extradoc/sprintinfo/paris-2005-possible-tasks.txt	(original)
+++ pypy/extradoc/sprintinfo/paris-2005-possible-tasks.txt	Fri Oct 14 11:33:03 2005
@@ -16,13 +16,13 @@
 JIT related work
-- support addresses in the backends
+- (DONE) support addresses in the backends
 - an ll interpreter written in RPython
 - Saving ll graphs plus a loader written in RPython
 - Start thinking/experimenting with JIT generation at translation time
-- start a genasm back-end
+- (DONE the starting) start a genasm back-end
@@ -30,12 +30,12 @@
 - release the GIL around system calls
 - understand and possibly fix where the overhead, when threads are enabled, comes from
-- generating (single-threaded) stackless C code
+- (DONE) generating (single-threaded) stackless C code
-- stack overflow detection (needed to be able to run many compliancy tests)
+- (somewhat DONE) stack overflow detection (needed to be able to run many compliancy tests)
 - try more interp. level optimisations (dicts with string keys, more agressive use of fastcall*...)
 - compute correct max stack size in compiler (?)

More information about the Pypy-commit mailing list