public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amodra at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/101977] [12 Regression] array subscript 0 is outside array bounds
Date: Wed, 25 Aug 2021 00:11:50 +0000	[thread overview]
Message-ID: <bug-101977-4-DBjyLg6Rn7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101977-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Alan Modra <amodra at gmail dot com> ---
(In reply to Martin Sebor from comment #5)
> The -Warray-bounds for section.c is gone
Thanks for fixing that.

> but last night's build still shows
> a large number of -Warray-bounds instances as well as other warnings for
> Binutils &  GDB.
I built gcc and binutils+gdb just now and see that these are all in sim/ with
the exception of -Wconflicts-sr and -Wconflicts-rr bison warnings, and this
libstdc++ warning:

home/alan/build/gcc-virgin/prev-x86_64-linux/libstdc++-v3/include/bits/stl_algo.h:1869:32:
error: array subscript 19 is outside array bounds of ‘void [136]’
[-Werror=array-bounds]

      parent reply	other threads:[~2021-08-25  0:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-19 11:47 [Bug tree-optimization/101977] New: " amodra at gmail dot com
2021-08-19 21:06 ` [Bug tree-optimization/101977] " msebor at gcc dot gnu.org
2021-08-19 21:07 ` [Bug tree-optimization/101977] [12 Regression] " msebor at gcc dot gnu.org
2021-08-23 23:41 ` msebor at gcc dot gnu.org
2021-08-24 16:49 ` cvs-commit at gcc dot gnu.org
2021-08-24 16:50 ` msebor at gcc dot gnu.org
2021-08-24 16:50 ` msebor at gcc dot gnu.org
2021-08-24 17:01 ` msebor at gcc dot gnu.org
2021-08-25  0:11 ` amodra at gmail dot com [this message]

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=bug-101977-4-DBjyLg6Rn7@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).