[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160803194429.GA14627@gate.crashing.org>
Date: Wed, 3 Aug 2016 14:44:29 -0500
From: Segher Boessenkool <segher@...nel.crashing.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: Nicholas Piggin <npiggin@...il.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Luis R. Rodriguez" <mcgrof@...nel.org>,
linux-next@...r.kernel.org, Paul Mackerras <paulus@...ba.org>,
Fengguang Wu <fengguang.wu@...el.com>,
linuxppc-dev@...ts.ozlabs.org, Guenter Roeck <linux@...ck-us.net>
Subject: Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures
Hi Arnd,
On Wed, Aug 03, 2016 at 08:52:48PM +0200, Arnd Bergmann wrote:
> From my first look, it seems that all of lib/*.o is now getting linked
> into vmlinux, while we traditionally leave out everything from lib/
> that is not referenced.
>
> I also see a noticeable overhead in link time, the numbers are for
> a cache-hot rebuild after a successful allyesconfig build, using a
> 24-way Opteron@...Ghz, just relinking vmlinux:
>
> $ time make skj30 vmlinux # before
> real 2m8.092s
> user 3m41.008s
> sys 0m48.172s
>
> $ time make skj30 vmlinux # after
> real 4m10.189s
> user 5m43.804s
> sys 0m52.988s
Is it better when using rcT instead of rcsT?
Segher
Powered by blists - more mailing lists