this is for holding javascript data
Daniele Cono D'Elia edited experim.tex
over 8 years ago
Commit id: 81c8af8feaf3e2dbf74e94d4e2c793feb4e9b088
deletions | additions
diff --git a/experim.tex b/experim.tex
index 0da429d..65747cf 100644
--- a/experim.tex
+++ b/experim.tex
...
\ifauthorea{\newline}{}
\paragraph{OSR Machinery Generation.}
We now discuss the overhead of the \osrkit\ library for inserting OSR machinery in the IR of a function. \mytable\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. Locations for OSR points are chosen as in the experiments about code
quality. quality, and the target function is a clone of the source function.
For open OSR points, we report the time spent in inserting the OSR point in the 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.
Not surprisingly, constructing a continuation function takes longer than the other operations (i.e., up to 1 ms vs. 20-40 us), as it involves cloning and manipulating the body of the target function
- in this case, the source function itself - as described in Section {\bf XXX}; as the required time and thus depends on
the size of the function, its size. For this reason, the table
also contains a comes with an additional column in which time is normalized against the number of IR
instructions in the function. instructions.
\begin{table}
\begin{small}