[pypy-commit] extradoc extradoc: fix reference
cfbolz
noreply at buildbot.pypy.org
Fri Sep 7 11:13:32 CEST 2012
Author: Carl Friedrich Bolz <cfbolz at gmx.de>
Branch: extradoc
Changeset: r4776:c0241f2dd33d
Date: 2012-09-07 11:09 +0200
http://bitbucket.org/pypy/extradoc/changeset/c0241f2dd33d/
Log: fix reference
diff --git a/talk/vmil2012/paper.bib b/talk/vmil2012/paper.bib
--- a/talk/vmil2012/paper.bib
+++ b/talk/vmil2012/paper.bib
@@ -28,3 +28,18 @@
note = {\url{http://lua-users.org/lists/lua-l/2009-11/msg00089.html}}
}
+
+ at inproceedings{bebenita_trace-based_2010,
+ address = {Vienna, Austria},
+ title = {Trace-based compilation in execution environments without interpreters},
+ isbn = {978-1-4503-0269-2},
+ url = {http://portal.acm.org/citation.cfm?id=1852761.1852771},
+ doi = {10.1145/1852761.1852771},
+ abstract = {Trace-based compilation is a technique used in managed language runtimes to detect and compile frequently executed program paths. The goal is to reduce compilation time and improve code quality by only considering "hot" parts of methods for compilation. Trace compilation is well suited for interpreter-based execution environments because the control flow of an application program is highly visible and recordable. In this paper, we show that trace compilation is also feasible and beneficial in runtime environments without interpreters where it is more difficult to monitor the control flow of an application.},
+ booktitle = {Proceedings of the 8th International Conference on the Principles and Practice of Programming in {Java}},
+ publisher = {{ACM}},
+ author = {Bebenita, Michael and Chang, Mason and Wagner, Gregor and Gal, Andreas and Wimmer, Christian and Franz, Michael},
+ year = {2010},
+ keywords = {{Java}, just-in-time compilation, optimization, ssa form, trace-based compilation, trace regions},
+ pages = {59--68}
+},
diff --git a/talk/vmil2012/paper.tex b/talk/vmil2012/paper.tex
--- a/talk/vmil2012/paper.tex
+++ b/talk/vmil2012/paper.tex
@@ -141,7 +141,7 @@
Tracing just-in-time (JIT) compilers record and compile commonly executed
linear control flow paths consisting of operations executed by an
interpreter.\footnote{There are also virtual machines that have a tracing JIT
-compiler and do not use an interpreter~\cite{xxx}. This paper assumes that the
+compiler and do not use an interpreter~\cite{bebenita_trace-based_2010}. This paper assumes that the
baseline is provided by an interpreter. Similar design constraints would apply
to a purely compiler-based system.}
At points of possible divergence from the traced path operations called guards
More information about the pypy-commit
mailing list