From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Tom N <nospam@codesniffer.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: -fsanitize=undefined behavior
Date: Fri, 1 May 2020 19:17:49 +0100 [thread overview]
Message-ID: <CAH6eHdTPGYF-sQOny694o7TztdDZQRr4PhqFG91zGk3_2NZuvA@mail.gmail.com> (raw)
In-Reply-To: <31960797.205994.1588353217751@email.ionos.com>
On Fri, 1 May 2020 at 18:13, Tom N <nospam@codesniffer.com> wrote:
>
> > On May 1, 2020 at 7:39 AM Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> >
> > On Thu, 30 Apr 2020 at 23:58, Tom N <nospam@codesniffer.com> wrote:>> > On April 30, 2020 at 5:57 PM Jonathan Wakely <jwakely.gcc@gmail.com> wrote:The man page says:"Unlike other similar options, -fsanitize=float-divide-by-zero is not enabled by -fsanitize=undefined" and "Unlike other similar options,-fsanitize=float-cast-overflow is not enabled by -fsanitize=undefined"So it seems reasonable to assume that all the other suboptions are enabled by -fsanitize=undefined, and if you want *all* of them then use -fsanitize=undefined -fsanitize=float-divide-by-zero-fsanitize=float-cast-overflow> Thanks for the tip. Any reason the description of -fsanitize=undefined doesn't include something like, "If the -fsanitize=undefined option is enabled all sub-options will be enabled unless otherwise specified." so it's clear?Probably because nobody has suggested doing that yet. Would you liketo propose a patch for the docs?
> > The relevant place is here:https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/doc/invoke.texi;h=527d362533ab503cee9568b27808177977a52ac8;hb=HEAD#l13541
>
> I'd be happy to but unfortunately I'm not familiar with git. (I know...). But here's an old-style patch off 8.4 if it helps (attached too):
That'll do, thanks. I'll do the rest early next week.
next prev parent reply other threads:[~2020-05-01 18:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 20:30 Tom N
2020-04-30 21:57 ` Jonathan Wakely
2020-04-30 22:58 ` Tom N
2020-05-01 11:39 ` Jonathan Wakely
2020-05-01 17:13 ` Tom N
2020-05-01 18:17 ` Jonathan Wakely [this message]
2020-05-01 20:53 ` Tom N
2020-05-01 13:38 ` Segher Boessenkool
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=CAH6eHdTPGYF-sQOny694o7TztdDZQRr4PhqFG91zGk3_2NZuvA@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=nospam@codesniffer.com \
/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).