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 CAC47385828B; Fri, 23 Sep 2022 09:52:27 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CAC47385828B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1663926747;
	bh=n6ZXq0yF5EFeSRHt23aMy8Ug00Abp+4N7NicY3sJXT8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=QnpNWTwbh6OAmLAHuGSKw9uiDO8lRPlVmecvkZj7ozw1rN5e8FYiQEuUF7MVl9zua
	 F0sUAx7vEBk390iPzKWtsJ8HwGKgh8JzklHV8mSJMzHbO9fKrsRdDE009BKbewLhoI
	 OX45qW2gFIlwqQx2gSwDPChpNaPNXeF0PSI4/Xkw=
From: "jirislaby at gmail dot com" <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 09:52:27 +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: jirislaby at gmail dot com
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-jU8IPBBdPC@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 #6 from Jiri Slaby <jirislaby at gmail dot com> ---
(In reply to Alexander Monakov from comment #5)
> I mean now, about compile time blowup with LTO.

No, LTO is not supported by upstream (yet) ;).

The point is what should I do when submitting the LTO support. Disabling
flatten in the kernel completely does not sound about right. I wanted to
confirm that this is not a compiler issue -- you guys say the function shoo=
ts
to its leg by __flatten__.

So thinking about the best approach...=