From 03cd823a72f9f7b3c2dffe845bee9a983d9f06ea Mon Sep 17 00:00:00 2001 From: Vedant Kumar Date: Mon, 20 Mar 2017 21:40:58 +0000 Subject: [PATCH] [docs] Clarify sanitizer flag behavior PR32346 suggests that UBSan's docs about the -fsanitize, -fno-sanitize-recover, and -fsanitize-trap options are not explicit enough. Try to improve the wording. git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@298310 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/UndefinedBehaviorSanitizer.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/UndefinedBehaviorSanitizer.rst b/docs/UndefinedBehaviorSanitizer.rst index f9111ee846..d6fdad2a0c 100644 --- a/docs/UndefinedBehaviorSanitizer.rst +++ b/docs/UndefinedBehaviorSanitizer.rst @@ -50,9 +50,9 @@ instead of ``clang++`` if you're compiling/linking C code. You can enable only a subset of :ref:`checks ` offered by UBSan, and define the desired behavior for each kind of check: -* print a verbose error report and continue execution (default); -* print a verbose error report and exit the program; -* execute a trap instruction (doesn't require UBSan run-time support). +* ``-fsanitize=...``: print a verbose error report and continue execution (default); +* ``-fno-sanitize-recover=...``: print a verbose error report and exit the program; +* ``-fsanitize-trap=...``: execute a trap instruction (doesn't require UBSan run-time support). For example if you compile/link your program as: -- 2.40.0