[pypy-svn] r77898 - pypy/extradoc/talk/pepm2011

[cfbolz at codespeak.net]

Author: cfbolz
Date: Thu Oct 14 11:18:31 2010
New Revision: 77898

Modified:
   pypy/extradoc/talk/pepm2011/escape-tracing.pdf
   pypy/extradoc/talk/pepm2011/paper.tex
Log:
two things from samuele, regen pdf


Modified: pypy/extradoc/talk/pepm2011/escape-tracing.pdf
==============================================================================
Binary files. No diff available.

Modified: pypy/extradoc/talk/pepm2011/paper.tex
==============================================================================
--- pypy/extradoc/talk/pepm2011/paper.tex	(original)
+++ pypy/extradoc/talk/pepm2011/paper.tex	Thu Oct 14 11:18:31 2010
@@ -469,8 +469,7 @@
     comparison (``greater than''), respectively.
 \end{itemize}
 
-Note how the functions that are called by \lstinline{f} are automatically inlined
-into the trace. The method calls are always preceded by a \lstinline{guard_class}
+The method calls in the trace are always preceded by a \lstinline{guard_class}
 operation, to check that the class of the receiver is the same as the one that
 was observed during tracing.\footnote{\lstinline{guard_class} performs a precise
 class check, not checking for subclasses.} These guards make the trace specific
@@ -549,6 +548,9 @@
 
 \subsection{Static Objects}
 
+XXX add a footnote saying that "static" is meant in the sense of PE, not static
+allocation
+
 The main insight to improve the code shown in the last section is that objects
 in category 1 don't survive very long -- they are used only inside the loop and
 nobody else in the program stores a reference to them. The idea for improving