Author: David Schneider <david.schnei...@picle.org> Branch: extradoc Changeset: r4459:b5406b13a6a6 Date: 2012-08-07 14:37 +0200 http://bitbucket.org/pypy/extradoc/changeset/b5406b13a6a6/
Log: (cfbolz, bivab) write about bridges and trace stitching diff --git a/talk/vmil2012/paper.tex b/talk/vmil2012/paper.tex --- a/talk/vmil2012/paper.tex +++ b/talk/vmil2012/paper.tex @@ -296,6 +296,9 @@ to create a trace tree. When that happens another use case of resume data is to construct the tracer state. +After the bridge has been recorded and compiled it is attached to the guard. +If the guard fails later, the bridge is executed. Therefore the resume data of +that guard is no longer needed. There are several forces guiding the design of resume data handling. Guards are a very common operations in the traces. @@ -416,16 +419,6 @@ of the delayed stores to be able to perform them when the guard fails. So far no special compression is done with this information. -% subsection Interaction With Optimization (end) -\subsection{Compiling Side-Exits and Trace Stitching} % (fold) -\label{sub:Compiling side-exits and trace stitching} - * tracing and attaching bridges and throwing away resume data - * restoring the state of the tracer - * keeping virtuals - * compiling bridges -\todo{maybe mention that the failargs also go into the bridge} - -% subsection Compiling side-exits and trace stitching (end) % section Resume Data (end) \begin{figure} @@ -560,12 +553,6 @@ \caption{Trace control flow in case of guard failures with and without bridges} \label{fig:trampoline} \end{figure} -%* Low level handling of guards -% * Fast guard checks v/s memory usage -% * memory efficient encoding of low level resume data -% * fast checks for guard conditions -% * slow bail out -% % section Guards in the Backend (end) %___________________________________________________________________________ _______________________________________________ pypy-commit mailing list pypy-commit@python.org http://mail.python.org/mailman/listinfo/pypy-commit