All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Alan Modra <amodra@bigpond.net.au>,
	Roland McGrath <roland@redhat.com>,
	Paul Mackerras <paulus@samba.org>,
	David Miller <davem@davemloft.net>, Adrian Bunk <bunk@stusta.de>,
	linux-kernel@vger.kernel.org
Subject: Re: "build-id" changes break sparc64
Date: Mon, 23 Jul 2007 20:00:48 +0200	[thread overview]
Message-ID: <20070723180048.GA8268@uranus.ravnborg.org> (raw)
In-Reply-To: <20070723114936.GH21668@ftp.linux.org.uk>

On Mon, Jul 23, 2007 at 12:49:36PM +0100, Al Viro wrote:
> On Mon, Jul 23, 2007 at 06:55:59PM +0930, Alan Modra wrote:
> > On Mon, Jul 23, 2007 at 10:14:35AM +0200, Sam Ravnborg wrote:
> > > But I would still like to hear from Alan what the benefits are.
> > 
> > See http://sourceware.org/ml/binutils/2004-10/msg00178.html
> 
> What does _not_ doing intermediates do to memory footprint of ld(1)
> and time spent in there?

x86_64 defconfig

rm vmlinux*; time make vmlinux

Vanilla tree: ~7,7 sec
With single shot ld (Roland's patch): 8,3 secs

So as expected slower. As we link twice the cost is ~0,3 sec 
for a x86_64 defconfig link on my box.

So it should be beneficial to do it and Alan's link did not really
convince me for the kernel usage.
Al - do you have any input there?

	Sam

  reply	other threads:[~2007-07-23 17:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-22  8:23 "build-id" changes break sparc64 David Miller
2007-07-22  8:59 ` Roland McGrath
2007-07-23  2:18   ` David Miller
2007-07-23  6:01 ` Roland McGrath
2007-07-23  6:13   ` Paul Mackerras
2007-07-23  6:27     ` Sam Ravnborg
2007-07-23  7:26       ` Roland McGrath
2007-07-23  8:14         ` Sam Ravnborg
2007-07-23  8:18           ` Roland McGrath
2007-07-23  8:24             ` Sam Ravnborg
2007-07-23  9:25           ` Alan Modra
2007-07-23 11:49             ` Al Viro
2007-07-23 18:00               ` Sam Ravnborg [this message]
2007-07-23 18:56                 ` Al Viro
2007-07-23 19:13                   ` Adrian Bunk
2007-07-23 19:12                 ` Roland McGrath
2007-07-23 19:39                   ` Al Viro
2007-07-23 20:05                     ` Roland McGrath
2007-07-23 20:33                       ` Sam Ravnborg
2007-07-23  6:14   ` [PATCH] Move --build-id option Roland McGrath
2007-07-23  6:42     ` Sam Ravnborg
2007-07-23  8:09       ` Roland McGrath
2007-07-23  8:12       ` [PATCH] Use LDFLAGS_MODULE only for .ko links Roland McGrath
2007-07-23  8:16         ` Sam Ravnborg
2007-07-23  6:22   ` "build-id" changes break sparc64 Sam Ravnborg

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=20070723180048.GA8268@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=amodra@bigpond.net.au \
    --cc=bunk@stusta.de \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=roland@redhat.com \
    --cc=viro@ftp.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.