From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f65.google.com ([209.85.220.65]:33402 "EHLO mail-pa0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750765AbcHWGaQ (ORCPT ); Tue, 23 Aug 2016 02:30:16 -0400 Date: Tue, 23 Aug 2016 16:17:39 +1000 From: Nicholas Piggin Subject: Re: [PATCH 0/6 v2] kbuild changes, thin archives, --gc-sections Message-ID: <20160823161739.0f4f7337@roar.ozlabs.ibm.com> In-Reply-To: <1470910580-18458-1-git-send-email-npiggin@gmail.com> References: <1470910580-18458-1-git-send-email-npiggin@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: linux-kbuild@vger.kernel.org Cc: linux-arch@vger.kernel.org, Michal Marek , Sam Ravnborg , Stephen Rothwell , Arnd Bergmann , Nicolas Pitre , Segher Boessenkool , Alan Modra On Thu, 11 Aug 2016 20:16:14 +1000 Nicholas Piggin wrote: > Hi, > > I would like to submit the kbuild changes in patches 1-3 for > consideration. > > I've taken on the feedback, so thanks everybody for that. The > biggest change since last time is a more general way for > architectures to do a post-link pass in patch 3. > > On the question of whether to enable thin archives unconditionally, > I prefer to have architectures enable them as they are tested. But > I would like to see everybody moved as soon as possible and the > incremental linking removed. > > All patches should be basically noops without arch enablement, > so I include initial powerpc enablement in patches 4-6 for > reference, but I will submit those via powerpc maintainer if > the kbuild changes are merged. Hi Michal, I'm wondering what your thoughts are with this series? Sam had some other comment on patch 3, but I think it has come to a matter of preference. I don't mind too much, so I can change it to whatever people prefer (sh or makefile). And did you want me to re-post the series, or are you happy to take updated patches from replies? The ARM slowness with allyesconfig builds with thin archives was a linker workaround for a processor bug that they don't need to enable for allyesconfig build anyway. I provided them a patch to avoid that. For usual sized builds, it's not noticeable. Thanks, Nick