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

antocuni at codespeak.net antocuni at codespeak.net
Wed Dec 17 12:12:26 CET 2008


Author: antocuni
Date: Wed Dec 17 12:12:26 2008
New Revision: 60535

Added:
   pypy/extradoc/talk/ecoop2009/tlc.tex
Modified:
   pypy/extradoc/talk/ecoop2009/benchmarks.tex
   pypy/extradoc/talk/ecoop2009/main.tex
Log:
move the section about tlc into its own file, and put it just after the introduction



Modified: pypy/extradoc/talk/ecoop2009/benchmarks.tex
==============================================================================
--- pypy/extradoc/talk/ecoop2009/benchmarks.tex	(original)
+++ pypy/extradoc/talk/ecoop2009/benchmarks.tex	Wed Dec 17 12:12:26 2008
@@ -1,55 +1,3 @@
-\section{The TLC language}
-
-\anto{maybe we should move this section somewhere else, if we want to use TLC
-  as a running example in other sections}
-\cfbolz{yes please! how about making it the next section after the
-introduction?}
-
-In this section, we will briefly describe \emph{TLC}, a simple dynamic
-language that we developed to exercise our JIT compiler generator.  As most of
-dynamic languages around, \emph{TLC} is implemented through a virtual machine
-that interprets a custom bytecode. Since our main interest is in the runtime
-performance of the VM, we did not implement the parser nor the bytecode
-compiler, but only the VM itself.
-
-TLC provides four different types:
-\begin{enumerate}
-\item Integers
-\item \lstinline{nil}, whose only value is the null value
-\item Objects
-\item Lisp-like lists
-\end{enumerate}
-
-Objects represent a collection of named attributes (much like JavaScript or
-Self) and named methods.  At creation time, it is necessary to specify the set
-of attributes of the object, as well as its methods.  Once the object has been
-created, it is not possible to add/remove attributes and methods.
-
-The virtual machine is stack-based, and provides several operations:
-
-\begin{itemize}
-\item \textbf{Stack manipulation}: standard operations to manipulate the
-  stack, such as \lstinline{PUSH}, \lstinline{POP}, \lstinline{SWAP}, etc.
-\item \textbf{Flow control} to do conditional and unconditional jumps.
-\item \textbf{Arithmetic}: numerical operations on integers, like
-  \lstinline{ADD}, \lstinline{SUB}, etc.
-\item \textbf{Comparisons} like \lstinline{EQ}, \lstinline{LT},
-  \lstinline{GT}, etc.
-\item \textbf{Object-oriented}: operations on objects: \lstinline{NEW},
-  \lstinline{GETATTR}, \lstinline{SETATTR}, \lstinline{SEND}.
-\item \textbf{List operations}: \lstinline{CONS}, \lstinline{CAR},
-  \lstinline{CDR}.
-\end{itemize}
-
-Obviously, not all the operations are applicable to all objects. For example,
-it is not possible to \lstinline{ADD} an integer and an object, or reading an
-attribute from an object which does not provide it.  Being a dynamic language,
-the VM needs to do all these checks at runtime; in case one of the check
-fails, the execution is simply aborted.
-
-\anto{should we try to invent a syntax for TLC and provide some examples?}
-\cfbolz{we should provide an example with the assembler syntax}
-
 \section{Benchmarks}
 
 \cfbolz{I think this should go to the beginning of the description of the TLC as

Modified: pypy/extradoc/talk/ecoop2009/main.tex
==============================================================================
--- pypy/extradoc/talk/ecoop2009/main.tex	(original)
+++ pypy/extradoc/talk/ecoop2009/main.tex	Wed Dec 17 12:12:26 2008
@@ -83,6 +83,7 @@
 
 \input{abstract}
 \input{intro}
+\input{tlc}
 \input{jitgen}
 \input{rainbow}
 \input{clibackend}

Added: pypy/extradoc/talk/ecoop2009/tlc.tex
==============================================================================
--- (empty file)
+++ pypy/extradoc/talk/ecoop2009/tlc.tex	Wed Dec 17 12:12:26 2008
@@ -0,0 +1,47 @@
+\section{The TLC language}
+
+In this section, we will briefly describe \emph{TLC}, a simple dynamic
+language that we developed to exercise our JIT compiler generator.  As most of
+dynamic languages around, \emph{TLC} is implemented through a virtual machine
+that interprets a custom bytecode. Since our main interest is in the runtime
+performance of the VM, we did not implement the parser nor the bytecode
+compiler, but only the VM itself.
+
+TLC provides four different types:
+\begin{enumerate}
+\item Integers
+\item \lstinline{nil}, whose only value is the null value
+\item Objects
+\item Lisp-like lists
+\end{enumerate}
+
+Objects represent a collection of named attributes (much like JavaScript or
+Self) and named methods.  At creation time, it is necessary to specify the set
+of attributes of the object, as well as its methods.  Once the object has been
+created, it is not possible to add/remove attributes and methods.
+
+The virtual machine is stack-based, and provides several operations:
+
+\begin{itemize}
+\item \textbf{Stack manipulation}: standard operations to manipulate the
+  stack, such as \lstinline{PUSH}, \lstinline{POP}, \lstinline{SWAP}, etc.
+\item \textbf{Flow control} to do conditional and unconditional jumps.
+\item \textbf{Arithmetic}: numerical operations on integers, like
+  \lstinline{ADD}, \lstinline{SUB}, etc.
+\item \textbf{Comparisons} like \lstinline{EQ}, \lstinline{LT},
+  \lstinline{GT}, etc.
+\item \textbf{Object-oriented}: operations on objects: \lstinline{NEW},
+  \lstinline{GETATTR}, \lstinline{SETATTR}, \lstinline{SEND}.
+\item \textbf{List operations}: \lstinline{CONS}, \lstinline{CAR},
+  \lstinline{CDR}.
+\end{itemize}
+
+Obviously, not all the operations are applicable to all objects. For example,
+it is not possible to \lstinline{ADD} an integer and an object, or reading an
+attribute from an object which does not provide it.  Being a dynamic language,
+the VM needs to do all these checks at runtime; in case one of the check
+fails, the execution is simply aborted.
+
+\anto{should we try to invent a syntax for TLC and provide some examples?}
+\cfbolz{we should provide an example with the assembler syntax}
+



More information about the Pypy-commit mailing list