[pypy-svn] r21896 - in pypy/extradoc/talk/chalmers: . image

arigo at codespeak.net arigo at codespeak.net
Tue Jan 10 18:35:20 CET 2006


Author: arigo
Date: Tue Jan 10 18:35:17 2006
New Revision: 21896

Added:
   pypy/extradoc/talk/chalmers/image/pipe-title.jpg   (contents, props changed)
   pypy/extradoc/talk/chalmers/image/py-web1.png
      - copied unchanged from r21895, pypy/extradoc/talk/chalmers/py-web1.png
Removed:
   pypy/extradoc/talk/chalmers/py-web1.png
Modified:
   pypy/extradoc/talk/chalmers/talk-wm2006.txt
Log:
Added the conclusion.  Minor tweaks.


Added: pypy/extradoc/talk/chalmers/image/pipe-title.jpg
==============================================================================
Binary file. No diff available.

Modified: pypy/extradoc/talk/chalmers/talk-wm2006.txt
==============================================================================
--- pypy/extradoc/talk/chalmers/talk-wm2006.txt	(original)
+++ pypy/extradoc/talk/chalmers/talk-wm2006.txt	Tue Jan 10 18:35:17 2006
@@ -10,7 +10,7 @@
 :Author: Armin Rigo
 :URL: http://codespeak.net/pypy
 
-.. image:: py-web1.png
+.. image:: image/py-web1.png
    :align: right
 
 
@@ -53,7 +53,7 @@
 Translation Overview
 =========================
 
-.. image:: translation-overview.png
+.. image:: image/translation-overview.png
    :align: center
 
 Translation Aspects
@@ -68,7 +68,7 @@
 Translation Aspects (2)
 =========================
 
-- the execution stragegy can be tweaked at translation time too
+- the execution strategy can be tweaked at translation time too
 - if the input RPython program is an Interpreter_...
 - ...the output low-level program can be a Compiler_
 
@@ -92,42 +92,52 @@
 
 - translation aspect
 
-:input:
-    PyPy Interpreter written in RPython
+:input:         PyPy Interpreter written in RPython
+:normal output: an Interpreter -- like CPython
+:new output:    a Compiler -- like Psyco
 
-:prev output:
-    an Interpreter -- like CPython
 
-:new output:
-    a Compiler -- like Psyco
-
-
-Recipe for a JIT
+Recipe for a JIT (1)
 ==========================
 
-- JIT part 1: high level, language dependent
-- JIT part 2: platform-specific code generation and optimizations
-- separation of concerns
-
-PyPy JIT part 1
-==========================
+JIT Part 1: high level, language dependent
 
 - generated as translation aspect from PyPy Interpreter
 - stays in sync with the evolution of the language
+- separation of concerns
 - same technique works for other languages
 
-PyPy JIT part 2
-=========================
+Recipe for a JIT (2)
+==========================
+
+JIT Part 2: platform-specific code generation and optimizations
 
 - no cross-platform code generation toolkit
 - needs to be manually rewritten for each platform
 - orthogonal to the source language
 - can reuse existing code generation and optimization projects
 
-Conclusion
+Summary
+=========================
+
+- don't port new languages to new platforms manually
+- manually port general translation toolsuites
+- start from high-level Language Definitions
+- regenerate Interpreters automatically
+- get Just-In-Time Compilers for free :-)
+
+For More Information
 =========================
 
-XXX
+- http://codespeak.net/pypy
+
+  .. image:: image/py-web1.png
+     :align: center
+
+- http://psyco.sf.net
+
+  .. image:: image/pipe-title.jpg
+     :align: center
 
 
 .. _Psyco: http://psyco.sourceforge.net



More information about the Pypy-commit mailing list