All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] Enable --hash-style=both for all recent gcc4 targets
Date: Wed, 15 Oct 2008 12:31:39 +0100	[thread overview]
Message-ID: <1224070299.5189.62.camel@ted> (raw)
In-Reply-To: <gd4j24$lq3$1@ger.gmane.org>

On Wed, 2008-10-15 at 13:09 +0200, Koen Kooi wrote:
> On 15-10-2008 12:43, Leon Woestenberg wrote:
> > On Wed, Oct 15, 2008 at 10:22 AM, Holger Freyther<zecke@selfish.org>  wrote:
> >> Hey guys,
> >>
> >> I would start linking everything with -Wl,--hash-style=both as this is said to
> >> speed up the loading of shared libraries by about 50% (google is your
> >>
> > If we care about dynamic link speed we should maybe revisit the rpath issue.
> >
> > I remember seeing strace's where on each .so, 10 attempts were made
> > before the right location was attempted.
> >
> > Actually, it is still on my to do:
> >
> > http://bugs.openembedded.net/show_bug.cgi?id=2140
> 
> Doesn't insane.bbclass log bad rpaths? Or are you talking about spurious 
> rpaths that don't point to staging or workdir?
> AIUI libtool 2.x should solve a lot of these.

I think what Leon is referring to is where different hardware
capabilities are checked. In Poky I ended up disabling this as at least
on ARM there were an insane number of different combinations of paths
being checked for. The patch I added to disable it was:

http://svn.o-hand.com/view/poky/trunk/meta/packages/glibc/files/no-hwcaps.patch?rev=5087&view=markup

I've not seen bad RPATH values for quite a while now.

Cheers,

Richard




  reply	other threads:[~2008-10-15 11:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15  8:22 [RFC] Enable --hash-style=both for all recent gcc4 targets Holger Freyther
2008-10-15  8:51 ` Koen Kooi
2008-10-15 21:17   ` Holger Freyther
2008-10-16  7:05     ` Koen Kooi
2008-10-16 11:52       ` Marcin Juszkiewicz
2008-10-16 14:52         ` -Wl,as-needed, was; " Koen Kooi
2008-10-15  8:54 ` Phil Blundell
2008-10-15 18:18   ` Holger Freyther
2008-10-15 18:36     ` Phil Blundell
2008-10-15  9:04 ` Holger Freyther
2008-10-15  9:19   ` Koen Kooi
2008-10-15 16:39     ` Holger Freyther
2008-10-15 18:16     ` Holger Freyther
2008-10-15 18:24       ` Koen Kooi
2008-10-15 19:53         ` Holger Freyther
2008-10-15 19:58           ` Koen Kooi
2008-10-15 22:43             ` Holger Freyther
2008-10-15 23:01               ` Henning Heinold
2008-10-16  3:17               ` Tom Talpey
2008-10-16  7:46               ` Phil Blundell
2008-10-15 10:43 ` Leon Woestenberg
2008-10-15 11:08   ` Phil Blundell
2008-10-15 11:09   ` Koen Kooi
2008-10-15 11:31     ` Richard Purdie [this message]
2008-10-15 11:58       ` Phil Blundell
2008-10-16  7:13 ` Koen Kooi

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=1224070299.5189.62.camel@ted \
    --to=rpurdie@rpsys.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    /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.