Changeset 3140


Ignore:
Timestamp:
Apr 12, 2013, 7:22:08 PM (4 years ago)
Author:
campbell
Message:

Diagram illustrating nested function calls in structured traces.

Location:
Deliverables/D3.4/Report
Files:
2 added
1 edited

Legend:

Unmodified
Added
Removed
  • Deliverables/D3.4/Report/report.tex

    r3138 r3140  
    379379\end{itemize}
    380380
    381 \todo{Nice version of the nested trace diagram from slides}
     381\begin{figure}
     382\begin{center}
     383\includegraphics[width=0.6\linewidth]{strtraces.pdf}
     384\end{center}
     385\caption{Nesting of functions in structured traces}
     386\label{fig:strtrace}
     387\end{figure}
    382388A structured trace is a mutually inductive data type which principally
    383389contains the steps from a normal program trace, but arranged into a
    384390nested structure which groups entire function calls together and
    385391aggregates individual steps between cost labels (or between the final
    386 cost label and the return from the function).  This capture the idea
    387 that the cost labels only represent costs \emph{within} a function ---
    388 calls to other functions are accounted for in the trace for their
    389 execution, and we can locally regard function calls as a single step.
     392cost label and the return from the function), see
     393Figure~\ref{fig:strtrace}.  This capture the idea that the cost labels
     394only represent costs \emph{within} a function --- calls to other
     395functions are accounted for in the trace for their execution, and we
     396can locally regard function calls as a single step.
    390397
    391398These structured traces form the core part of the intermediate results
Note: See TracChangeset for help on using the changeset viewer.