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 228193858C62; Tue, 11 Jul 2023 08:01:25 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 228193858C62
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1689062485;
	bh=NuoMyjWXSy+SEUSSTpqVJmS38CrxmyZrW0ff6V6xjNw=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=VgZgJnO8dcshTJDtrSMyjrAH50lCaj0SnWxRuWg2FfDOrVQxHysqy84klZI0Q1gbd
	 NO7PQfTnv+nQFXwBRs/YmYWlLFimmS5k1ai8Vnd2XQn3SP3pT0UGPX/PkD5ZYTuGNJ
	 2sDJeuuK48MEi7dNMrSE5BkSMGTDvCnqWZBnX1lk=
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110620] spurious array-bounds
Date: Tue, 11 Jul 2023 08:01:19 +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: 12.1.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
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: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-110620-4-H8gIM6kDfX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110620-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110620-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=3D110620

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2023-07-11
     Ever confirmed|0                           |1

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.  We diagnose

  _41 =3D operator new (8);

  <bb 3> [local count: 1014634345]:
  # iftmp.3_28 =3D PHI <_41(2)>
...
  <bb 9> [local count: 507317173]:=20
  MEM[(struct value_type &)iftmp.3_28 + 24].first =3D 0;

and this access _is_ out of bounds, it's just in an unreachable path we
have not yet proved to be unreachable.=