@@ -2155,13 +2155,11 @@ are listed below.
21552155
21562156.. option :: -f[no-]sanitize=check1 ,check2 ,...
21572157
2158- Turn on runtime checks for various forms of undefined or suspicious
2159- behavior.
2158+ Turn on runtime checks or mitigations for various forms of undefined or
2159+ suspicious behavior. These are disabled by default .
21602160
2161- This option controls whether Clang adds runtime checks for various
2162- forms of undefined or suspicious behavior, and is disabled by
2163- default. If a check fails, a diagnostic message is produced at
2164- runtime explaining the problem. The main checks are:
2161+ The following options enable runtime checks for various forms of undefined
2162+ or suspicious behavior:
21652163
21662164 - .. _opt_fsanitize_address:
21672165
@@ -2194,8 +2192,14 @@ are listed below.
21942192 protection against stack-based memory corruption errors.
21952193 - ``-fsanitize=realtime ``: :doc: `RealtimeSanitizer `,
21962194 a real-time safety checker.
2197- - ``-fsanitize=alloc-token ``: :doc: `AllocToken `,
2198- allocation token instrumentation (requires compatible allocator).
2195+
2196+ The following options enable runtime mitigations for various forms of
2197+ undefined or suspicious behavior:
2198+
2199+ - ``-fsanitize=alloc-token ``: Enables :doc: `allocation tokens <AllocToken >`
2200+ for allocator-level heap organization strategies, such as for security
2201+ hardening. It passes type-derived token IDs to a compatible memory
2202+ allocator. Requires linking against a token-aware allocator.
21992203
22002204 There are more fine-grained checks available: see
22012205 the :ref: `list <ubsan-checks >` of specific kinds of
0 commit comments