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 0429A3858288; Wed, 20 Mar 2024 20:32:58 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0429A3858288
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1710966779;
	bh=6XoHMKeqrpMH9rEwFLDUPK+di9l7UsWnokDrKHDdI2Y=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=ouHh+urIG4oNt0knttSmWugRuRT7OadAw5Glyy+v8Rr+bDekPJNG59dnhsDQPb5B7
	 5DDtViBuIIIpO8WAyewFjFCvnB0GMAoxIvq1llGTLAJQ8X6FzWU3zuPjfqd2h6Se4+
	 BNzlP1EMu+ZtFBmfhpmStWw+qrNM/vKLwNFdMi6M=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110316] [11/12/13/14 Regression]
 g++.dg/ext/timevar1.C and timevar2.C fail erratically
Date: Wed, 20 Mar 2024 20:32:58 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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-110316-4-z0VuxePVzH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110316-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110316-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=3D110316

--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to seurer from comment #6)
> Was this only fixed for trunk?  I started seeing it for gcc 13:

Yes it was only fixed on the trunk. The ICE only happens when -ftime-report=
 is
used which most folks won't run into the issue and it only happens when the=
re
is a short time spent in many of the passes so it won't show up when folks =
try
to use -ftime-report to see where the time is mostly spent. So backporting
seems not high priority except to have a clean testsuite results.=