From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A2675385828B; Fri, 23 Sep 2022 10:12:21 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A2675385828B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1663927941; bh=3Gm/8CY/z7ecpcOCao56BQOrAMIk4eoge+eRdlyEgPc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=sCFZngJNVcxMyNbIdjH4xShNtB0McxABmCvPyVr7wxggtVn5anA25P8a2hBR2jiu5 8mWKawJmUPEPGmRtQl7O6t8aVYqjGmzQRo7+2NkR/Mk0ILa0FY5PA+1RHsJykdSmhi 5kSd5hzGgQhzWLKhMxqOrTaA3rHnGrLnpv2tKxGY= From: "amonakov at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/107014] flatten+lto fails the kernel build Date: Fri, 23 Sep 2022 10:12:21 +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: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107014 --- Comment #7 from Alexander Monakov --- I wanted to understand what gets exposed in LTO mode that causes a blowup. I'd say flatten is not appropriate for this function (I don't think you wan= t to force inlining of memset or _find_next_bit?), so might be better to go back= to the original issue and solve the problem in a more focused way (e.g. force-inlining the function which needs to access __initdata if you really = need the verification that triggers otherwise).=