[pypy-commit] extradoc extradoc: write something about SPUR

cfbolz noreply at buildbot.pypy.org
Tue Jul 24 11:01:23 CEST 2012


Author: Carl Friedrich Bolz <cfbolz at gmx.de>
Branch: extradoc
Changeset: r4343:c9ebca1a4d82
Date: 2012-07-24 10:49 +0200
http://bitbucket.org/pypy/extradoc/changeset/c9ebca1a4d82/

Log:	write something about SPUR

diff --git a/talk/vmil2012/paper.tex b/talk/vmil2012/paper.tex
--- a/talk/vmil2012/paper.tex
+++ b/talk/vmil2012/paper.tex
@@ -107,7 +107,7 @@
 intermediate and low-level representation of the JIT instructions and how these
 are implemented.
 
-Although there are several publications about tracing jut-in-time compilers, to
+Although there are several publications about tracing just-in-time compilers, to
 our knowledge, there are none that describe the use and implementation of
 guards in this context. With the following contributions we aim to shed some
 light (to much?) on this topic.
@@ -459,6 +459,15 @@
 
 \section{Related Work}
 
+SPUR~\cite{bebenita_spur:_2010} is a tracing JIT compiler
+for a C\# virtual machine.
+It handles guards by always generating code for every one of them
+that transfers control back to the unoptimized code.
+Since the transfer code needs to reconstruct the stack frames
+of the unoptimized code,
+the transfer code is quite large.
+
+
 
 \section{Conclusion}
 


More information about the pypy-commit mailing list