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 52D7A3858025; Fri, 10 Feb 2023 22:03:28 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 52D7A3858025
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1676066608;
	bh=UgKegFpjPTEu0uRUMRKA82IxThJ48x5q9y3YExNXnXI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=sqna/ZsBqSNHwrW6r2JxY3FHhX6YSbHMWPfNelf+YNDyCUBLKCz+AZMLVFRmbMcBt
	 +LYD4NSOD0gFXw01Vl1AJqrNID4ZpvcA9xqUtoJ1srpAVxFtvS2BReJFzKP0na3e9V
	 wuEVgdTMP51lsDK+ygakD9/c9tPW0sOg2mPYjy1Q=
From: "rimvydas.jas at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108705] [13 Regression] Unexpected CPU time
 usage with LTO in ranger propagation
Date: Fri, 10 Feb 2023 22:03:28 +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: 13.0
X-Bugzilla-Keywords: compile-time-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rimvydas.jas at gmail dot com
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: 13.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: resolution bug_status
Message-ID: <bug-108705-4-ECp0jADcvY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108705-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108705-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=3D108705

Rimvydas (RJ) <rimvydas.jas at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|WAITING                     |RESOLVED

--- Comment #10 from Rimvydas (RJ) <rimvydas.jas at gmail dot com> ---
Fixed by g:6493b7af37e473a89c67afab474330f931dd8447 no more issues in ltrans
partitions=