From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: why do we poison -Os?
Date: Wed, 24 Aug 2011 09:14:15 -0700 [thread overview]
Message-ID: <4E552357.3070609@gmail.com> (raw)
In-Reply-To: <1314183168.19905.6.camel@phil-desktop>
On 8/24/2011 3:52 AM, Phil Blundell wrote:
> 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.
>
thats correct. this options is only for making gcc runtime to be built
with Os. It does not make gcc to use -Os by default. The problem for ppc
however is that if you built with Os then gcc depends upon functions
from libgcc.a which needs libgcc.so to be a linker script stub rather
than a symlink as it used to be but this has been fixed
> p.
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
prev parent reply other threads:[~2011-08-24 16:19 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
2011-08-24 16:14 ` Khem Raj [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=4E552357.3070609@gmail.com \
--to=raj.khem@gmail.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