[pypy-svn] extradoc extradoc: try to take the best of both versions

[cfbolz]

Author: Carl Friedrich Bolz <cfbolz at gmx.de>
Branch: extradoc
Changeset: r3468:a2cff55ff6da
Date: 2011-04-04 16:55 +0200
http://bitbucket.org/pypy/extradoc/changeset/a2cff55ff6da/

Log:	try to take the best of both versions

diff --git a/talk/icooolps2011/paper.tex b/talk/icooolps2011/paper.tex
--- a/talk/icooolps2011/paper.tex
+++ b/talk/icooolps2011/paper.tex
@@ -147,10 +147,9 @@
 In this paper we present two of these hints that are extensively used in the
 PyPy project to improve the performance of its Python interpreter. 
 
-% XXX: paragraph rephrased by anto; feel free to pick the one you like best
-
-Conceptually, it is possible to achieve significant speed-ups by feeding into
-the compiler some information that is observed at runtime: in particular, if
+Conceptually, the significant speed-ups that can be achieved with
+dynamic compilation depend on feeding into compilation and exploiting
+values observed at runtime. In particular, if
 there are values which vary very slowly, it is possible to compile multiple
 specialized versions of the same code, one for each actual value.  To exploit
 the runtime feedback, the implementation code and data structures need to be
@@ -158,13 +157,6 @@
 we present allow exactly to implement such feedback and exploitation in a
 meta-tracing context.
 
-% Conceptually the significant speed-ups that can be achieved with
-% dynamic compilation depend on feeding into compilation and exploiting
-% values observed at runtime that are slow-varying in practice. To exploit the
-% runtime feedback, the implementation code and data structures need to be
-% structured so that many such values are at hand. The hints that we present allow
-% exactly to implement such feedback and exploitation in a meta-tracing context.
-
 Concretely these hints are used to control how the optimizer of the
 tracing JIT can improve the traces of the object model. More
 specifically, these hints influence the constant folding
@@ -442,7 +434,7 @@
 in static compilers it is significantly less applicable.
 
 Promotion is essentially a tool for trace specialization. There are places in
-the interpreter where knowing that a value if constant opens a lot of
+the interpreter where knowing that a value is constant opens a lot of
 optimization opportunities, even though it
 could have different values in practice. In such a place, promotion is used. The
 typical reason to do that is if there is
@@ -643,7 +635,7 @@
 side effects, because it changes the memoizing dictionary. However, because this side
 effect is not externally visible, the function from the outside is pure. This is
 a property that is not easily detectable by analysis. Therefore, the purity
-of this function needs to be manually annotated.
+of this function needs to be annotated manually.