From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [bugfix 1/1] mesa-xlib: workaround gcc 4.6.0 ICE
Date: Fri, 27 May 2011 00:33:42 +0100 [thread overview]
Message-ID: <1306452822.27470.220.camel@rex> (raw)
In-Reply-To: <03152273cac84eef23738c5f26c45b082194284f.1306442263.git.nitin.a.kamble@intel.com>
On Thu, 2011-05-26 at 13:41 -0700, nitin.a.kamble@intel.com wrote:
> ---
> meta/recipes-graphics/mesa/mesa-xlib_7.10.2.bb | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/meta/recipes-graphics/mesa/mesa-xlib_7.10.2.bb b/meta/recipes-graphics/mesa/mesa-xlib_7.10.2.bb
> index b77df2c..051bd72 100644
> --- a/meta/recipes-graphics/mesa/mesa-xlib_7.10.2.bb
> +++ b/meta/recipes-graphics/mesa/mesa-xlib_7.10.2.bb
> @@ -17,3 +17,6 @@ PE = "1"
> PR = "r0"
>
> EXTRA_OECONF += "--with-driver=xlib"
> +
> +# nullify -O2
> +CFLAGS_append += " -O"
I talked about this on IRC but simply put, no way.
The problem is:
a) Arm specific
b) determined now to be armv7 specific
c) gcc version specific
and the fix should reflect this.
So ideally when we select gcc 4.6 in tcmode-default.inc we should add
something there which adds a work around for mesa-xlib.
I've suggested something like:
TARGET_CC_ARCH_arm_pn-mesa-xlib := "${@'${TARGET_CC_ARCH}'.replace('armv7','armv5')}"
which whilst ugly, should do what we need it to.
Cheers,
Richard
next prev parent reply other threads:[~2011-05-26 23:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 20:41 [bugfix 0/1] workaround for gcc 4.6.0 issue on beagleboard nitin.a.kamble
2011-05-26 20:41 ` [bugfix 1/1] mesa-xlib: workaround gcc 4.6.0 ICE nitin.a.kamble
2011-05-26 21:16 ` Darren Hart
2011-05-26 21:22 ` Kamble, Nitin A
2011-05-26 23:33 ` Richard Purdie [this message]
2011-05-27 0:37 ` Khem Raj
2011-05-27 1:03 ` Kamble, Nitin A
2011-05-27 7:14 ` Koen Kooi
2011-05-27 8:54 ` Richard Purdie
2011-05-27 9:30 ` Phil Blundell
2011-05-27 17:11 ` Richard Purdie
2011-05-27 15:06 ` Phil Blundell
2011-05-27 17:13 ` Kamble, Nitin A
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=1306452822.27470.220.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox