From: Darren Hart <dvhart@linux.intel.com>
To: Ilya Yanok <yanok@emcraft.com>
Cc: poky@pokylinux.org
Subject: Re: [PATCH 3/3] u-boot: compile with -O2 on PowerPC
Date: Wed, 09 Feb 2011 15:34:54 -0800 [thread overview]
Message-ID: <4D53249E.9030606@linux.intel.com> (raw)
In-Reply-To: <4D53216D.4010908@emcraft.com>
On 02/09/2011 03:21 PM, Ilya Yanok wrote:
> Hi Darren,
>
> 09.02.2011 20:42, Darren Hart wrote:
>> This is already disabled in u-boot.inc with the following line:
>>
>> # GCC 4.5.1 builds unusable binaries using -Os, remove it from OPTFLAGS
>> EXTRA_OEMAKE = "CROSS_COMPILE=${TARGET_PREFIX} OPTFLAGS=''"
>
> Yes, sorry, I've useed not up-to-date version of metadata and missed
> this fix. But it has to be '-O2' still.
Understood, -O2 is in master now for all arches.
>
>> Resetting OPTFLAGS to '' removes the -Os from the variable in the
>> Makefile. This isn't just a PowerPC problem, it also manifested on ARM,
>> I believe it is a GCC 4.5.1 issue.
>
> Well, the difference here is that on PowerPC we have -Os option disabled
> completely. Wolfgang tried to summarize know gcc bugs and seems like -Os
> bugs on ARM and PowerPC have different nature (it looks like bugs on ARM
> are already fixed while on the ones PowerPC are not).
> Then I think it's a bad idea to remove -Os everywhere: U-Boot really
> wants to be built with -Os optimization so we might want to change
> optimization level to -O2 only for targets where it's absolutely
> required. Actually I was able to build and successfully run U-Boot on
> beagleboard with -Os so it doesn't look like it's completely broken on ARM.
Interesting - is this using the current recipe in poky? It was building
for the beagleboard that I hit the bug which caused me to clear -Os from
the EXTRA_OEMAKE arguments.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-02-09 23:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 20:26 [PATCH 1/3] linux: add LIC_FILES_CHKSUM Ilya Yanok
2011-02-08 20:26 ` [PATCH 2/3] u-boot: " Ilya Yanok
2011-02-09 17:38 ` Darren Hart
2011-02-09 17:42 ` Gary Thomas
2011-02-09 23:02 ` Ilya Yanok
2011-02-09 22:58 ` Ilya Yanok
2011-02-09 23:04 ` Darren Hart
2011-02-09 23:25 ` Ilya Yanok
2011-02-09 23:38 ` Darren Hart
2011-02-09 23:43 ` Ilya Yanok
2011-02-10 0:06 ` Darren Hart
2011-02-10 0:42 ` Richard Purdie
2011-02-08 20:26 ` [PATCH 3/3] u-boot: compile with -O2 on PowerPC Ilya Yanok
2011-02-09 17:42 ` Darren Hart
2011-02-09 18:05 ` Adrian Alonso
2011-02-09 18:40 ` Darren Hart
2011-02-09 18:15 ` Koen Kooi
2011-02-09 18:27 ` Wolfgang Denk
2011-02-09 23:21 ` Ilya Yanok
2011-02-09 23:34 ` Darren Hart [this message]
2011-02-09 23:48 ` Ilya Yanok
2011-02-09 11:26 ` [PATCH 1/3] linux: add LIC_FILES_CHKSUM Richard Purdie
2011-02-09 17:33 ` Darren Hart
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=4D53249E.9030606@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=poky@pokylinux.org \
--cc=yanok@emcraft.com \
/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