this is for holding javascript data
Camil Demetrescu edited approach.tex
over 8 years ago
Commit id: 6c931369b4bf45a3cbf2fd0ea6afa71b35831043
deletions | additions
diff --git a/approach.tex b/approach.tex
index e001481..ba11d37 100644
--- a/approach.tex
+++ b/approach.tex
...
Consider the generic OSR scenario shown Figure~\ref{fi:osr-dynamics}. A base function \textsf{f} is executed and it can either terminate normally (dashed lines), or an OSR event may transfer control to a variant \textsf{f'}. The decision of whether an OSR should be fired at a given point \textsf{L} is based on an {\em OSR condition}. A typical example is a guard testing whether a speculative function \textsf{f} has become unsafe and a fallback to a safe version \textsf{f'} is in order. Another example is a profile counter reaching a certain hotness threshold, which indicates that \textsf{f} is taking longer than expected and is worth optimizing.
Classical OSR implementations adjust the stack so that execution can continue in \textsf{f'} with the current frame
\cite{}. \mynote{add citations}. This requires manipulating the program at machine code level and is highly ABI- and compiler-dependent. A simpler approach, which we follow in this paper, consists of creating a new frame every time an OSR is fired, essentially regarding an OSR transition as a function call
\cite{}. \mynote{cite WebKit and McVM}.
%\ref{fi:overview-osr-final}
...