[pypy-svn] r64226 - in pypy/trunk/pypy/doc: . jit
cfbolz at codespeak.net
cfbolz at codespeak.net
Fri Apr 17 11:40:19 CEST 2009
Author: cfbolz
Date: Fri Apr 17 11:40:18 2009
New Revision: 64226
Modified:
pypy/trunk/pypy/doc/_ref.txt
pypy/trunk/pypy/doc/glossary.txt
pypy/trunk/pypy/doc/index.txt
pypy/trunk/pypy/doc/jit/_ref.txt
pypy/trunk/pypy/doc/rffi.txt
pypy/trunk/pypy/doc/rtyper.txt
pypy/trunk/pypy/doc/translation.txt
Log:
kill some of the references to the llvm backend
Modified: pypy/trunk/pypy/doc/_ref.txt
==============================================================================
--- pypy/trunk/pypy/doc/_ref.txt (original)
+++ pypy/trunk/pypy/doc/_ref.txt Fri Apr 17 11:40:18 2009
@@ -31,6 +31,7 @@
.. _`interpreter/pyparser/`:
.. _`pypy/interpreter/pyparser`: ../../pypy/interpreter/pyparser
.. _`pypy/interpreter/typedef.py`: ../../pypy/interpreter/typedef.py
+.. _`jit/`: ../../pypy/jit
.. _`lang/`: ../../pypy/lang
.. _`lang/js/`: ../../pypy/lang/js
.. _`lang/prolog/`: ../../pypy/lang/prolog
@@ -95,9 +96,7 @@
.. _`translator/goal/`: ../../pypy/translator/goal
.. _`pypy/translator/goal/targetnopstandalone.py`: ../../pypy/translator/goal/targetnopstandalone.py
.. _`pypy/translator/goal/targetprologstandalone.py`: ../../pypy/translator/goal/targetprologstandalone.py
-.. _`translator/js/`: ../../pypy/translator/js
.. _`translator/jvm/`: ../../pypy/translator/jvm
-.. _`translator/llvm/`: ../../pypy/translator/llvm
.. _`translator/stackless/`: ../../pypy/translator/stackless
.. _`translator/tool/`: ../../pypy/translator/tool
-.. _`jit/`: http://codespeak.net/svn/pypy/branch/oo-jit/pypy/jit/
+.. _`translator/js/`: http://codespeak.net/svn/pypy/branch/oo-jit/pypy/translator/js/
Modified: pypy/trunk/pypy/doc/glossary.txt
==============================================================================
--- pypy/trunk/pypy/doc/glossary.txt (original)
+++ pypy/trunk/pypy/doc/glossary.txt Fri Apr 17 11:40:18 2009
@@ -79,7 +79,7 @@
**lltypesystem**
A `C-like type model <rtyper.html#low-level-types>`__ that contains
structs and pointers. A backend_ that uses this type system is also
- called a low-level backend. The C and LLVM backends use this
+ called a low-level backend. The C backend uses this
typesystem.
.. _`low-level helper`:
Modified: pypy/trunk/pypy/doc/index.txt
==============================================================================
--- pypy/trunk/pypy/doc/index.txt (original)
+++ pypy/trunk/pypy/doc/index.txt Fri Apr 17 11:40:18 2009
@@ -87,10 +87,8 @@
time before we notice and fix bugs).
PyPy's own tests `summary`_, daily updated, run through BuildBot infrastructure.
-
-`Nightly builds and benchmarks`_ of PyPy to C, CLI and LLVM (PowerPC machine).
-
-`Nightly compliance test runs for compiled pypy-c`_.
+You can also find CPython's compliance tests run with compiled ``pypy-c``
+exeuctables there.
information dating from early 2007:
@@ -159,8 +157,6 @@
.. _`sprint reports`: sprint-reports.html
.. _`talks and related projects`: extradoc.html
.. _`license`: ../../LICENSE
-.. _`Nightly compliance test runs for compiled pypy-c`: http://www2.openend.se/~pedronis/pypy-c-test/
-.. _`compliance test status`: http://codespeak.net/~hpk/pypy-testresult/
.. _`PyPy LOC statistics`: http://codespeak.net/~hpk/pypy-stat/
.. _`PyPy statistics`: http://codespeak.net/pypy/trunk/pypy/doc/statistic
.. _`object spaces`: objspace.html
@@ -283,9 +279,6 @@
`translator/jvm/`_ the Java backend
-`translator/llvm/`_ contains the `LLVM backend`_ producing LLVM assembler
- from fully annotated RPython programs
-
`translator/stackless/`_ the `Stackless Transform`_
`translator/tool/`_ helper tools for translation, including the Pygame
@@ -321,7 +314,6 @@
.. _`testing methods`: coding-guide.html#testing-in-pypy
.. _`translation`: translation.html
.. _`GenC backend`: translation.html#genc
-.. _`LLVM backend`: translation.html#llvm
.. _`CLI backend`: cli-backend.html
.. _`py.py`: getting-started.html#main-entry-point
.. _`translatorshell.py`: getting-started.html#try-out-the-translator
Modified: pypy/trunk/pypy/doc/jit/_ref.txt
==============================================================================
--- pypy/trunk/pypy/doc/jit/_ref.txt (original)
+++ pypy/trunk/pypy/doc/jit/_ref.txt Fri Apr 17 11:40:18 2009
@@ -1,8 +1,8 @@
.. _`demo/jit/`: ../../../demo/jit
.. _`demo/jit/f1.py`: ../../../demo/jit/f1.py
+.. _`pypy/jit/tl/targettiny1.py`: ../../../pypy/jit/tl/targettiny1.py
+.. _`pypy/jit/tl/tiny1.py`: ../../../pypy/jit/tl/tiny1.py
+.. _`pypy/jit/tl/tiny2.py`: ../../../pypy/jit/tl/tiny2.py
.. _`rpython/rlist.py`: ../../../pypy/rpython/rlist.py
.. _`pypy/jit/codegen/model.py`: http://codespeak.net/svn/pypy/branch/oo-jit/pypy/jit/codegen/model.py
.. _`pypy/jit/timeshifter/rvalue.py`: http://codespeak.net/svn/pypy/branch/oo-jit/pypy/jit/timeshifter/rvalue.py
-.. _`pypy/jit/tl/targettiny1.py`: http://codespeak.net/svn/pypy/branch/oo-jit/pypy/jit/tl/targettiny1.py
-.. _`pypy/jit/tl/tiny1.py`: http://codespeak.net/svn/pypy/branch/oo-jit/pypy/jit/tl/tiny1.py
-.. _`pypy/jit/tl/tiny2.py`: http://codespeak.net/svn/pypy/branch/oo-jit/pypy/jit/tl/tiny2.py
Modified: pypy/trunk/pypy/doc/rffi.txt
==============================================================================
--- pypy/trunk/pypy/doc/rffi.txt (original)
+++ pypy/trunk/pypy/doc/rffi.txt Fri Apr 17 11:40:18 2009
@@ -6,7 +6,7 @@
-------
This document describes an FFI for RPython language, concentrating
-on low-level backends like C or LLVM. It describes
+on low-level backends like C. It describes
how to declare and call low-level (C) functions from RPython level.
Declaring low-level external function
Modified: pypy/trunk/pypy/doc/rtyper.txt
==============================================================================
--- pypy/trunk/pypy/doc/rtyper.txt (original)
+++ pypy/trunk/pypy/doc/rtyper.txt Fri Apr 17 11:40:18 2009
@@ -129,8 +129,8 @@
---------------
The RPython Typer uses a standard low-level model which we believe can
-correspond rather directly to various target languages such as C and
-LLVM_. This model is implemented in the first part of
+correspond rather directly to various target languages such as C.
+This model is implemented in the first part of
`rpython/lltypesystem/lltype.py`_.
The second part of `rpython/lltypesystem/lltype.py`_ is a runnable
@@ -438,7 +438,7 @@
---------------------
The standard `low-level type` model described above is fine for
-targeting low level backends such as C and LLVM, but it is not good
+targeting low level backends such as C, but it is not good
enough for targeting higher level backends such as .NET CLI or Java
JVM, so a new object oriented model has been introduced. This model is
implemented in the first part of `rpython/ootypesystem/ootype.py`_.
@@ -791,5 +791,4 @@
assert res == ~3
.. _annotator: translation.html#the-annotation-pass
-.. _llvm: translation.html#the-llvm-back-end
.. include:: _ref.txt
Modified: pypy/trunk/pypy/doc/translation.txt
==============================================================================
--- pypy/trunk/pypy/doc/translation.txt (original)
+++ pypy/trunk/pypy/doc/translation.txt Fri Apr 17 11:40:18 2009
@@ -28,7 +28,7 @@
introduce them.
As of the 1.0 release, RPython_ programs can be translated into the following
-languages/platforms: C/POSIX, LLVM/POSIX, CLI/.NET, Javascript
+languages/platforms: C/POSIX, CLI/.NET, Javascript
and Java/JVM (in addition, there's `a backend`_ that translates
`application-level`_ into `interpreter-level`_ code, but this is a special
case in several ways).
@@ -691,53 +691,12 @@
("databasing") and actually generating the source are best considered
separately has become clear.
-This process is reflected in the source somewhat; for example, the LLVM
-and C backends use different implementations of the graph preparation
-code, although there is no real reason for this.
-
Other backends
==============
-.. _LLVM:
-
Use the :config:`translation.backend` option to choose which backend to use.
-The LLVM Back-End
------------------
-
-http://codespeak.net/pypy/trunk/pypy/translator/llvm/
-
-For information on getting started on the LLVM (`low level virtual machine`_)
-backend - please see `here`_.
-
-Similar to the task of GenC, GenLLVM translates a flow graph to low level LLVM
-bytecode. LLVM's memory model is pretty similar to that of GenC's, and so the
-LLVM backend uses the same stages of the tool chain -- the annotator, the
-RTyper (targeting the low-level type system) and subsequent transformations,
-although the final preparations are done by different code (for historical,
-rather than fundamental, reasons).
-
-One of the reasons for targeting LLVM bytecodes is that the LLVM tools include
-excellent optimizers -- RPython programs, including the Standard Interpreter,
-compiled via LLVM are generally faster than when compiled via C.
-
-The LLVM backend is pretty well maintained, although fewer people have the
-necessary tools installed so it can take a bit longer to be fixed when a
-refactoring causes it to stop working. It doesn't support all the features of
-GenC -- in particular it only supports the Boehm GC.
-
-The LLVM backend would not have been possible without all the people
-contributing to PyPy. Carl Friedrich did an amazing amount of groundwork during
-the first half of 2005. Carl Friedrich and Holger then initiated a revamped
-version based on the new `RPython Typer`_ flow graph. Significant progress was
-made during the Gothenburg sprint - and then the following 6 weeks Eric and
-Richard worked on it, achieving a standalone executable just prior to the
-Heidelberg sprint. During the Heidelberg sprint Eric and Richard mainly
-worked on sharing the backend external code with GenC.
-
-.. _`low level virtual machine`: http://llvm.org/
-.. _`here`: getting-started.html#translating-the-flow-graph-to-llvm-code
The Object-Oriented Backends
More information about the Pypy-commit
mailing list