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 D38E73858431; Tue, 14 Mar 2023 08:12:01 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D38E73858431
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1678781521;
	bh=uChPOqQ1ErIrwdMYpGQgctLCAQNGnG/ad+A2P5/4MnY=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Zo4cAXAvgSVwTv++Nb3+x7zgN+i4wmXTbvuNW+AnSLHzXjdoo4hS5Jt7MQMIHy4Rt
	 0UufuhQ6ZPxOUpIz6GXWNQgT5pT/ueNpuKMRhIKTT146q9YZpRlJIg+7g+/xdWYYJI
	 p5AygUHDWr7ZV+MHjnpBbAUOZvXvcAEw6schzb3g=
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109087] [13 Regression] csmith: end of year runtime bug
 since r13-4839-geef81eefcdc2a581
Date: Tue, 14 Mar 2023 08:12:01 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 13.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-109087-4-so230Y8vFe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109087-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109087-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=3D109087

--- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I didn't mean for GCC 13, we need to fix the actual backend bug regardless =
and
so a DSE improvement can't be considered a fix... ;)
Just the DSE thing happens very often with -ftrivial-auto-var-init=3D.
I wonder if even after your improvement we don't keep .DEFERRED_INIT for un=
used
vars for the case when the DSE walk will run into the vdef/vuse limits (I
assume it doesn't do unbounded walk).  Perhaps some special handling of
.DEFERRED_INITs for vars which have solely those statements and clobbers and
nothing else?=