summaryrefslogtreecommitdiffstats
path: root/clang/docs/SafeStack.rst
Commit message (Collapse)AuthorAgeFilesLines
* [Docs] Modernize references to macOSJ. Ryan Stinnett2019-05-301-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Summary: This updates all places in documentation that refer to "Mac OS X", "OS X", etc. to instead use the modern name "macOS" when no specific version number is mentioned. If a specific version is mentioned, this attempts to use the OS name at the time of that version: * Mac OS X for 10.0 - 10.7 * OS X for 10.8 - 10.11 * macOS for 10.12 - present Reviewers: JDevlieghere Subscribers: mgorny, christof, arphaman, cfe-commits, lldb-commits, libcxx-commits, llvm-commits Tags: #clang, #lldb, #libc, #llvm Differential Revision: https://reviews.llvm.org/D62654 llvm-svn: 362113
* [Documentation] Fix problem in docs/SafeStack.rst introduced in r351976.Eugene Zelenko2019-01-231-3/+3
| | | | llvm-svn: 351977
* [Documentation] Use HTTPS whenever possibleEugene Zelenko2019-01-231-8/+8
| | | | | | Differential revision: https://reviews.llvm.org/D56946 llvm-svn: 351976
* [Docs] Update supported oses for safestack, ubsan, asan, tsan and msanDavid Carlier2018-07-251-1/+1
| | | | | | Adding oses others than Linux. llvm-svn: 337926
* SafeStack: Add builtins to read unsafe stack top/bottomVlad Tsyrklevich2018-07-131-2/+14
| | | | | | | | | | | | | | | | | | | | Summary: Introduce built-ins to read the unsafe stack top and bottom. The unsafe stack top is required to implement garbage collection scanning for Oilpan. Currently there is already a built-in 'get_unsafe_stack_start' to read the bottom of the unsafe stack, but I chose to duplicate this API because 'start' is ambiguous (e.g. Oilpan uses WTF::GetStackStart to read the safe stack top.) Reviewers: pcc Reviewed By: pcc Subscribers: llvm-commits, kcc Differential Revision: https://reviews.llvm.org/D49152 llvm-svn: 337037
* docs: Document how safestack handles setjmp and exceptions.Peter Collingbourne2016-05-241-0/+11
| | | | llvm-svn: 270634
* docs: Fix bad link in SafeStack.rst.Peter Collingbourne2015-06-251-1/+1
| | | | llvm-svn: 240696
* Silencing some Sphinx warnings about duplicate explicit target names.Aaron Ballman2015-06-241-3/+3
| | | | llvm-svn: 240536
* SafeStack documentation improvementsPeter Collingbourne2015-06-231-46/+70
| | | | | | | | | | | | | | | | | This patch makes the following improvements to the SafeStack documentation: Explicitly states the security guarantees of the SafeStack Clarifies which of the security guarantees are probabilistic Re-orders security limitations to put the most severe ones first Explains how `__attribute__((no_sanitize("safe-stack")))` works and how to use it safely Explains that SafeStack should be combined with a forward-edge protection mechanism, such as CPI, IFCC or others Multiple readability and stylistic improvements Patch by Volodymyr Kuznetsov! Differential Revision: http://reviews.llvm.org/D10598 llvm-svn: 240472
* Protection against stack-based memory corruption errors using SafeStack: ↵Peter Collingbourne2015-06-151-0/+163
Clang command line option and function attribute This patch adds the -fsanitize=safe-stack command line argument for clang, which enables the Safe Stack protection (see http://reviews.llvm.org/D6094 for the detailed description of the Safe Stack). This patch is our implementation of the safe stack on top of Clang. The patches make the following changes: - Add -fsanitize=safe-stack and -fno-sanitize=safe-stack options to clang to control safe stack usage (the safe stack is disabled by default). - Add __attribute__((no_sanitize("safe-stack"))) attribute to clang that can be used to disable the safe stack for individual functions even when enabled globally. Original patch by Volodymyr Kuznetsov and others at the Dependable Systems Lab at EPFL; updates and upstreaming by myself. Differential Revision: http://reviews.llvm.org/D6095 llvm-svn: 239762
OpenPOWER on IntegriCloud