From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 037063858D33; Wed,  9 Aug 2023 09:21:19 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 037063858D33
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1691572880;
	bh=QsQy+JjA5Vklfrz1X8O4esofMow0MUOob8XIDijj8/c=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=qUEOWY3bWDK7CibBBzWGv1e0kArF/Sn3p7xzj12I++c07iNvvjH1IALWAo1DAbKlx
	 KH9Dw6yPkhMBe5/MED8flj+Q3fanJoK1uhfROwwePMEY2nLEkQwSQe3zbIW0hPpwA0
	 C2+lbQtekYRR8Y0zAaRnxyWod6MsVGsuKxFVwCbM=
From: "sirl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110458] [14 Regression] -Warray-bounds=2 new
 false positive
Date: Wed, 09 Aug 2023 09:21:16 +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: sirl 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: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-110458-4-YwteNU8U6u@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110458-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110458-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

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

--- Comment #3 from Franz Sirl <sirl at gcc dot gnu.org> ---
Actually Comment 2 is only true for the original testcode (which was quite
fragile to reproduce). The reduced testcode started to fail with the backwa=
rds
jump threader rewrite in r12-2591-g2e96b5f14e4025691b57d2301d71aa6092ed44bc=
 and
a simple -Warray-bounds. This is proven by the fact that compiling the test=
case
with gcc@r12-2591 with an additional --param=3Dthreader-mode=3Dlegacy makes=
 the
warning go away.

So this bug maybe a duplicate of the other bugs (couldn't find a metabug)
related to r12-2591.=