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

Commit id: e9dca87ceea8551978235206f71676a863134d09

deletions | additions      

       

\paragraph{Impact on code quality}  In order to measure how much a never-firing OSR point impacts code quality, we analyzed the code structure of each benchmark and profiled its run-time behavior with gprof to determine the most 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.