Author: Carl Friedrich Bolz <[email protected]>
Branch: extradoc
Changeset: r4558:6a6c5c66028e
Date: 2012-08-14 13:06 +0200
http://bitbucket.org/pypy/extradoc/changeset/6a6c5c66028e/

Log:    cite Self debugging paper

diff --git a/talk/vmil2012/paper.tex b/talk/vmil2012/paper.tex
--- a/talk/vmil2012/paper.tex
+++ b/talk/vmil2012/paper.tex
@@ -876,13 +876,16 @@
 
 Deutsch et. al.~\cite{deutsch_efficient_1984} describe the use of stack 
descriptions
 to make it possible to do source-level debugging of JIT-compiled code.
-Self uses deoptimization to reach the same goal~\cite{XXX}.
+Self uses deoptimization to reach the same goal~\cite{holzle_debugging_1992}.
 When a function is to be debugged, the optimized code version is left
 and one compiled without inlining and other optimizations is entered.
 Self uses scope descriptors to describe the frames
 that need to be re-created when leaving the optimized code.
-The scope descriptors are between 0.45 and 0.76 times
+The scope descriptors are between 0.42 and 1.09 times
 the size of the generated machine code.
+All the information needed for debugging together
+is between 1.22 and 2.33 times the size of generated machine code,
+according to the paper.
 
 Java Hotspot~\cite{paleczny_java_2001} contains a deoptimization framework 
that is used
 for debugging and when an uncommon trap is triggered.
_______________________________________________
pypy-commit mailing list
[email protected]
http://mail.python.org/mailman/listinfo/pypy-commit

Reply via email to