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 B4AB83857814; Fri, 23 Sep 2022 08:28:01 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B4AB83857814
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1663921681;
	bh=KtyBJ3m+NqI44XqbEUgkohJK4v3gu2Uh5XtI8tDNcRs=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=p/MSm+YGOlDbVsi2d/LyIPJgG7ffnfXnX6C76+DoQwS6naz+h9FPNQ7Z4UThID/zk
	 GeHNXjC0JZLOjaD1LntyCBpFRYqh7+B1pWTTKbKJbS0cbP26lSFuhiiq04vz73uejx
	 z7cWwRp+6JRm5DijSEAB2Wbh1ppjAgWBpudPJYDc=
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/107014] flatten+lto fails the kernel build
Date: Fri, 23 Sep 2022 08:28:01 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 12.1.1
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov 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: 
Message-ID: <bug-107014-4-sxFoKmvuZV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107014-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107014-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=3D107014

--- Comment #5 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
(In reply to Jiri Slaby from comment #4)
> > I am surprised that "flatten" blows up on this function. Is that with a=
ny
> > config, or again some specific settings like gcov? Is there an existing=
 lkml
> > thread about this?
>=20
> Yes, linked in the commit log:
> https://lore.kernel.org/all/
> CAK8P3a2ZWfNeXKSm8K_SUhhwkor17jFo3xApLXjzfPqX0eUDUA@mail.gmail.com/

I mean now, about compile time blowup with LTO.=