From: Peter Collingbourne <peter@pcc.me.uk>
Date: Thu, 25 Jun 2015 21:02:17 +0000 (+0000)
Subject: docs: Fix bad link in SafeStack.rst.
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=454d8618ebadd14319064d04a87d91368d7d1875;p=clang

docs: Fix bad link in SafeStack.rst.

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

diff --git a/docs/SafeStack.rst b/docs/SafeStack.rst
index 79e02cabef..21e9b6c621 100644
--- a/docs/SafeStack.rst
+++ b/docs/SafeStack.rst
@@ -87,7 +87,7 @@ that are stored on the heap or the unsafe stack, such as `CPI
 <http://dslab.epfl.ch/proj/cpi/>`_, or a forward-edge control flow integrity
 mechanism that enforces correct calling conventions at indirect call sites,
 such as `IFCC <http://research.google.com/pubs/archive/42808.pdf>`_ with arity
-checks. Clang has control-flow integrity protection scheme for `C++ virtual
+checks. Clang has control-flow integrity protection scheme for :doc:`C++ virtual
 calls <ControlFlowIntegrity>`, but not non-virtual indirect calls. With
 SafeStack alone, an attacker can overwrite a function pointer on the heap or
 the unsafe stack and cause a program to call arbitrary location, which in turn