diff options
| -rw-r--r-- | clang/docs/ReleaseNotes.rst | 5 | ||||
| -rw-r--r-- | clang/docs/UndefinedBehaviorSanitizer.rst | 13 |
2 files changed, 17 insertions, 1 deletions
diff --git a/clang/docs/ReleaseNotes.rst b/clang/docs/ReleaseNotes.rst index 60d418bd4a0..6f4644c01cd 100644 --- a/clang/docs/ReleaseNotes.rst +++ b/clang/docs/ReleaseNotes.rst @@ -229,7 +229,10 @@ Static Analyzer Undefined Behavior Sanitizer (UBSan) ------------------------------------ -... +* A minimal runtime is now available. It is suitable for use in production + environments, and has a small attack surface. It only provides very basic + issue logging and deduplication, and does not support ``-fsanitize=vptr`` + checking. Core Analysis Improvements ========================== diff --git a/clang/docs/UndefinedBehaviorSanitizer.rst b/clang/docs/UndefinedBehaviorSanitizer.rst index 5b43e2ef847..ed9357754ca 100644 --- a/clang/docs/UndefinedBehaviorSanitizer.rst +++ b/clang/docs/UndefinedBehaviorSanitizer.rst @@ -155,6 +155,19 @@ Volatile The ``null``, ``alignment``, ``object-size``, and ``vptr`` checks do not apply to pointers to types with the ``volatile`` qualifier. +Minimal Runtime +=============== + +There is a minimal UBSan runtime available suitable for use in production +environments. This runtime has a small attack surface. It only provides very +basic issue logging and deduplication, and does not support ``-fsanitize=vptr`` +checking. + +To use the minimal runtime, add ``-fsanitize-minimal-runtime`` to the clang +command line options. For example, if you're used to compiling with +``-fsanitize=undefined``, you could enable the minimal runtime with +``-fsanitize=undefined -fsanitize-minimal-runtime``. + Stack traces and report symbolization ===================================== If you want UBSan to print symbolized stack trace for each error report, you |
