Author: Peter Collingbourne Date: 2025-04-14T19:50:37-07:00 New Revision: 984ec70b61cb57b00e622a21b259aaf11775c5f0
URL: https://github.com/llvm/llvm-project/commit/984ec70b61cb57b00e622a21b259aaf11775c5f0 DIFF: https://github.com/llvm/llvm-project/commit/984ec70b61cb57b00e622a21b259aaf11775c5f0.diff LOG: Minor documentation update. Added: Modified: clang/docs/ControlFlowIntegrity.rst Removed: ################################################################################ diff --git a/clang/docs/ControlFlowIntegrity.rst b/clang/docs/ControlFlowIntegrity.rst index a88271faf6b42..2f2f8ccf4481b 100644 --- a/clang/docs/ControlFlowIntegrity.rst +++ b/clang/docs/ControlFlowIntegrity.rst @@ -19,11 +19,12 @@ of undefined behavior that can potentially allow attackers to subvert the program's control flow. These schemes have been optimized for performance, allowing developers to enable them in release builds. -To enable Clang's available CFI schemes, use the flag ``-fsanitize=cfi``. -You can also enable a subset of available :ref:`schemes <cfi-schemes>`. -As currently implemented, all schemes rely on link-time optimization (LTO); -so it is required to specify ``-flto``, and the linker used must support LTO, -for example via the `gold plugin`_. +To enable Clang's available CFI schemes, use the flag +``-fsanitize=cfi``. You can also enable a subset of available +:ref:`schemes <cfi-schemes>`. As currently implemented, all schemes +except for ``kcfi`` rely on link-time optimization (LTO); so it is +required to specify ``-flto`` or ``-flto=thin``, and the linker used +must support LTO, for example via the `gold plugin`_. To allow the checks to be implemented efficiently, the program must be structured such that certain object files are compiled with CFI _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
