[pypy-svn] r80286 - pypy/extradoc/talk/ustour2011

hpk at codespeak.net hpk at codespeak.net
Fri Feb 4 21:59:16 CET 2011


Author: hpk
Date: Fri Feb  4 21:59:13 2011
New Revision: 80286

Modified:
   pypy/extradoc/talk/ustour2011/mozilla-abstract.txt
Log:
* factoring out "RPython" into a leading sentence
* focusing a bit more on the jit-generation for interpreters
  bit as it also represents the main research result
  (which is now a practical one)


Modified: pypy/extradoc/talk/ustour2011/mozilla-abstract.txt
==============================================================================
--- pypy/extradoc/talk/ustour2011/mozilla-abstract.txt	(original)
+++ pypy/extradoc/talk/ustour2011/mozilla-abstract.txt	Fri Feb  4 21:59:13 2011
@@ -10,13 +10,17 @@
 * the real-world PyPy compiler toolchain itself (200 KLocs) runs twice as fast
 * full compatibility to CPython (more than Jython/IronPython)
 
-In this talk we will focus on how we reached this goal:
+In this talk we will focus on how we reached this goal in a truly
+ouroboros manner by implementing many pieces in RPython, a subset
+of Python that our toolchain analyzes and compiles to C:
 
-* "RPython", a subset of Python that our toolchain analyzes and compiles to C
-* our Python interpreter is written in RPython
-* pluggable GCs, also written in RPython
-* JIT support automatically generated from the interpreter source code
-* the JIT itself is also written in RPython
+* our Python interpreter
+* pluggable GCs
+* the JIT itself, including x86/ARM backends
+
+The translation toolchain itself is written in full Python (not RPython!)
+and generates JIT support automatically from the interpreter source code,
+thereby reducing complexity for writing state-of-the-art interpreters.
 
 There are many interesting details that can be explored further;
 we will focus on the points the audiance is most interested in.



More information about the Pypy-commit mailing list