Attempt to unbreak sphinx build bot by inserting a link.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@367487 91177308-0d34-0410-b5e6-96231b3b80d8

diff --git a/docs/LoopTerminology.rst b/docs/LoopTerminology.rst
index 7306167de65cd96d8be0b41ce98e8c0d95b13e36..e901720e23e6c00772b84f1d5e2a4f68771f2bbb 100644 (file)
--- a/docs/LoopTerminology.rst
+++ b/docs/LoopTerminology.rst
@@ -1,3 +1,4 @@
+.. _loop-terminology:
 ===========================================
 LLVM Loop Terminology (and Canonical Forms)
 ===========================================

diff --git a/docs/WritingAnLLVMPass.rst b/docs/WritingAnLLVMPass.rst
index 386f3d61d0e7df3f7966df43179c58264564fd5a..ddf045acb74ad62bcece742ac2e0d10cb60d582c 100644 (file)
--- a/docs/WritingAnLLVMPass.rst
+++ b/docs/WritingAnLLVMPass.rst
@@ -538,9 +538,9 @@ compiled.
 The ``LoopPass`` class
 ----------------------
 
-All ``LoopPass`` execute on each loop in the function independent of all of the
-other loops in the function.  ``LoopPass`` processes loops in loop nest order
-such that outer most loop is processed last.
+All ``LoopPass`` execute on each :ref:`loop <loop-terminology>` in the function
+independent of all of the other loops in the function.  ``LoopPass`` processes
+loops in loop nest order such that outer most loop is processed last.
 
 ``LoopPass`` subclasses are allowed to update loop nest using ``LPPassManager``
 interface.  Implementing a loop pass is usually straightforward.