[pypy-svn] r63176 - pypy/extradoc/talk/pycon2009/vm-summit

[fijal at codespeak.net]

Author: fijal
Date: Sat Mar 21 14:47:59 2009
New Revision: 63176

Modified:
   pypy/extradoc/talk/pycon2009/vm-summit/picture.svg
   pypy/extradoc/talk/pycon2009/vm-summit/slides.txt
Log:
the way how I see it


Modified: pypy/extradoc/talk/pycon2009/vm-summit/picture.svg
==============================================================================
--- pypy/extradoc/talk/pycon2009/vm-summit/picture.svg	(original)
+++ pypy/extradoc/talk/pycon2009/vm-summit/picture.svg	Sat Mar 21 14:47:59 2009
@@ -14,7 +14,10 @@
    sodipodi:version="0.32"
    inkscape:version="0.46"
    sodipodi:docname="picture.svg"
-   inkscape:output_extension="org.inkscape.output.svg.inkscape">
+   inkscape:output_extension="org.inkscape.output.svg.inkscape"
+   inkscape:export-filename="/home/fijal/lang/python/pypy-dist/extradoc/talk/pycon2009/vm-summit/picture.png"
+   inkscape:export-xdpi="90"
+   inkscape:export-ydpi="90">
   <metadata
      id="metadata409">
     <rdf:RDF>

Modified: pypy/extradoc/talk/pycon2009/vm-summit/slides.txt
==============================================================================
--- pypy/extradoc/talk/pycon2009/vm-summit/slides.txt	(original)
+++ pypy/extradoc/talk/pycon2009/vm-summit/slides.txt	Sat Mar 21 14:47:59 2009
@@ -2,63 +2,49 @@
 PyPy - Motivation 
 =================================
 
-* **high level Python specification** (in RPyhton) 
+.. image:: picture.png
+   :scale: 50
+   :align: center
 
-* layer GCs, JIT, Stackless atop the spec 
+High level specification - how exactly
+=======================================
 
-* **generate** efficient interpreters for targets 
+* in our opinion specification that cannot be run
+  is not worth it
 
-.. (antocuni) I would say "generate efficient VMs", not "interpreters"
+* Python is high level enough
 
+* We derived a static subset of Python that can be
+  efficiently compiled, called RPython
 
-.. image:: pypy-multitarget.png
-   :scale: 50
-   :align: center
+XXX show mario
 
-RPython - two words 
-==========================
+Garbage Collection framework
+====================================
 
-- RPython is a subset of Python, used in a static way
-- whole-program type-inference
-- GCs, threading, stackless applied as graph transforms
-- you can implement other languages or VMs in RPython
+* Written in Python
 
+* We introduced a bunch of low-level primitives
 
-Virtual Machine translation! 
-==========================================
+* We can test a GC on top of Python (running specification)
 
-.. image:: mario.png
-   :scale: 100
-   :align: center
+* ... and translate to a target
 
-Next-generation Garbage Collection
-====================================
+* Completely interpreter-agnostic
 
-- currently: naive Mark&Compact  (600 lines of code) 
-- port/implement newer techniques (e.g. deferred refcounting) 
-- even more compact GC headers 
-- malloc-directed inlining 
-- maximize shared interpreter state 
-- co-operate with kernel in swapping/collect situations
-
-PyPy's GC framework
-===================================
-
-- program your GC in Python 
-- test your GC in Python 
-- get Python tracebacks instead of segfaults
-- once ready, translate with Python Interpreter 
+XXX show a piece of code in GC
 
 
 Generating JIT Compilers
 ========================================
 
+* We apply JIT generator to specification
 
-Current Challenges
-======================
+* A couple of manual hints is required
 
-* generate a working JIT-compiling Python Interpreter 
-* PyPy 1.1 release 
-* more extension modules, C++ bindings? 
-* split into multiple projects 
+* We can try on top of Python as well
+
+Challenges
+======================
 
+XXX out of time I suppose