From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-x241.google.com (mail-pf0-x241.google.com [IPv6:2607:f8b0:400e:c00::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3s4rz01h4MzDqS9 for ; Thu, 4 Aug 2016 23:54:36 +1000 (AEST) Received: by mail-pf0-x241.google.com with SMTP id h186so18129447pfg.2 for ; Thu, 04 Aug 2016 06:54:36 -0700 (PDT) Date: Thu, 4 Aug 2016 23:54:18 +1000 From: Nicholas Piggin To: Arnd Bergmann Cc: Stephen Rothwell , Nicolas Pitre , "linux-kernel@vger.kernel.org" , "Luis R. Rodriguez" , linux-next@vger.kernel.org, Paul Mackerras , Fengguang Wu , linuxppc-dev@lists.ozlabs.org, Guenter Roeck Subject: Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures Message-ID: <20160804235418.1f235f55@roar.ozlabs.ibm.com> In-Reply-To: <20160804223139.0196b3aa@roar.ozlabs.ibm.com> References: <1880505.MpH3ISbtMJ@wuerfel> <20160804214713.4baa832e@roar.ozlabs.ibm.com> <4007331.2ypSqpxHsb@wuerfel> <20160804223139.0196b3aa@roar.ozlabs.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, 4 Aug 2016 22:31:39 +1000 Nicholas Piggin wrote: > On Thu, 04 Aug 2016 14:09:02 +0200 > Arnd Bergmann wrote: > > Nicolas Pitre has done some related work, adding him to Cc. IIRC we have > > actually had multiple implementations of -ffunction-sections/--gc-sections > > in the past that people have used in production, but none of them > > ever made it upstream. After some googling around it seems lto has been difficult to get in and it was agreed this gc-sections should be done first anyway (although it may indeed provide a superset of DCE, but it's always going to be more costly and complicated). Lto would have the same issue with liveness of entry points, which is really the only thing you need change in the kernel as far as I can see. I didn't really see what problems people were having with it though, so maybe it's architecture specific or something I haven't run into yet. Thanks, Nick