From: Eugene Zelenko Date: Wed, 23 Jan 2019 20:51:06 +0000 (+0000) Subject: [Documentation] Fix problem in docs/SafeStack.rst introduced in r351976. X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=45b5be68b31579b7db8ef0b954fe5e67cc840c2f;p=clang [Documentation] Fix problem in docs/SafeStack.rst introduced in r351976. git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@351977 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/SafeStack.rst b/docs/SafeStack.rst index 3c426cf9a7..c1e09da935 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 @@ -186,7 +186,7 @@ Deprecated: This builtin function is an alias for 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. @@ -204,7 +204,7 @@ in the function ``SafeStack::createStackRestorePoints``. 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