All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Stefan Müller-Klieser" <s.mueller-klieser@phytec.de>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [meta-oe][dizzy][PATCH] gcc-4.9: backport from gcc trunk r212178
Date: Mon, 20 Apr 2015 15:34:20 +0100	[thread overview]
Message-ID: <1429540460.26983.11.camel@linuxfoundation.org> (raw)
In-Reply-To: <1429525121-28802-1-git-send-email-s.mueller-klieser@phytec.de>

On Mon, 2015-04-20 at 12:18 +0200, Stefan Müller-Klieser wrote:
> When compiling meta-toolchain-qt5 on cortexa8, the compiler throws an
> internal compiler error:
> 
> ...
> qttools-opensource-src-5.3.2/src/linguist/shared/po.cpp:
> In function 'bool loadPO(Translator&, QIODevice&, ConversionData&)':
> qttools-opensource-src-5.3.2/src/linguist/shared/po.cpp:717:1:
> internal compiler error: in add_stores, at var-tracking.c:6000
> ...
> 
> Tracking this down led to https://bugs.linaro.org/show_bug.cgi?id=534
> It seems the bug is well know and fixed upstream. So backporting from
> trunk seems to be the right solution. This fixes the compiler problem
> on cortexa8 and does not seem to be very invasive. The original commit
> can be found at:
> 
> git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@212178 138bc75d-0d04-0410-961f-82ee72b054a4
> 
> Signed-off-by: Stefan Müller-Klieser <s.mueller-klieser@phytec.de>
> ---
>  meta/recipes-devtools/gcc/gcc-4.9.inc              |  1 +
>  ...racking.c-backport-from-gcc-trunk-r212178.patch | 39 ++++++++++++++++++++++
>  2 files changed, 40 insertions(+)
>  create mode 100644 meta/recipes-devtools/gcc/gcc-4.9/0060-gcc-var-tracking.c-backport-from-gcc-trunk-r212178.patch

Does this need to be added to master before we can backport to dizzy?

Cheers,

Richard



  reply	other threads:[~2015-04-20 14:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 10:18 [meta-oe][dizzy][PATCH] gcc-4.9: backport from gcc trunk r212178 Stefan Müller-Klieser
2015-04-20 14:34 ` Richard Purdie [this message]
2015-04-21  8:39   ` Stefan Müller-Klieser

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=1429540460.26983.11.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=s.mueller-klieser@phytec.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.