aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLogan Chien <tzuhsiang.chien@gmail.com>2017-10-04 22:05:27 +0800
committerLogan Chien <tzuhsiang.chien@gmail.com>2017-10-04 22:05:27 +0800
commit9d611497dc455d03529b67f17c52a96b57ebcc5b (patch)
treeb4005de5543f8c817cc0f4659ce34edd37e13054 /rpython
parentMoved tag release-pypy2.7-v5.9.0 to changeset 84a2f3e6a7f8 (from changeset 03... (diff)
downloadpypy-9d611497dc455d03529b67f17c52a96b57ebcc5b.tar.gz
pypy-9d611497dc455d03529b67f17c52a96b57ebcc5b.tar.bz2
pypy-9d611497dc455d03529b67f17c52a96b57ebcc5b.zip
fix the PYPYLOG link in rpython doc
Diffstat (limited to 'rpython')
-rw-r--r--rpython/doc/jit/optimizer.rst7
1 files changed, 3 insertions, 4 deletions
diff --git a/rpython/doc/jit/optimizer.rst b/rpython/doc/jit/optimizer.rst
index ad7cb319d2..9b892179ef 100644
--- a/rpython/doc/jit/optimizer.rst
+++ b/rpython/doc/jit/optimizer.rst
@@ -42,10 +42,9 @@ to compare the Python code that constructed the trace::
There are better ways to compute the sum from ``[0..100]``, but it gives a better intuition on how
traces are constructed than ``sum(range(101))``.
Note that the trace syntax is the one used in the test suite. It is also very
-similar to traces printed at runtime by PYPYLOG_. The first line gives the input variables, the
-second line is a ``label`` operation, the last one is the backwards ``jump`` operation.
-
-.. _PYPYLOG: logging.html
+similar to traces printed at runtime by :doc:`PYPYLOG <../logging>`. The first
+line gives the input variables, the second line is a ``label`` operation, the
+last one is the backwards ``jump`` operation.
These instructions mentioned earlier are special: