From: Mike Looijmans <mike.looijmans@topic.nl>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Default value for FULL_OPTIMIZATION
Date: Tue, 2 Feb 2016 15:26:33 +0100 [thread overview]
Message-ID: <56B0BC99.5050405@topic.nl> (raw)
In-Reply-To: <56B0AE88.3090103@siemens.com>
You'd have to check the GCC documentation to be sure, but I suspect that all
of "-fexpensive-optimizations -fomit-frame-pointer -frename-registers" are
already in effect at -O2 optimization level, so they're redundant.
On 02-02-16 14:26, Pascal Bach wrote:
> Hi everybody
>
> I noticed an inconsistency in oe-core regarding the variable: FULL_OPTIMIZATION
>
> In bitbake.conf the variable is defined as follows:
>
> FULL_OPTIMIZATION = "-O2 -pipe ${DEBUG_FLAGS}"
>
> But if I look into the documentation.conf it tells me the following:
>
> FULL_OPTIMIZATION[doc]= "The options to pass in TARGET_CFLAGS and CFLAGS when compiling an optimized system. This variable defaults to '-fexpensive-optimizations -fomit-frame-pointer -frename-registers -O2'."
>
> I'm not sure if the documentation is wrong or if the default set in bitbake.conf is incorrect.
> Maybe somebody can shed some light on this.
>
> Regards
> Pascal
>
Kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
Visit us at: Embedded World 2016 Germany, Hall 1, stand number 220.
Click here to schedule an appointment with us at Embedded World, free ticket included
http://topicembeddedproducts.com/schedule-an-appointment/
next prev parent reply other threads:[~2016-02-02 15:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 13:26 Default value for FULL_OPTIMIZATION Pascal Bach
2016-02-02 14:26 ` Mike Looijmans [this message]
2016-02-02 16:23 ` Pascal Bach
2016-02-02 14:47 ` Richard Purdie
2016-02-02 20:52 ` Phil Blundell
2016-02-03 6:17 ` Khem Raj
2016-02-03 20:48 ` Phil Blundell
2016-02-03 20:51 ` Khem Raj
2016-02-03 20:54 ` Burton, Ross
2016-02-03 20:57 ` Phil Blundell
2016-02-03 20:59 ` Khem Raj
2016-02-03 21:08 ` Phil Blundell
2016-02-03 22:37 ` Khem Raj
2016-02-04 12:56 ` Mike Looijmans
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=56B0BC99.5050405@topic.nl \
--to=mike.looijmans@topic.nl \
--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