From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: why do we poison -Os?
Date: Wed, 24 Aug 2011 11:52:47 +0100 [thread overview]
Message-ID: <1314183168.19905.6.camel@phil-desktop> (raw)
In-Reply-To: <D5AB6E638E5A3E4B8F4406B113A5A19A12D724C949@shsmsx501.ccr.corp.intel.com>
On Wed, 2011-08-24 at 09:47 +0800, Xu, Dongxiao wrote:
> My understanding is that, if GCC is not configured with the ability of code space optimization, target recipes will not have code size benefit even if adding "-Os" option.
No, that's incorrect. All that --enable-target-optspace does is change
the definition of CFLAGS_FOR_TARGET, which causes the GCC support
libraries (i.e. libgcc, libstdc++, etc) to be built with -Os rather than
-O2. It has no effect on the functionality of the compiler itself.
p.
next prev parent reply other threads:[~2011-08-24 10:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 0:52 why do we poison -Os? Kumar Gala
2011-08-24 1:16 ` Xu, Dongxiao
2011-08-24 1:31 ` Kumar Gala
2011-08-24 1:32 ` Kumar Gala
2011-08-24 1:45 ` Richard Purdie
2011-08-24 4:02 ` Kumar Gala
2011-08-24 1:47 ` Xu, Dongxiao
2011-08-24 4:06 ` Kumar Gala
2011-08-24 10:52 ` Phil Blundell [this message]
2011-08-24 16:14 ` Khem Raj
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=1314183168.19905.6.camel@phil-desktop \
--to=philb@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox