From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-05-16
Date: Tue, 17 May 2016 17:20:40 +0200 [thread overview]
Message-ID: <20160517172040.630eda58@free-electrons.com> (raw)
In-Reply-To: <20160517171350.247927aa@x230.trabucayre.com>
Hello,
On Tue, 17 May 2016 17:13:50 +0200, gwenhael.goavec wrote:
> > > x86_64 | gnuradio-3.7.9.1 | NOK |
> > > http://autobuild.buildroot.net/results/714019031fb8c8f70c1838aa18e4ec1e4abf165e/
> >
> > internal compiler error: Segmentation fault
> >
> > Gwenhael, can you look into this problem?
> >
> I'm looking into this problem :
> - Fails with a binary toolchain (gcc-4.7.2);
> - Works with a toolchain generated by buildroot (same options but
> 4.8.5 and 4.9.3).
> I need to see if it's due to the gcc version or something else.
Potentially seems like a bug in gcc 4.7.x, which has been fixed in gcc
4.8.x, no? We still support gcc 4.7.x in the internal toolchain
backend, if you enable "deprecated options". This way you can check if
a Buildroot toolchain with gcc 4.7 exhibits the same problem.
Note that this kind of issue is often sensitive to optimization flags:
i.e it might fail at -O3 but succeed at -Os.
If we conclude that 4.7 is broken, and >= 4.8 is working, then adding a
dependency on BR2_TOOLCHAIN_GCC_AT_LEAST_4_8 is good enough for me.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-17 15:20 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 [this message]
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
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=20160517172040.630eda58@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