[pypy-commit] extradoc extradoc: improvements to guards in the frontend section

[bivab]

Author: David Schneider <david.schneider at picle.org>
Branch: extradoc
Changeset: r4545:4bebc3e52c25
Date: 2012-08-13 16:22 +0200
http://bitbucket.org/pypy/extradoc/changeset/4bebc3e52c25/

Log:	improvements to guards in the frontend section

diff --git a/talk/vmil2012/paper.tex b/talk/vmil2012/paper.tex
--- a/talk/vmil2012/paper.tex
+++ b/talk/vmil2012/paper.tex
@@ -313,7 +313,7 @@
 
 Since tracing linearizes control flow by following one concrete execution,
 the full control flow of a program is not observed.
-The possible points of deviation from the trace are guard operations
+The possible points of deviation from the trace are denoted by guard operations
 that check whether the same assumptions observed while tracing
 still hold during execution.
 Similarly, in the case of dynamic languages guards can also encode type
@@ -411,7 +411,7 @@
 If the same guard is encountered a second time in the trace,
 the second one can be removed.
 This also works if a later guard is weaker
-and hence implied by a earlier guard.
+and hence implied by an earlier guard.
 
 One of the techniques in the optimizer specific to tracing for removing guards
 is guard strengthening~\cite{bebenita_spur:_2010}.
@@ -467,7 +467,7 @@
 compared to the other source of information delayed heap stores are quite rare.
 
 Figure~\ref{fig:trace-log} shows the optimized version of the trace in
-Figure~\ref{fig:fig:unopt-trace}. Allocation removal has removed the
+Figure~\ref{fig:unopt-trace}. Allocation removal has removed the
 \lstinline{new} operation and other operations handling the instance. The
 operations handle unboxed numbers now.