[OE-core] [meta-oe][dizzy][PATCH] gcc-4.9: backport from gcc trunk r212178

[Stefan Müller-Klieser]

Hi Richard,

Richard Purdie <richard.purdie at linuxfoundation.org> wrote on 04/20/2015 
04:34:20 PM:

> Von: Richard Purdie <richard.purdie at linuxfoundation.org>
> An: Stefan Müller-Klieser <s.mueller-klieser at phytec.de>
> Kopie: openembedded-core at lists.openembedded.org
> Datum: 04/20/2015 04:34 PM
> Betreff: Re: [OE-core] [meta-oe][dizzy][PATCH] gcc-4.9: backport 
> from gcc trunk r212178
> 
> 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 at 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?
I thought Yocto will resolve those dependencies automatically ;-) No for 
real, I don't use master at the moment. But I managed to quickly test the 
patch on master with qt5.3.2 on the beagleboneblack. The bug still exists 
and is fixed with the patch. I will send a new one...

Regards, Stefan

> 
> Cheers,
> 
> Richard
>