Author: Hakan Ardo <ha...@debian.org>
Branch: extradoc
Changeset: r3719:f4ba9e40e2a4
Date: 2011-06-17 08:04 +0200
http://bitbucket.org/pypy/extradoc/changeset/f4ba9e40e2a4/
Log: started to draft abstract
diff --git a/talk/iwtc11/paper.tex b/talk/iwtc11/paper.tex
--- a/talk/iwtc11/paper.tex
+++ b/talk/iwtc11/paper.tex
@@ -121,7 +121,18 @@
\maketitle
\begin{abstract}
-This is the text of the abstract.
+By introducing loop peeling into the optimization step of a tracing
+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
+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.
\end{abstract}
\category{D.3.4}{Programming Languages}{Processors}[code generation,
_______________________________________________
pypy-commit mailing list
pypy-commit@python.org
http://mail.python.org/mailman/listinfo/pypy-commit
