[pypy-svn] r36254 - pypy/dist/pypy/doc
mwh at codespeak.net
mwh at codespeak.net
Mon Jan 8 12:45:05 CET 2007
Author: mwh
Date: Mon Jan 8 12:45:01 2007
New Revision: 36254
Modified:
pypy/dist/pypy/doc/glossary.txt
Log:
add some JIT terminology to the glossary
Modified: pypy/dist/pypy/doc/glossary.txt
==============================================================================
--- pypy/dist/pypy/doc/glossary.txt (original)
+++ pypy/dist/pypy/doc/glossary.txt Mon Jan 8 12:45:01 2007
@@ -17,15 +17,21 @@
.. _backend:
-**backend**
+**backend**
Code generator that converts an `RPython
<coding-guide.html#restricted-python>`__ program to a `target
language`_ using the PyPy toolchain_. A backend uses either the
lltypesystem_ or the ootypesystem_.
+.. _`compile-time`:
+
+**compile-time**
+ In the context of the JIT_, compile time is when the JIT is
+ generating machine code "just in time".
+
.. _CPython:
-**CPython**
+**CPython**
The "default" implementation of Python, written in C and
distributed by the PSF_ on http://www.python.org.
@@ -53,8 +59,9 @@
.. _`jit`:
**jit**
- `just in time compiler`_
-
+ `just in time compiler`_. Our jit now has `some draft documentation
+ <jit.html>`__.
+
.. _`l3interpreter`:
**l3interpreter**
@@ -88,7 +95,7 @@
a module that accesses PyPy's `interpreter level`_. The name comes
from the fact that the module's implementation can be a mixture of
`application level`_ and `interpreter level`_ code.
-
+
.. _`object space`:
**object space**
@@ -117,6 +124,13 @@
.. _`rpython`:
+.. _`promotion`:
+
+**promotion**
+ JIT_ terminology. *promotion* is a way of "using" a `run-time`_
+ value at `compile-time`_, essentially by deferring compilation
+ until the run-time value is known. See if `the jit docs`_ help.
+
**rpython**
`Restricted Python`_, a limited subset of the Python_ language.
The limitations make `type inference`_ possible.
@@ -130,6 +144,12 @@
graph into one that fits the model of the target platform/backend_
using either the lltypesystem_ or the ootypesystem_.
+.. _`run-time`:
+
+**run-time**
+ In the context of the JIT_, run time is when the code the JIT has
+ generated is executing.
+
.. _`specialization`:
**specialization**
@@ -153,6 +173,11 @@
.. _toolchain:
+**timeshifting**
+ JIT_ terminology. *timeshifting* is to do with moving from the
+ world where there are only `run-time`_ operations to a world where
+ there are both `run-time`_ and `compile-time`_ operations.
+
**toolchain**
The `annotator pass`_, `The RPython Typer`_, and various
`backends`_.
@@ -162,6 +187,12 @@
**transformation**
Code that modifies flowgraphs to weave in `translation-aspects`_
+.. _`translation-time`:
+
+**translation-time**
+ In the context of the JIT_, translation time is when the PyPy
+ source is being analysed and the JIT itself is being created.
+
.. _`translator`:
**translator**
@@ -184,6 +215,7 @@
.. _applevel: coding-guide.html#application-level
.. _`target language`: getting-started.html#trying-out-the-translator
.. _`just in time compiler`: http://en.wikipedia.org/wiki/Just-in-time_compilation
+.. _`the jit docs`: jit.html
.. _`type inference article on Wikipedia`: http://en.wikipedia.org/wiki/Type_inference
.. _`annotator pass`: translation.html#the-annotation-pass
.. _`The RPython Typer`: translation.html#the-rpython-typer
More information about the Pypy-commit
mailing list