From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A49F43858D33; Thu, 4 Jan 2024 21:10:02 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A49F43858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1704402602; bh=D/vig8op37Ymxu+3JqZGGyT6DJAZDGZXpunvf3ISoCs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=OK9JormRc1vKpOQiGSxzv9OfdC/GergEFuxhHnp/7++QJii/tz50srfn8QByIWwmS /6tykrjjpS5NPi+IzQVdYeO4GsvPbH88QFUx6Xbi0jkDEMbBNpTfO9HuBGCvmHygUB nrFjERZyiYm8t9iJ72pXU98hoC4Vo4j+aTM9XBaM= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113239] [13 regression] After 822a11a1e64, bogus -Warray-bounds warnings in std::vector Date: Thu, 04 Jan 2024 21:10:02 +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: 14.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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=3D113239 --- Comment #1 from Andrew Pinski --- So I suspect it is either inlining differences due to slightly increased si= zes in some cases or jump threading due to the extra check. I highly doubt that patch is underlying cause of the warning ...=