this is for holding javascript data
Daniele Cono D'Elia edited experim.tex
over 8 years ago
Commit id: 2ff7cab270b18a462f0bb899ccf5e88f4c611847
deletions | additions
diff --git a/experim.tex b/experim.tex
index d0aa783..5e1bdf5 100644
--- a/experim.tex
+++ b/experim.tex
...
\paragraph{OSR machinery generation}
We now discuss the overhead of the library for the insertion of OSR machinery in the IR of a function. Table~\ref{tab:instrTime} reports for each benchmark the number of IR instructions in the instrumented function, the number of live values to transfer and the time spent in the IR manipulation.
For open OSR points, we report the time spent in inserting the OSR point in the original function and in generating the stub; both operations do not depend on the size of the function. For resolved OSR points, we report the time spent in inserting the OSR point and in generating the continuation function.
The latter operation is the most expensive, as it involves cloning and manipulating the body of the target function - that is the source function itself - as described in Section {\bf XXX}; for this reason, the table also contains a column in which time is normalized against the number of IR instructions in the function.
OSR point insertion
Not surprisingly, generating this function is more expensive than the other operations, as it involves cloning and manipulating the body of the target function - that is the source function itself - as described in Section {\bf XXX}; as the time spent in it depends on the size of the function, the table contains an additional column in which time is normalized against the number of IR instructions in it.
\begin{table}
\begin{small}
...
\end{small}
\end{table}
%\paragraph{Discussion} \paragraph{Discussion}