From: Phil Blundell <pb@pbcl.net>
To: raj.khem@gmail.com,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] tcmode-default: disable ARMv7 Optimization for qt4-x11-free
Date: Wed, 01 Jun 2011 11:46:34 +0100 [thread overview]
Message-ID: <1306925194.2529.38.camel@phil-desktop> (raw)
In-Reply-To: <4DE5DA86.7040808@gmail.com>
On Tue, 2011-05-31 at 23:21 -0700, Khem Raj wrote:
> On 05/31/2011 11:10 PM, Martin Jansa wrote:
> > On Tue, May 31, 2011 at 10:57:00PM -0700, Khem Raj wrote:
> >> On 05/31/2011 10:26 PM, Saul Wold wrote:
> >>> | ../../include/QtCore/../../src/corelib/arch/qatomic_arm.h:361:35:
> >>> error: output number 1 not directly addressable
> >>
> >> this is a coding error you can fix the source code I guess instead of
> >> pessimising the whole package
> >
> > FWIW: I haven't seen it in my armv7-a builds (nokia900), but I'm using
> > gcc-4.6 from meta-oe.
>
> this is because gcc 4.6 in meta-oe has fix for it its this patch here
> http://gcc.gnu.org/ml/gcc-patches/2011-03/msg01477.html
I'm a bit confused by this. In the first quote above you said that this
was a coding error and ought to be fixed in qt, but now you seem to be
saying that it's a compiler bug and should be fixed in gcc. If it's the
latter, can we get that patch applied to the oe-core version of gcc?
Either way, I agree, working around this by just frobbing the
architecture options seems like a bad idea.
p.
next prev parent reply other threads:[~2011-06-01 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 5:26 [PATCH] tcmode-default: disable ARMv7 Optimization for qt4-x11-free Saul Wold
2011-06-01 5:57 ` Khem Raj
2011-06-01 6:10 ` Martin Jansa
2011-06-01 6:14 ` Khem Raj
2011-06-01 6:21 ` Khem Raj
2011-06-01 10:46 ` Phil Blundell [this message]
2011-06-01 17:50 ` Saul Wold
2011-06-01 18:31 ` 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=1306925194.2529.38.camel@phil-desktop \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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