Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] bitbake.conf: Prune global OPTIMIZATION flags
Date: Tue, 29 Mar 2011 17:53:24 -0600	[thread overview]
Message-ID: <4D9270F4.3080004@mlbassoc.com> (raw)
In-Reply-To: <20110329150018.GB4529@sakrah.homelinux.org>

On 03/29/2011 09:00 AM, Khem Raj wrote:
> On (29/03/11 14:34), Richard Purdie wrote:
>> On Mon, 2011-03-21 at 11:11 -0700, Khem Raj wrote:
>>> -fexpensive-optimizations is enabled by default at -O2
>>>
>>> -fomit-frame-pointer is enabled at -O2 selectively by gcc depending upon
>>>    architecture if debug info is not hurt
>>>
>>> -frename-registers - This might have some performance advantage on top
>>>   of O2 on architectures which have more registers and registers are left
>>>   after scheduling but it affects debuggability quite a bit so as a i
>>>   tradeoff we do not use it.
>>>
>>> -feliminate-dwarf2-dups - We use this option to reduce the size of debug
>>>   information by removing duplicates this is only valid for dwarf2+ and we
>>>   use dwarf2 by default
>>
>> I've disabled this flag for now as it was causing too many failures
>> across the board (various apps, prelinker). We can add it back when this
>> has been tested more extensively and its been confirmed to work with the
>> prelinker.
>
> It would have been better to disable one by one we would be able to
> utilize current testing. Most probaly the prelink issue is due to -feliminate-dwarf2-dups did you try to remove that out ?

This change, in particular adding -feliminate-dwarf2-dups, breaks my
build of chromium(*) (in strange ways, it ends up building .a libraries
which the linker can't parse).  Everything else I've tried to build
seems OK though.  For now, I've just dropped this option in my DISTRO.conf

(*) It took quite some time to isolate this as the problem as it is a royal
pain to test BTW as it takes more than an hour to build this one package on my
hefty build server!

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------



  reply	other threads:[~2011-03-29 23:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21 18:10 [PATCH 0/3] Prune global compilation flags Khem Raj
2011-03-21 18:11 ` [PATCH 1/3] bitbake.conf: Prune global OPTIMIZATION flags Khem Raj
2011-03-29 13:34   ` Richard Purdie
2011-03-29 15:00     ` Khem Raj
2011-03-29 23:53       ` Gary Thomas [this message]
2011-03-30  1:31         ` Khem Raj
2011-03-30 11:11           ` Gary Thomas
2011-03-30  1:29       ` Khem Raj
2011-03-21 18:11 ` [PATCH 2/3] machine/include/tune-atom.inc: Remove FULL_OPTIMIZATION_pn-gtk+ Khem Raj
2011-03-21 18:11 ` [PATCH 3/3] gcc-runtime_4.5.1.bb: Fix ICE in gcc-runtime with -feliminate-dwarf2-dups Khem Raj
2011-03-23 17:10 ` [PATCH 0/3] Prune global compilation flags Richard Purdie

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=4D9270F4.3080004@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=openembedded-core@lists.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