mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: switch to thin archives
Date: Mon, 19 Jun 2017 17:45:21 +1000	[thread overview]
Message-ID: <20170619174521.277a9402@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <20170618100426.GB20211@amd>

On Sun, 18 Jun 2017 12:04:26 +0200
Pavel Machek <pavel@ucw.cz> wrote:

> On Fri 2017-06-02 22:54:54, Nicholas Piggin wrote:
> > Switch from incremental build to thin archives for packaging built-in.o.
> > binutils version must be bumped to 2.20. Proposed patch for 4.13.
> > 
> > Signed-off-by: Nicholas Piggin <npiggin@gmail.com>  
> 
> You should explain any advantage this is supposed to have.

Hi Pavel,

You're right, sorry for this, I was spamming the list with a quick
hack to try to get 0day to pick up the patch.

Most of the discussion has been going on in other patch series (check
linux-kbuild).

There are 3 main categories of advantages.

First is reduced size of intermediate artifacts in the build output
tree.

Second is that incremental linking constrains the linker because it
has to assemble each section in the output as a sequence of those
section from the inputs. So the more incremental linking, the more
you constrain the linker, and this can end up resulting in link fail
with large kernels on some architectures.

Third is that some link-time optimizations are not compatible or
not very optimal with incremental linking, whereas thin archives
is much more amenable to such things.

Thanks,
Nick

  reply	other threads:[~2017-06-19  7:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02 12:54 Nicholas Piggin
2017-06-02 20:57 ` kbuild test robot
2017-06-02 20:57 ` kbuild test robot
2017-06-03  6:51   ` Nicholas Piggin
2017-06-18 10:04 ` Pavel Machek
2017-06-19  7:45   ` Nicholas Piggin [this message]
2017-06-19  9:15     ` Pavel Machek

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=20170619174521.277a9402@roar.ozlabs.ibm.com \
    --to=npiggin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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

all inboxes | Powered by JetHome®