From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] Prune global compilation flags
Date: Wed, 23 Mar 2011 17:10:42 +0000 [thread overview]
Message-ID: <1300900242.3018.33.camel@rex> (raw)
In-Reply-To: <cover.1300730825.git.raj.khem@gmail.com>
On Mon, 2011-03-21 at 11:10 -0700, Khem Raj wrote:
> This patch series is for removing the unneeded flags in SELECTED_OPTIMIZATIONS
> that gets passed to every recipe build by default. I have also introduced flags
> to remove duplicate debug information which will reduce the debug info sections
>
> Tested by building and booting console-image/angstrom on ppc,arm,mips,x86-64,x86
> qemu machines.
>
> Please apply
>
> Pull URL: git://git.openembedded.org/openembedded-core-contrib
> Branch: kraj/global-opts
> Browse: http://git.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/global-opts
>
> Thanks,
> Khem Raj <raj.khem@gmail.com>
> ---
>
>
> Khem Raj (3):
> bitbake.conf: Prune global OPTIMIZATION flags
> machine/include/tune-atom.inc: Remove FULL_OPTIMIZATION_pn-gtk+
> gcc-runtime_4.5.1.bb: Fix ICE in gcc-runtime with
> -feliminate-dwarf2-dups
Merged into master, thanks.
Richard
prev parent reply other threads:[~2011-03-23 17:56 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
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 ` Richard Purdie [this message]
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=1300900242.3018.33.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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 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.