Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-08-18
Date: Sat, 20 Aug 2016 12:27:59 +0200	[thread overview]
Message-ID: <20160820122759.68b6e8b7@free-electrons.com> (raw)
In-Reply-To: <20160819222238.GZ22524@waldemar-brodkorb.de>

Hello,

On Sat, 20 Aug 2016 00:22:38 +0200, Waldemar Brodkorb wrote:

> > eelf32bfin.c:1790:1: error: unable to find a register to spill in class 'CCREGS'
> > 
> > Waldemar, this is a gcc bug.  
> 
> Seems simlar to the ffmpeg issue. Some kind of optimization is
> broken for Blackfin in gcc 6.1.x.

OK. Can you cook a patch for this one as well?

Ideally, we should fix the gcc problem, but I clearly don't have enough
knowledge about gcc internals to fix this one I believe. Though it
would be a good opportunity to learn about such internals.

> > >         m68k |                   libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/1014a22cfdd3b18f349dde33f14acca4131dbd5b/  
> > 
> > Waldemar, no support of libffi for 5208. What's the plan for that?  
> 
> I have a local patch for this. I will sent it out later.

Applied, thanks.

> > >         m68k |                      php-7.0.9 | NOK | http://autobuild.buildroot.net/results/20b1586757450d6aad8583ad7a787a7ca11acef1/  
> > 
> > Waldemar, this is still occuring :)  
> 
> I am pretty sure it will disappear, when we switched to simple FLAT
> as it just seems to be a newer error message for the same problem we
> are seeing with -msep-data.

OK. I guess you'll send a patch series about this soonish?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-08-20 10:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-08-18 Thomas Petazzoni
2016-08-19 22:07 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-08-19 22:19   ` Yann E. MORIN
2016-08-19 22:22   ` Waldemar Brodkorb
2016-08-20 10:27     ` Thomas Petazzoni [this message]
2016-08-19 22:29   ` Yann E. MORIN
2016-08-24 16:51     ` Thomas Petazzoni
2016-08-24 20:40       ` [Buildroot] Remaining kmsxx build issue Thomas Petazzoni
2016-08-26 19:30         ` Arnout Vandecappelle
2016-08-26 19:42           ` Thomas Petazzoni
2016-08-20  9:17   ` [Buildroot] Analysis of build results for 2016-08-18 Rahul Bedarkar
2016-08-20  9:22     ` Thomas Petazzoni
2016-08-20 10:11       ` Rahul Bedarkar
2016-08-20 13:52   ` Gustavo Zacarias
2016-08-20 13:55     ` [Buildroot] odroid-mali issue Thomas Petazzoni
2016-08-21  6:42   ` [Buildroot] Analysis of build results for 2016-08-18 Baruch Siach

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=20160820122759.68b6e8b7@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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