Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1668575 > unrolled thread

Re: [PATCH] kbuild: switch to thin archives

Started byPavel Machek <pavel@ucw.cz>
First post2017-06-18 12:10 +0200
Last post2017-06-19 11:20 +0200
Articles 3 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH] kbuild: switch to thin archives Pavel Machek <pavel@ucw.cz> - 2017-06-18 12:10 +0200
    Re: [PATCH] kbuild: switch to thin archives Nicholas Piggin <npiggin@gmail.com> - 2017-06-19 09:50 +0200
      Re: [PATCH] kbuild: switch to thin archives Pavel Machek <pavel@ucw.cz> - 2017-06-19 11:20 +0200

#1668575 — Re: [PATCH] kbuild: switch to thin archives

FromPavel Machek <pavel@ucw.cz>
Date2017-06-18 12:10 +0200
SubjectRe: [PATCH] kbuild: switch to thin archives
Message-ID<tTFjz-3Kq-3@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

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.

									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[toc] | [next] | [standalone]


#1668867

FromNicholas Piggin <npiggin@gmail.com>
Date2017-06-19 09:50 +0200
Message-ID<tTZBD-89S-3@gated-at.bofh.it>
In reply to#1668575
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

[toc] | [prev] | [next] | [standalone]


#1668925

FromPavel Machek <pavel@ucw.cz>
Date2017-06-19 11:20 +0200
Message-ID<tU10L-Jx-37@gated-at.bofh.it>
In reply to#1668867

[Multipart message — attachments visible in raw view] — view raw

On Mon 2017-06-19 17:45:21, Nicholas Piggin wrote:
> 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 for explanation. I checked, and binutils version bumb will not
affect me, but...
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web