Author: Manuel Jacob <[email protected]>
Branch:
Changeset: r76413:402d41538ce3
Date: 2015-03-16 17:42 +0100
http://bitbucket.org/pypy/pypy/changeset/402d41538ce3/
Log: Fix typo.
diff --git a/rpython/doc/jit/optimizer.rst b/rpython/doc/jit/optimizer.rst
--- a/rpython/doc/jit/optimizer.rst
+++ b/rpython/doc/jit/optimizer.rst
@@ -1,7 +1,7 @@
.. _trace_optimizer:
-Trace Optimizier
-================
+Trace Optimizer
+===============
Traces of user programs are not directly translated into machine code.
The optimizer module implements several different semantic preserving
@@ -14,10 +14,10 @@
Before some optimizations are explained in more detail, it is essential to
understand how traces look like.
The optimizer comes with a test suit. It contains many trace
-examples and you might want to take a look at it
+examples and you might want to take a look at it
(in `rpython/jit/metainterp/optimizeopt/test/*.py`).
The allowed operations can be found in
`rpython/jit/metainterp/resoperation.py`.
-Here is an example of a trace::
+Here is an example of a trace::
[p0,i0,i1]
label(p0, i0, i1)
_______________________________________________
pypy-commit mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pypy-commit
