r240696 - docs: Fix bad link in SafeStack.rst.

Peter Collingbourne peter at pcc.me.uk
Thu Jun 25 14:02:17 PDT 2015


Author: pcc
Date: Thu Jun 25 16:02:17 2015
New Revision: 240696

URL: http://llvm.org/viewvc/llvm-project?rev=240696&view=rev
Log:
docs: Fix bad link in SafeStack.rst.

Modified:
    cfe/trunk/docs/SafeStack.rst

Modified: cfe/trunk/docs/SafeStack.rst
URL: http://llvm.org/viewvc/llvm-project/cfe/trunk/docs/SafeStack.rst?rev=240696&r1=240695&r2=240696&view=diff
==============================================================================
--- cfe/trunk/docs/SafeStack.rst (original)
+++ cfe/trunk/docs/SafeStack.rst Thu Jun 25 16:02:17 2015
@@ -87,7 +87,7 @@ that are stored on the heap or the unsaf
 <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





More information about the cfe-commits mailing list