this is for holding javascript data
Daniele Cono D'Elia edited case-study.tex
over 8 years ago
Commit id: a973c655f36740ce06fd169966449a425a2a2ddc
deletions | additions
diff --git a/case-study.tex b/case-study.tex
index b178fb8..9b6c2f8 100644
--- a/case-study.tex
+++ b/case-study.tex
...
We integrated our analysis pass in McVM's analysis manager. In particular, we group \feval\ instructions whose first argument is reached by the same definition, and for each group we mark for instrumentation only instructions not dominated by others, so that the function can be optimized as early as possible at run-time. The analysis pass is also able to determine whether the value of the argument can change across two executions of the same \feval\ instruction, thus discriminating when a run-time guard must be inserted during the run-time optimization phase.
When the IIR compiler processes an annotated \feval\ instruction, it keeps track of the current {\em variable map} between IIR and IR objects, the {\tt llvm::BasicBlock*} created for the \feval\ and the {\tt llvm::Value*} object used as its first argument. The last two elements are then used by the inserter component as basic block and {\tt val} argument
for in the open-OSR
stub, which stub that invokes the optimizer
component we are about to present. component.
\newcommand{\gbase}{$g$}
\newcommand{\gOpt}{$g_{opt}$}