this is for holding javascript data
Camil Demetrescu edited overview.tex
over 8 years ago
Commit id: 8e907cd1405a8947c3e0d060728e5d54c400e681
deletions | additions
diff --git a/overview.tex b/overview.tex
index 6ac9363..7696a7f 100644
--- a/overview.tex
+++ b/overview.tex
...
\begin{enumerate}
\item {\em Platform independence}: the OSR instrumentation code is lowered to native code by the compiler backend, which handles the details of the target ABI;
\item {\em Global optimizations}: lowering OSR instrumentation code along with the application code can generate faster code than local binary instrumentation. For instance, dead code elimination can suppress from \fosrto\ portions of code that would no longer be needed when jumping to the landing pad \textsf{L'}, producing smaller code and enabling better register allocation and instruction scheduling.
\item {\em Debugging and Profiling}: preserving ABI conventions in the native code versions of \fosrfrom, \fstub, and \fosrto\ helps debuggers and profilers
to more precisely locate the current execution context and collect more informative data.
%avoiding low-lever tampering with stack frames can more easily preserve ABI calling conventions
\item {\em Abstraction}: the approach is amenable to a clean instrumentation API that abstracts the OSR implementation details, allowing a front-end to focus on where to insert OSR points independently
on of the final target architecture.
%by analyzing code at an intermediate representation level.
\end{enumerate}
...