Skip to contentSkip to conversation

Internal compiler error

DISCUSSION Paul Eggleton 4 participants 4 messages Dec 22, 2011 – Dec 23, 2011

lore
Share & tools
lore
#0 lore raw

Hi Nitin/Khem/all,

We saw a failure on the Yocto Project autobuilder recently which appears to be the result of an internal compiler error [1] (note this is with the edison branch of Yocto, so it's somewhat older than what we have in master). Some searching brought up a Linaro gcc bug that looks remarkably similar [2].

Do you guys know anything about this? Do we need to bring in the fix from the bug report above?

Cheers,
Paul

[1] http://autobuilder.yoctoproject.org:8010/builders/nightly-
arm/builds/232/steps/shell_81/logs/stdio
[2] https://bugs.launchpad.net/gcc-linaro/+bug/723185

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#1 lore raw
Quoted 10 lines · Paul Eggleton

Hi Nitin/Khem/all,

We saw a failure on the Yocto Project autobuilder recently which appears to be the result of an internal compiler error [1] (note this is with the edison branch of Yocto, so it's somewhat older than what we have in master). Some searching brought up a Linaro gcc bug that looks remarkably similar [2].

Do you guys know anything about this? Do we need to bring in the fix from the bug report above?

Quoted 7 lines

Cheers,
Paul

[1] http://autobuilder.yoctoproject.org:8010/builders/nightly-
arm/builds/232/steps/shell_81/logs/stdio
[2] https://bugs.launchpad.net/gcc-linaro/+bug/723185

There also seems to be a gcc patch for qt4-x11-free in master:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=7022a8f8045bdf82b9209b8cd62fb09c4a7a24f8

Does this address it?

Sau!

#2 lore raw
In reply to Paul Eggleton
Quoted 9 lines · Paul Eggleton

Hi Nitin/Khem/all,

We saw a failure on the Yocto Project autobuilder recently which appears to be the result of an internal compiler error [1] (note this is with the edison branch of Yocto, so it's somewhat older than what we have in master). Some searching brought up a Linaro gcc bug that looks remarkably similar [2].

Do you guys know anything about this? Do we need to bring in the fix from the bug report above?

I've seen few ICEs with libav, libvpx and mplayer2 in meta-oe, disabling tree-vectorize worked as work around
http://git.openembedded.org/meta-openembedded/commit/?id=11fbc9fb4efaa59aca85ba352f6ebc3412eaedd0
http://git.openembedded.org/meta-openembedded/commit/?id=c59fda28b29afcdcb245651cabbe08a76856d8ca

But I'm using more gcc-4.6 patches from meta-oe.

Cheers,

Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#3 lore raw
In reply to Paul Eggleton

Khem had fixed this in the oecore, I just sent a pull request for that commit for edison branch.

Thanks
Nitin

Quoted 33 lines

-----Original Message-----
From: Paul Eggleton [mailto:[email protected]]
Sent: Thursday, December 22, 2011 10:33 AM
To: [email protected]
Cc: Kamble, Nitin A; Khem Raj
Subject: Internal compiler error

Hi Nitin/Khem/all,

We saw a failure on the Yocto Project autobuilder recently which appears to be
the result of an internal compiler error [1] (note this is with the edison
branch of Yocto, so it's somewhat older than what we have in master). Some
searching brought up a Linaro gcc bug that looks remarkably similar [2].

Do you guys know anything about this? Do we need to bring in the fix from the
bug report above?

Cheers,
Paul

[1] http://autobuilder.yoctoproject.org:8010/builders/nightly-
arm/builds/232/steps/shell_81/logs/stdio
[2] https://bugs.launchpad.net/gcc-linaro/+bug/723185

--

Paul Eggleton
Intel Open Source Technology Centre