From: Khem Raj <raj.khem@gmail.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
Zhenhua Luo <zhenhua.luo@freescale.com>,
'Patches and discussions about the oe-core layer'
<openembedded-core@lists.openembedded.org>,
Schmitt Richard-B43082 <B43082@freescale.com>,
richard.schmitt@freescale.com
Subject: Re: GCC 4.8 Issues with fsl-ppc and fsl-arm (e5000)
Date: Tue, 25 Jun 2013 19:44:53 -0700 [thread overview]
Message-ID: <2409553.DWj15DeEDt@leo> (raw)
In-Reply-To: <51C9CE42.8020207@linux.intel.com>
On Tuesday, June 25, 2013 10:07:14 AM Saul Wold wrote:
> Guys,
>
> There is a continuing failure on the auto-builder with the 4.8 version
> of GCC for the fsl-ppc and fsl-arm BSPs. This is currently holding
> oe-core back from updating GCC to 4.8, which we want to do soon so
that
> we have get any other issues worked out that might come up.
>
> These seem to be ICE issues can get bee seen in the following log files:
>
> http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-arm/builds/148
> /steps/Building%20Images/logs/stdio
>
> http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-ppc/builds/149
> /steps/Building%20Images/logs/stdio
>
ppc issue is singled out and reported as regression in gcc
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57717
> Has anyone investigated these?
>
> One possibility discussed during the tech call was to set the tune for
> these BSPs to use GCC 4.7, but this is not preferred as it just defers
> and hides the issue.
>
> Thanks
prev parent reply other threads:[~2013-06-26 2:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 17:07 GCC 4.8 Issues with fsl-ppc and fsl-arm (e5000) Saul Wold
2013-06-25 17:42 ` Khem Raj
2013-06-25 17:46 ` Otavio Salvador
2013-06-25 18:00 ` Khem Raj
2013-06-25 18:03 ` Otavio Salvador
2013-06-25 18:09 ` Khem Raj
2013-06-26 17:14 ` Saul Wold
2013-07-02 14:28 ` Saul Wold
2013-07-02 14:47 ` Otavio Salvador
2013-07-02 14:54 ` Khem Raj
2013-07-02 15:01 ` Otavio Salvador
2013-07-02 15:24 ` Saul Wold
2013-06-26 2:44 ` Khem Raj [this message]
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=2409553.DWj15DeEDt@leo \
--to=raj.khem@gmail.com \
--cc=B43082@freescale.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=richard.schmitt@freescale.com \
--cc=sgw@linux.intel.com \
--cc=zhenhua.luo@freescale.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