[pypy-commit] extradoc extradoc: explain the "type analysis"
cfbolz
noreply at buildbot.pypy.org
Thu Aug 16 17:53:22 CEST 2012
Author: Carl Friedrich Bolz <cfbolz at gmx.de>
Branch: extradoc
Changeset: r4629:f12857b69262
Date: 2012-08-16 17:10 +0200
http://bitbucket.org/pypy/extradoc/changeset/f12857b69262/
Log: explain the "type analysis"
diff --git a/talk/dls2012/paper.tex b/talk/dls2012/paper.tex
--- a/talk/dls2012/paper.tex
+++ b/talk/dls2012/paper.tex
@@ -457,6 +457,8 @@
\item \lstinline{set} writes to an attribute of an object.
\item \lstinline{guard_class} is a precise type check. It typically precedes
an (inlined) method call and is followed by the trace of the called method.
+ The type that the guard checks for is the one that the variable had during
+ tracing.
\end{itemize}
Method calls in the trace are preceded by a \lstinline{guard_class}
@@ -476,8 +478,7 @@
In general, the paper is over-long on generalities and too short on details.
For example, the description of the basic technique at the beginning of section
5 is the third time the idea is explained at basically the same level of detail
-(the others are in section 2 and section 4). In contrast, the optimizations
-applied rely on a simple type analysis, but this is only briefly alluded to.
+(the others are in section 2 and section 4).
}
Before a trace is passed to the backend compiling it into machine code
More information about the pypy-commit
mailing list