From: Phil Blundell <pb@reciva.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: [RFC] Enable --hash-style=both for all recent gcc4 targets
Date: Wed, 15 Oct 2008 12:58:59 +0100 [thread overview]
Message-ID: <1224071940.30790.45.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <1224070299.5189.62.camel@ted>
On Wed, 2008-10-15 at 12:31 +0100, Richard Purdie wrote:
> 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:
Right, the default set of hwcaps is probably a bit more inclusive than
most folks want. I don't think this issue is specific to ARM though
it's possible that arm does have it worse than some other
architectures.
As with so many things it is basically a DISTRO decision which hwcaps to
include in the list for ld.so. I suppose the ideal thing would be to
have a variable LD_SO_CONSIDER_HWCAPS or some such, which could be set
by DISTRO.conf to specify which ones should be included. For the
majority of single-target-platform DISTROs the answer is obviously going
to be none.
Another similar issue for embedded-type DISTROs to consider is
minimising the length of the linker search path by, for example,
eliminating /usr/lib in favour of putting everything in /lib. (The same
goes for /usr/bin and /bin, of course.) And of course, not putting
anything in /etc/ld.so.conf unless it's necessary: my openmoko install
seems to have /usr/X11R6/lib and /usr/local/lib listed in that file even
though neither directory actually exists in the filesystem, which will
be causing another 2*N useless path lookups for every library.
Plus of course, PACKAGE_SNAP_LIB_SYMLINKS will eliminate another source
of indirection and hence another dentry name lookup.
p.
next prev parent reply other threads:[~2008-10-15 12:04 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
2008-10-15 11:58 ` Phil Blundell [this message]
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=1224071940.30790.45.camel@mill.internal.reciva.com \
--to=pb@reciva.com \
--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.