Daniele Cono D'Elia edited experim.tex  over 8 years ago

Commit id: 8b9507d5a7e9db542158de598db78341815c0a23

deletions | additions      

       

For recursive benchmarks, we insert an OSR point in the body of the method that accounts for the largest {\em self} execution time of the program. Such an OSR point might enable recompilation of the invoked method at a higher degree of optimization, [...]  In the shootout benchmarks, ({\tt binary-trees} and {\tt spectral-norm}) show a recursive pattern.  \begin{figure}[b]  \center\includegraphics[width=0.65\textwidth]{figures/code-quality-noBB.eps}  \vspace{-2mm}  \caption{Impact on running time of never-firing OSR points inside hot code portions.}  \label{fig:code-quality}  \end{figure}