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/108980] [13 Regression] Warning text missing the warning itself (GCC 13)
Date: Thu, 09 Mar 2023 18:28:48 +0000	[thread overview]
Message-ID: <bug-108980-4-rV0XscwPoU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108980-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>:

https://gcc.gnu.org/g:c6232ba229a4fcd453b50f11351fcbd35296809c

commit r13-6559-gc6232ba229a4fcd453b50f11351fcbd35296809c
Author: Andrew Pinski <apinski@marvell.com>
Date:   Wed Mar 1 11:13:21 2023 -0800

    Fix PR 108980: note without warning due to array bounds check

    The problem here is after r13-4748-g2a27ae32fabf85, in some
    cases we were calling inform without a corresponding warning.
    This changes the logic such that we only cause that to happen
    if there was a warning happened before hand.

    Changes since
    * v1: Fix formating and dump message as suggested by Jakub.

    OK? Bootstrapped and tested on x86_64-linux-gnu with no regressions.

    gcc/ChangeLog:

            PR tree-optimization/108980
            * gimple-array-bounds.cc (array_bounds_checker::check_array_ref):
            Reorgnize the call to warning for not strict flexible arrays
            to be before the check of warned.

  parent reply	other threads:[~2023-03-09 18:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01  4:18 [Bug c++/108980] New: " thiago at kde dot org
2023-03-01  4:19 ` [Bug c++/108980] " thiago at kde dot org
2023-03-01  4:20 ` [Bug tree-optimization/108980] " pinskia at gcc dot gnu.org
2023-03-01  4:26 ` [Bug tree-optimization/108980] [13 Regression] " pinskia at gcc dot gnu.org
2023-03-01  4:27 ` pinskia at gcc dot gnu.org
2023-03-01  4:27 ` pinskia at gcc dot gnu.org
2023-03-01  7:54 ` rguenth at gcc dot gnu.org
2023-03-01 18:02 ` thiago at kde dot org
2023-03-01 18:34 ` thiago at kde dot org
2023-03-01 18:46 ` pinskia at gcc dot gnu.org
2023-03-01 19:05 ` thiago at kde dot org
2023-03-01 20:16 ` pinskia at gcc dot gnu.org
2023-03-01 23:27 ` pinskia at gcc dot gnu.org
2023-03-09 18:04 ` pinskia at gcc dot gnu.org
2023-03-09 18:28 ` cvs-commit at gcc dot gnu.org [this message]
2023-03-09 18:29 ` pinskia 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-108980-4-rV0XscwPoU@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).