From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-05-16
Date: Thu, 19 May 2016 15:52:01 -0300 [thread overview]
Message-ID: <573E0B51.7010000@zacarias.com.ar> (raw)
In-Reply-To: <20160517153611.2a3b4199@free-electrons.com>
On 17/05/16 10:36, Thomas Petazzoni wrote:
>> powerpc | gadgetfs-test-undefined | NOK | http://autobuild.buildroot.net/results/163fbc2ccd88282be2f5d5354b125429bfb4ff4b/
>
> Gustavo, another _restgpr_29_x issue, and this is with a Buildroot
> toolchain, so we can't blame an old CT-NG or Sourcery toolchain here :)
Hi.
No no no, the other was a _restgpr_31_x issue ;)
The recurring problem is that gcc targetting powerpc has bugs when using
-Os.
We could override per-package given this condition, or simply switch to
-O2 as default for powerpc. I'm more inclined for the second option.
I believe there are patches floating around the internets to fix this
but they were never committed upstream.
Regards.
next prev parent reply other threads:[~2016-05-19 18:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-05-16 Thomas Petazzoni
2016-05-17 13:36 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-05-17 13:53 ` Rodrigo Rebello
2016-05-17 15:13 ` gwenhael.goavec
2016-05-17 15:20 ` Thomas Petazzoni
2016-05-18 7:09 ` gwenhael.goavec
2016-05-18 19:40 ` Arnout Vandecappelle
2016-05-18 21:54 ` Thomas Petazzoni
2016-05-18 22:15 ` Arnout Vandecappelle
2016-05-17 16:27 ` Bernd Kuhls
2016-05-17 18:47 ` Bernd Kuhls
2016-05-17 18:56 ` Geoff Levand
2016-05-17 19:34 ` Thomas Petazzoni
2016-05-17 20:15 ` Geoff Levand
2016-05-17 21:03 ` Yegor Yefremov
2016-05-17 21:06 ` Yegor Yefremov
2016-05-18 19:33 ` Samuel Martin
2016-05-19 13:26 ` Gustavo Zacarias
2016-05-19 18:52 ` Gustavo Zacarias [this message]
2016-05-19 21:31 ` Arnout Vandecappelle
2016-05-20 7:35 ` Thomas Petazzoni
2016-05-25 14:44 ` Clayton Shotwell
2016-06-17 1:21 ` Ben Boeckel
2016-06-17 2:11 ` Ben Boeckel
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=573E0B51.7010000@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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