From: Segher Boessenkool <segher@kernel.crashing.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Nicholas Piggin <npiggin@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Luis R. Rodriguez" <mcgrof@kernel.org>,
linux-next@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Fengguang Wu <fengguang.wu@intel.com>,
linuxppc-dev@lists.ozlabs.org, Guenter Roeck <linux@roeck-us.net>
Subject: Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures
Date: Wed, 3 Aug 2016 14:44:29 -0500 [thread overview]
Message-ID: <20160803194429.GA14627@gate.crashing.org> (raw)
In-Reply-To: <3892328.nUGXIq3MaH@wuerfel>
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@2.5Ghz, 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
next prev parent reply other threads:[~2016-08-03 19:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 20:07 powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures Luis R. Rodriguez
2016-08-02 21:58 ` Guenter Roeck
2016-08-02 22:02 ` Luis R. Rodriguez
2016-08-02 22:34 ` Arnd Bergmann
2016-08-03 0:23 ` Stephen Rothwell
2016-08-03 7:52 ` Arnd Bergmann
2016-08-03 12:19 ` Stephen Rothwell
2016-08-03 12:29 ` Arnd Bergmann
2016-08-03 15:37 ` Nicholas Piggin
2016-08-03 18:52 ` Arnd Bergmann
2016-08-03 19:44 ` Segher Boessenkool [this message]
2016-08-03 20:13 ` Arnd Bergmann
2016-08-11 12:43 ` Nicholas Piggin
2016-08-11 13:04 ` Arnd Bergmann
2016-08-11 13:12 ` Nicholas Piggin
2016-08-11 13:49 ` [TESTING] kbuild: link drivers subdirectories separately Arnd Bergmann
2016-08-11 15:46 ` Arnd Bergmann
2016-08-04 0:10 ` powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures Stephen Rothwell
2016-08-04 9:00 ` Arnd Bergmann
2016-08-04 10:37 ` Arnd Bergmann
2016-08-04 11:47 ` Nicholas Piggin
2016-08-04 12:09 ` Arnd Bergmann
2016-08-04 12:31 ` Nicholas Piggin
2016-08-04 13:54 ` Nicholas Piggin
2016-08-04 15:43 ` Arnd Bergmann
2016-08-04 16:10 ` Arnd Bergmann
2016-08-04 17:06 ` Segher Boessenkool
2016-08-05 8:41 ` Nicholas Piggin
2016-08-05 10:17 ` Arnd Bergmann
2016-08-05 12:26 ` Nicholas Piggin
2016-08-05 16:01 ` Arnd Bergmann
2016-08-05 16:16 ` Nicholas Piggin
2016-08-05 19:16 ` Arnd Bergmann
2016-08-06 4:17 ` Nicholas Piggin
2016-08-06 21:13 ` Arnd Bergmann
2016-08-03 2:46 ` Michael Ellerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160803194429.GA14627@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=arnd@arndb.de \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mcgrof@kernel.org \
--cc=npiggin@gmail.com \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).