From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] grub: add -fno-reorder-functions into STAGE2_COMPILE
Date: Wed, 29 Jun 2011 15:04:13 +0100 [thread overview]
Message-ID: <1309356253.20015.390.camel@rex> (raw)
In-Reply-To: <1309353632.2551.32.camel@phil-desktop>
On Wed, 2011-06-29 at 14:20 +0100, Phil Blundell wrote:
> On Wed, 2011-06-29 at 21:09 +0800, Dexuan Cui wrote:
> > +This turned out to be a gcc's bug. See
> > +https://bugs.gentoo.org/show_bug.cgi?id=360513
> > +http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39333
> > +
> > +Upstream gcc seems uninterested in the bug, so at present we can disable the
> > +option as a workaround. Thanks Ryan Hill for the investigation and the
> > +workaround patch.
>
> I'm not sure it's fair to say that upstream gcc is uninterested. It
> doesn't appear that anybody has been willing or able to produce a
> testcase which will allow the gcc people to debug the problem.
Agreed, it would be good if the gcc people could get a testcase to fix
the problem. In the meantime I will take the workaround though.
Cheers,
RIchard
next prev parent reply other threads:[~2011-06-29 14:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 13:09 [PATCH 0/3] fix to bug #1099, updates to Upstream-Status and distro_tracking_fields.inc Dexuan Cui
2011-06-29 13:09 ` [PATCH 1/3] grub: add -fno-reorder-functions into STAGE2_COMPILE Dexuan Cui
2011-06-29 13:17 ` Cui, Dexuan
2011-06-29 13:20 ` Phil Blundell
2011-06-29 14:04 ` Richard Purdie [this message]
2011-06-29 13:09 ` [PATCH 2/3] lttng-ust: change the patch's Upstream-Status to Accepted Dexuan Cui
2011-06-29 13:09 ` [PATCH 3/3] distro_tracking_fields.inc: update RECIPE_MANUAL_CHECK_DATE for screen and tcf-agent Dexuan Cui
2011-06-29 14:04 ` [PATCH 0/3] fix to bug #1099, updates to Upstream-Status and distro_tracking_fields.inc Richard Purdie
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=1309356253.20015.390.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