Author: Hakan Ardo <[email protected]>
Branch: extradoc
Changeset: r3721:c402e451d800
Date: 2011-06-17 08:28 +0200
http://bitbucket.org/pypy/extradoc/changeset/c402e451d800/
Log: clairify
diff --git a/talk/iwtc11/paper.tex b/talk/iwtc11/paper.tex
--- a/talk/iwtc11/paper.tex
+++ b/talk/iwtc11/paper.tex
@@ -122,14 +122,15 @@
\begin{abstract}
By introducing loop peeling into the optimization step of a tracing
-jit, the effect of optimizations already in place will be increased
+jit the effect of optimizations already in place will be increased
greatly. Not only will they become able to move loop invariant code
out of loop. They will also become able to reuse results from the
previous iteration. Also, the implementation of excising optimizations
can be left almost intact as they will not have to interact much with
the loop peeling.
-Several benchmarks executed on the PyPy python JIT show over 2
+Several benchmarks, with few guard failures, executed on the
+PyPy python JIT show over 2
times increase in speed when loop peeling was introduced. This makes
some of them almost match optimized C performance and become over XXX
times faster than cpython.
_______________________________________________
pypy-commit mailing list
[email protected]
http://mail.python.org/mailman/listinfo/pypy-commit
