From f30899265a93b7823036eaa102758baff0a26974 Mon Sep 17 00:00:00 2001 From: Aaron Ballman Date: Wed, 24 Jun 2015 12:11:04 +0000 Subject: [PATCH] Silencing some Sphinx warnings about duplicate explicit target names. git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@240536 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/SafeStack.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/SafeStack.rst b/docs/SafeStack.rst index 2412512aee..79e02cabef 100644 --- a/docs/SafeStack.rst +++ b/docs/SafeStack.rst @@ -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 -`_ paper for details). This is mainly +`__ 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 `_ +Please refer to the `Code-Pointer Integrity `__ project page for more information about the design of the SafeStack and its related technologies. Publications ------------ -`Code-Pointer Integrity `_. +`Code-Pointer Integrity `__. Volodymyr Kuznetsov, Laszlo Szekeres, Mathias Payer, George Candea, R. Sekar, Dawn Song. USENIX Symposium on Operating Systems Design and Implementation (`OSDI `_), Broomfield, CO, October 2014 -- 2.40.0