Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] Enable --hash-style=both for all recent gcc4 targets
Date: Wed, 15 Oct 2008 10:51:33 +0200	[thread overview]
Message-ID: <gd4aul$sb5$1@ger.gmane.org> (raw)
In-Reply-To: <200810151022.38477.zecke@selfish.org>

On 15-10-2008 10:22, Holger Freyther 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%

Also check the as-needed stuff from Poky:

ASNEEDED = "-Wl,--as-needed"
ASNEEDED_pn-console-tools = ""
ASNEEDED_pn-distcc = ""
ASNEEDED_pn-openobex = ""
ASNEEDED_pn-icu = ""
ASNEEDED_pn-xserver-kdrive-xomap = ""
ASNEEDED_pn-minimo = ""
ASNEEDED_pn-pciutils = ""
ASNEEDED_pn-puzzles = ""
ASNEEDED_pn-dialer = ""

TARGET_LDFLAGS += "${ASNEEDED}"

That should also reduce library load time *and* eliminate spurious deps.

> (google is your
> friend). This is an option for binutils and was introduced with binutils
> 2.17. Now there are two ways to achieve this:
>
> Change TARGET_LDFLAGS in e.g. the distro config (as this knows if binutils has
> this option available) or to change the "specs" of gcc to enable this by
> default. There is a patch from debian for gcc4.3 but it is leaving
> arm/armeabi out. What do you guys prefer?

It seems that the TARGET_LDFLAGS in distro would be the best option forward.

> I'm pretty sure that we will want to use the GNU hash style at Openmoko and
> this is creating an interesting problem in regard to a full system upgrade
> (which is supposed to work). Again there are two ways. Use force and bump PE
> on each package but we should avoid this.

PE is only there to fix versioning screwups (be it upstream or OE)

> I propose to rename PR to FILE_PR
> and change PR  to "${FILE_PR}${DISTRO_PR}" so everytime a distro is changing
> something that effects every package we can bump (e.g. Setting DISTRO_PR
> to .1 for Openmoko).

That sounds like a good idea, it would make changing compiler versions a 
lot safer.

regards,

Koen




  reply	other threads:[~2008-10-15  8:56 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 [this message]
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
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='gd4aul$sb5$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox