[pypy-svn] r60582 - pypy/extradoc/talk/ecoop2009

antocuni at codespeak.net antocuni at codespeak.net
Thu Dec 18 18:02:37 CET 2008


Author: antocuni
Date: Thu Dec 18 18:02:34 2008
New Revision: 60582

Modified:
   pypy/extradoc/talk/ecoop2009/benchmarks.tex
   pypy/extradoc/talk/ecoop2009/jitgen.tex
   pypy/extradoc/talk/ecoop2009/tlc.tex
Log:
answer to a comment, insert another one, fix a typo



Modified: pypy/extradoc/talk/ecoop2009/benchmarks.tex
==============================================================================
--- pypy/extradoc/talk/ecoop2009/benchmarks.tex	(original)
+++ pypy/extradoc/talk/ecoop2009/benchmarks.tex	Thu Dec 18 18:02:34 2008
@@ -241,7 +241,7 @@
 \anto{maybe we should move the following paragraph to
   abstract/introduction/conclusion?}
 
-Despite being only a microbenchmarks, this result is very important as it proves
+Despite being only a microbenchmark, this result is very important as it proves
 that our strategy of intermixing compile time and runtime can yield to better
 performances than current techniques.  The result is even more impressive if
 we consider dynamically typed languages as TLC are usually considered much

Modified: pypy/extradoc/talk/ecoop2009/jitgen.tex
==============================================================================
--- pypy/extradoc/talk/ecoop2009/jitgen.tex	(original)
+++ pypy/extradoc/talk/ecoop2009/jitgen.tex	Thu Dec 18 18:02:34 2008
@@ -67,7 +67,7 @@
 Let us look at an example. Figure \ref{fig:tlc-main} shows parts of the
 main-loop of the TLC interpreter (in slightly simplified form). The static
 arguments of this functions would typically be the \lstinline{code} argument
-(containing the bytecode as a string), the \lstinline{pc} argument (containing
+(containing the bytecode as a string \anto{what about using array of bytes instead of string? For .NET/JVM people, there is a strong difference between the twos}), the \lstinline{pc} argument (containing
 the initial program counter) and the \lstinline{pool} argument (containing the
 constant pool). The \lstinline{args} argument is dynamic since it contains the
 user-input of the interpreted function. Since the \lstinline{while} loop and the

Modified: pypy/extradoc/talk/ecoop2009/tlc.tex
==============================================================================
--- pypy/extradoc/talk/ecoop2009/tlc.tex	(original)
+++ pypy/extradoc/talk/ecoop2009/tlc.tex	Thu Dec 18 18:02:34 2008
@@ -29,8 +29,8 @@
 \begin{itemize}
 \item \textbf{Stack manipulation}: standard operations to manipulate the
   stack, such as \lstinline{POP}, \lstinline{PUSHARG}, \lstinline{SWAP}, etc.
-\item \textbf{Flow control} to do conditional and unconditional jumps.
-\cfbolz{what is the bytecode for conditional jumps?}
+\item \textbf{Flow control} to do conditional (\lstinline{BR_COND}) and
+  unconditional (\lstinline{BR}) jumps.
 \item \textbf{Arithmetic}: numerical operations on integers, like
   \lstinline{ADD}, \lstinline{SUB}, etc.
 \item \textbf{Comparisons} like \lstinline{EQ}, \lstinline{LT},



More information about the Pypy-commit mailing list