Author: Samuele Pedroni <[email protected]> Branch: extradoc Changeset: r4554:d1cc6d00c04d Date: 2012-08-13 22:46 +0200 http://bitbucket.org/pypy/extradoc/changeset/d1cc6d00c04d/
Log: clarify/streamline diff --git a/talk/vmil2012/paper.tex b/talk/vmil2012/paper.tex --- a/talk/vmil2012/paper.tex +++ b/talk/vmil2012/paper.tex @@ -135,12 +135,11 @@ are used in the intermediate and low-level representation of the JIT instructions and how these are implemented. -The goal of this paper is to understand the design constraints when +Our aim is to help understand the design constraints when implementing guards. Guards have a runtime cost, they take time to execute. On the other hand, guards are possible deoptimization points, meaning the recorded -and compiled path has to be left returning control to the interpreter. They need to -store -enough information to rebuild the interpreter state. +and compiled path has to be left returning control to the interpreter. They need +enough associated information to enable rebuilding the interpreter state. Based on the informal observation that guards are among the most common operations in the traces produced by RPython's tracing JIT, our goal is to present concrete numbers for the frequency and the overhead related _______________________________________________ pypy-commit mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-commit
