public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Martin Sebor <msebor@gmail.com>,
	Martin Sebor via Gcc-help <gcc-help@gcc.gnu.org>,
	 Dumitru Ceara <dceara@redhat.com>,
	Richard Sandiford <richard.sandiford@arm.com>
Subject: Re: Potentially false-positive -Wstringop-overflow= warning with gcc >= 11.1
Date: Wed, 2 Feb 2022 20:44:25 +0000	[thread overview]
Message-ID: <CAH6eHdRTMEU1+jTPTMU10diehBDWMpOaGrVs7wij75sPrMRmHQ@mail.gmail.com> (raw)
In-Reply-To: <20220202183334.GA614@gate.crashing.org>

On Wed, 2 Feb 2022 at 18:35, Segher Boessenkool wrote:
>
> On Wed, Feb 02, 2022 at 10:12:44AM +0000, Jonathan Wakely wrote:
> > On Tue, 1 Feb 2022 at 23:55, Martin Sebor via Gcc-help
> > > There's plenty of literature out there that explains this, including
> > > the GCC manual, so I'd expect most C/C++ programmers to understand
> > > that.
> >
> > I disagree. So does the manual:
> >
> >       -Warray-bounds
> >       -Warray-bounds=n
> >           This option is only active when -ftree-vrp is active
> > (default for -O2 and above). It
> >           warns about subscripts to arrays that are always out of
> > bounds. This warning is
> >           enabled by -Wall.
>
> Yes, that is wrong as written.  Please open a PR?

Done: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104355

  reply	other threads:[~2022-02-02 20:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28 15:01 Dumitru Ceara
2022-01-28 15:27 ` Segher Boessenkool
2022-01-28 16:16   ` Dumitru Ceara
2022-01-28 17:37     ` Segher Boessenkool
2022-01-31 21:49     ` Martin Sebor
2022-01-31 22:01       ` Segher Boessenkool
2022-02-01  8:21         ` Jonathan Wakely
2022-02-01  5:18       ` Richard Sandiford
2022-02-01 14:42         ` Segher Boessenkool
2022-02-01 23:54         ` Martin Sebor
2022-02-02 10:12           ` Jonathan Wakely
2022-02-02 18:33             ` Segher Boessenkool
2022-02-02 20:44               ` Jonathan Wakely [this message]
2022-02-02 18:23           ` 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=CAH6eHdRTMEU1+jTPTMU10diehBDWMpOaGrVs7wij75sPrMRmHQ@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=dceara@redhat.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=msebor@gmail.com \
    --cc=richard.sandiford@arm.com \
    --cc=segher@kernel.crashing.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).