From: Diane Meirowitz <diane.meirowitz@oracle.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: *PING 2* [PATCH] doc: improve -fsanitize=undefined description
Date: Wed, 29 Sep 2021 19:56:23 +0000 [thread overview]
Message-ID: <D625A9B0-A82E-44E4-9B9A-4F3BD0D5B4D8@oracle.com> (raw)
Please review my patch. It is tiny. Thank you.
Diane
On 9/15/21, 5:02 PM, "Diane Meirowitz" <diane.meirowitz@oracle.com> wrote:
doc: improve -fsanitize=undefined description
gcc/ChangeLog:
* doc/invoke.texi: add link to UndefinedBehaviorSanitizer documentation,
mention UBSAN_OPTIONS, similar to what is done for AddressSanitizer.
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 78cfc100ac2..f022885edf8 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -15200,7 +15200,8 @@ The option cannot be combined with @option{-fsanitize=thread}.
@opindex fsanitize=undefined
Enable UndefinedBehaviorSanitizer, a fast undefined behavior detector.
Various computations are instrumented to detect undefined behavior
-at runtime. Current suboptions are:
+at runtime. See @uref{https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html} for more details. The run-time behavior can be influenced using the
+@env{UBSAN_OPTIONS} environment variable. Current suboptions are:
@table @gcctabopt
reply other threads:[~2021-09-29 20:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D625A9B0-A82E-44E4-9B9A-4F3BD0D5B4D8@oracle.com \
--to=diane.meirowitz@oracle.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).