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 EFBF2385800B; Wed, 26 Oct 2022 05:47:05 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EFBF2385800B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1666763225;
	bh=ciBrz/YarChsnoGaKjje0RGQZ+RsUiN+LjcP99USx8Q=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=VHmXNqhxUguXsT3FMXQQT//P70tp6nGwDfLlXyyWQ2yo7+wq5nVbYUbOhZK+yjtmT
	 elRkX4uCE1LTo1CQocHB6PqqACY7v7OdxNPN5pgnE2EsO/wDv5YEbHAQgDJCsYLKdY
	 mzLiYxcCf3tTK5hFhkj/hGV/iqkCgfBeqkd0AbuU=
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88132] Compile time and memory hog w/
 var-tracking on 32-bit targets
Date: Wed, 26 Oct 2022 05:47:01 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: compile-time-hog, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: linkw 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: cc
Message-ID: <bug-88132-4-oh3UspToWt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88132-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88132-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=3D88132

Kewen Lin <linkw at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |linkw at gcc dot gnu.org

--- Comment #3 from Kewen Lin <linkw at gcc dot gnu.org> ---
(In reply to Arseny Solokha from comment #2)
> I cannot reproduce it anymore w/ gcc 13.0.0 20221016 snapshot
> (g:6366e3e8847af98d4728d55951534769d034d02a) and w/ gcc 12.2.

Should we check the release branches gcc-10 and gcc-11? Or can we just
aggressively close this? since the original release gcc-9 which this PR was
opened against isn't an active branch any more and this issue doesn't exist=
 on
latest branch gcc-12 and trunk?=