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 tree-optimization/105726] [10/11/12 Regression] spurious warning with -Warray-bounds
Date: Thu, 02 Jun 2022 09:40:05 +0000	[thread overview]
Message-ID: <bug-105726-4-PCx5haPvvh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105726-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:

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

commit r12-8452-g9bc27ee76d510360637c9578ffdefeab5c336e86
Author: Richard Biener <rguenther@suse.de>
Date:   Wed May 25 11:49:03 2022 +0200

    tree-optimization/105726 - adjust array bound heuristic

    There's heuristic to detect ptr[1].a[...] out of bound accesses
    reasoning that if ptr points to an array of aggregates a trailing
    incomplete array has to have size zero.  The following more
    thoroughly constrains the cases this applies to avoid false
    positive diagnostics.

    2022-05-25  Richard Biener  <rguenther@suse.de>

            PR tree-optimization/105726
            * gimple-ssa-warn-restrict.cc
(builtin_memref::set_base_and_offset):
            Constrain array-of-flexarray case more.

            * g++.dg/warn/Warray-bounds-27.C: New testcase.

    (cherry picked from commit e7c482b08076bb299742883c4ffd65b31e33200c)

  parent reply	other threads:[~2022-06-02  9:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-25  4:10 [Bug c++/105726] New: " cuzdav at gmail dot com
2022-05-25  7:42 ` [Bug c++/105726] " rguenth at gcc dot gnu.org
2022-05-25  8:39 ` rguenth at gcc dot gnu.org
2022-05-25  8:41 ` rguenth at gcc dot gnu.org
2022-05-25  9:46 ` rguenth at gcc dot gnu.org
2022-05-25  9:52 ` [Bug tree-optimization/105726] [10/11/12/13 Regression] " rguenth at gcc dot gnu.org
2022-05-27  9:42 ` cvs-commit at gcc dot gnu.org
2022-05-27  9:43 ` [Bug tree-optimization/105726] [10/11/12 " rguenth at gcc dot gnu.org
2022-06-02  9:40 ` cvs-commit at gcc dot gnu.org [this message]
2022-06-15  8:59 ` [Bug tree-optimization/105726] [10/11 " cvs-commit at gcc dot gnu.org
2022-06-15  9:49 ` cvs-commit at gcc dot gnu.org
2022-06-15  9:50 ` rguenth 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-105726-4-PCx5haPvvh@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).