r240536 - Silencing some Sphinx warnings about duplicate explicit target names.
Aaron Ballman
aaron at aaronballman.com
Wed Jun 24 05:11:04 PDT 2015
Author: aaronballman
Date: Wed Jun 24 07:11:04 2015
New Revision: 240536
URL: http://llvm.org/viewvc/llvm-project?rev=240536&view=rev
Log:
Silencing some Sphinx warnings about duplicate explicit target names.
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=240536&r1=240535&r2=240536&view=diff
==============================================================================
--- cfe/trunk/docs/SafeStack.rst (original)
+++ cfe/trunk/docs/SafeStack.rst Wed Jun 24 07:11:04 2015
@@ -25,7 +25,7 @@ Performance
The performance overhead of the SafeStack instrumentation is less than 0.1% on
average across a variety of benchmarks (see the `Code-Pointer Integrity
-<http://dslab.epfl.ch/pubs/cpi.pdf>`_ paper for details). This is mainly
+<http://dslab.epfl.ch/pubs/cpi.pdf>`__ paper for details). This is mainly
because most small functions do not have any variables that require the unsafe
stack and, hence, do not need unsafe stack frames to be created. The cost of
creating unsafe stack frames for large functions is amortized by the cost of
@@ -174,14 +174,14 @@ current thread.
Design
======
-Please refer to the `Code-Pointer Integrity <http://dslab.epfl.ch/proj/cpi/>`_
+Please refer to the `Code-Pointer Integrity <http://dslab.epfl.ch/proj/cpi/>`__
project page for more information about the design of the SafeStack and its
related technologies.
Publications
------------
-`Code-Pointer Integrity <http://dslab.epfl.ch/pubs/cpi.pdf>`_.
+`Code-Pointer Integrity <http://dslab.epfl.ch/pubs/cpi.pdf>`__.
Volodymyr Kuznetsov, Laszlo Szekeres, Mathias Payer, George Candea, R. Sekar, Dawn Song.
USENIX Symposium on Operating Systems Design and Implementation
(`OSDI <https://www.usenix.org/conference/osdi14>`_), Broomfield, CO, October 2014
More information about the cfe-commits
mailing list