public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Jack Howarth <howarth@nitro.med.uc.edu>
Cc: binutils@sources.redhat.com, libc-alpha@sources.redhat.com
Subject: Re: -z combreloc
Date: Sat, 13 Oct 2001 13:32:00 -0000	[thread overview]
Message-ID: <20011013223456.B666@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <200110132014.QAA34332@nitro.msbb.uc.edu>

On Sat, Oct 13, 2001 at 04:14:16PM -0400, Jack Howarth wrote:
> howarth@bogus:~/debian6/zip-2.30$ LD_DEBUG=statistics ./zip 
> 08344:                   number of relocations: 256
> 08344:        number of relocations from cache: 99

This means ld.so does 355 symbol lookups, 99 of them are served from lookup
cache, the rest are looked up.

> ...after prelinking this binary I got...
> 
> howarth@bogus:~/debian6/zip-2.30$ LD_DEBUG=statistics ./zip
> 08355:                   number of relocations: 0
> 08355:        number of relocations from cache: 16

This means prelinking could be used, so no symbol lookups, just 16 conflicts
were applied (conflicts are always Rela relocs against symidx 0, so no
lookup).

> prelink: /lib/libncurses.so.5.2: Not enough room to add .dynamic entry

This means libncurses.so.5.2 was not rebuilt with recent binutils
(particularly there are no spare .dynamic section entries which prelink
needs for its work).

> under a newer binutils but all libs linked in have to
> be as well. Is this true?

Sure.

>     Lastly back to -z combreloc...is there a good way to
> benchmark any speed up gained by recompiling with that 
> option enabled in binutils? Jakub seems to have different
> output from LD_DEBUG=statistics than we do (he can get

The difference is that glibc powerpc port doesn't support HP_TIMING_*.
From what I understand, there is mftb instruction on ppc which sets a
register to current timer value, but it is not supported on some earlier PPC
CPUs and it looks like it is 32-bit only (right?). In this case, someone
would need to hack up some way how to configure glibc which would not
support these older PPC CPUs and, assuming it is really 32-bit only and thus
overflows quickly, look at Alpha HP_TIMING_* which is limited for short time
periods too.

	Jakub

  reply	other threads:[~2001-10-13 13:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-13 13:15 Jack Howarth
2001-10-13 13:32 ` Jakub Jelinek [this message]
2001-10-13 13:53 ` Andrew Cagney
2001-10-13 15:30   ` Christopher C. Chimelis
2001-10-13 17:58     ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2001-10-13 18:38 Jack Howarth
2001-10-13 19:01 ` Andrew Cagney
2001-10-13 19:14   ` Christopher C. Chimelis
2001-10-13 20:12 ` Andrew Cagney
2001-10-14  8:29   ` Daniel Jacobowitz
2001-10-14  8:46     ` Andrew Cagney
2001-10-13 10:47 Jack Howarth
2001-10-13 12:25 ` Andrew Cagney
2001-10-13 13:20 ` Jakub Jelinek

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=20011013223456.B666@sunsite.ms.mff.cuni.cz \
    --to=jakub@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=howarth@nitro.med.uc.edu \
    --cc=libc-alpha@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).