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

Commit id: f33f58d3dea1ed179163bd027b58fdc093b37abb

deletions | additions      

       

\end{itemize}  \paragraph{Impact on code quality}  In order to measure how much a never-firing OSR point impacts code quality, for each benchmark  we analyzed the its  code structureof each benchmark  and profiled its run-time behavior with gprof to determine the most critical performance-critical  sections for OSR point insertion. For recursive benchmarks ({\tt binary-trees} and {\tt spectral-norm}), we insert an OSR point in the body of the hottest method (i.e., the one accounting for the largest {\em self} execution time) of the program. For iterative benchmarks, we insert an OSR point on loops that are responsible for the largest fraction of cumulative invocations of the hottest method.