public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/101374] [12 Regression] bootstrap failure varpool.c:490:19: error: array subscript 'varpool_node[0]' is partly outside array bounds of 'varpool_node [0]' [-Werror=array-bounds]
Date: Thu, 08 Jul 2021 17:44:27 +0000	[thread overview]
Message-ID: <bug-101374-4-PYuE4cftn8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101374-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Sebor <msebor@gcc.gnu.org>:

https://gcc.gnu.org/g:9bf9f27ac6db4823628c435da9b242fd82bf8d68

commit r12-2171-g9bf9f27ac6db4823628c435da9b242fd82bf8d68
Author: Martin Sebor <msebor@redhat.com>
Date:   Thu Jul 8 11:34:27 2021 -0600

    Use Object Size Type zero for -Warray-bounds [PR101374].

    Resolves:
    PR bootstrap/101374 - -Warray-bounds accessing a member subobject as
derived

    gcc/cp/ChangeLog:
            PR bootstrap/101374
            * module.cc (module_state::read_macro_maps): Temporarily disable
            -Warray-bounds.
            (module_state::install_macros): Same.

    gcc/ChangeLog:
            PR bootstrap/101374
            * gimple-array-bounds.cc (array_bounds_checker::check_mem_ref):
            Use Object Size Type 0 instead of 1.

    gcc/testsuite/ChangeLog:
            PR bootstrap/101374
            * c-c++-common/Warray-bounds-3.c: Xfail assertion.
            * c-c++-common/Warray-bounds-4.c: Same.

  parent reply	other threads:[~2021-07-08 17:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-08  7:43 [Bug bootstrap/101374] New: " rguenth at gcc dot gnu.org
2021-07-08  7:44 ` [Bug bootstrap/101374] " rguenth at gcc dot gnu.org
2021-07-08  7:48 ` rguenth at gcc dot gnu.org
2021-07-08  8:50 ` rguenth at gcc dot gnu.org
2021-07-08  9:22 ` rguenth at gcc dot gnu.org
2021-07-08  9:26 ` rguenth at gcc dot gnu.org
2021-07-08 10:46 ` schwab@linux-m68k.org
2021-07-08 14:47 ` schwab@linux-m68k.org
2021-07-08 14:47 ` schwab@linux-m68k.org
2021-07-08 14:49 ` msebor at gcc dot gnu.org
2021-07-08 15:47 ` msebor at gcc dot gnu.org
2021-07-08 17:44 ` cvs-commit at gcc dot gnu.org [this message]
2021-07-08 18:04 ` msebor at gcc dot gnu.org
2021-07-08 21:20 ` bergner at gcc dot gnu.org
2021-07-08 22:13 ` msebor at gcc dot gnu.org
2021-07-10  2:49 ` cvs-commit at gcc dot gnu.org
2021-07-13 16:10 ` msebor at gcc dot gnu.org
2021-07-16 16:33 ` abidh at gcc dot gnu.org

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-101374-4-PYuE4cftn8@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).