public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Richard Sandiford <rsandifo@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r9-9764] doc: improve -fsanitize=undefined description
Date: Mon, 11 Oct 2021 16:15:08 +0000 (GMT)	[thread overview]
Message-ID: <20211011161508.D5ADD3858D28@sourceware.org> (raw)

https://gcc.gnu.org/g:48c71dbb0d95396a7ef37c97006535751d523f22

commit r9-9764-g48c71dbb0d95396a7ef37c97006535751d523f22
Author: Diane Meirowitz <diane.meirowitz@oracle.com>
Date:   Wed Sep 15 21:03:00 2021 +0000

    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.
    
    (cherry picked from commit 1c0a83eff7bb5b1db997a9726ae6542aec893baa)

Diff:
---
 gcc/doc/invoke.texi | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 7226c9cc4af..977fe4574ec 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -12484,7 +12484,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-10-11 16:15 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=20211011161508.D5ADD3858D28@sourceware.org \
    --to=rsandifo@gcc.gnu.org \
    --cc=gcc-cvs@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).