From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4D8C23858D20; Thu, 9 Mar 2023 18:28:48 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4D8C23858D20 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1678386528; bh=gDi7Enzgp1QHsq5uUfu4TO4/ZTYRnHVWmJazXvoGSJ0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=lyOSl9RZvsHGIbtfiqi4ug1N7vwdvKYkRmXqb8MYxP4+vDK2he5+sXAgwdDuro63H iXigU0CcYqOsPYK8vuF/cOWpwuond9vSQ3rSdi0FdtFAPMNY5HpQEfvzYzr9tNfaNX SEuvKXGH57ZMTV1oVcNg5lJOAz5NYS31zhb03uJk= From: "cvs-commit at gcc dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: diagnostic, patch X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: pinskia at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108980 --- Comment #13 from CVS Commits --- The trunk branch has been updated by Andrew Pinski : https://gcc.gnu.org/g:c6232ba229a4fcd453b50f11351fcbd35296809c commit r13-6559-gc6232ba229a4fcd453b50f11351fcbd35296809c Author: Andrew Pinski 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.=