From: Mike Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2014-04-19
Date: Sun, 20 Apr 2014 08:09:24 -0500 [thread overview]
Message-ID: <20140420080924.6ef37e79@core2quad.morethan.org> (raw)
In-Reply-To: <20140420104812.5bc926a9@skate>
On Sun, 20 Apr 2014 10:48:12 +0200
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> CC consumer-stream.lo
> consumer-timer.c: In function 'consumer_timer_thread':
> consumer-timer.c:518:1: internal compiler error: in gen_movsi, at
> config/arm/arm.md:5452 Please submit a full bug report,
> with preprocessed source if appropriate.
>
I seem to remember that message usually having a (missing here)
line with the bug report URL.
It is (or was) one of the build time options.
> Nobody ever answered me on how to handle gcc bugs affecting custom
> external toolchains...
>
Directions should be in doc/<version>/README.bugs of the documentation -
Which probably was not shipped and/or installed with the compiler. ;)
In general, the bug report goes to the builder of the binary,
not to gcc.gnu.org
In the case of a gcc binary built by Buildroot, that would be
Buildroot.org.
Ah, but it is already here. ;)
Duh...
For the auto-builder, I guess all you can do is exclude the
vendor/arch/gcc-version that exhibits an ICE.
Mike
next prev parent reply other threads:[~2014-04-20 13:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-20 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-04-19 Thomas Petazzoni
2014-04-20 8:48 ` [Buildroot] Analysis of build " Thomas Petazzoni
2014-04-20 13:09 ` Mike Zick [this message]
2014-04-21 17:35 ` Luca Ceresoli
2014-04-22 20:25 ` [Buildroot] php / snmp / iconv problem Thomas Petazzoni
2014-04-23 1:17 ` Gustavo Zacarias
2014-04-22 16:41 ` [Buildroot] Analysis of build results for 2014-04-19 Arnout Vandecappelle
2014-04-22 20:19 ` Thomas Petazzoni
2014-04-22 22:14 ` Arnout Vandecappelle
2014-04-23 7:22 ` Thomas Petazzoni
2014-04-23 8:51 ` Arnout Vandecappelle
2014-04-23 8:56 ` Jeremy Rosen
2014-04-23 9:02 ` Arnout Vandecappelle
2014-04-23 9:05 ` Thomas Petazzoni
2014-04-23 8:59 ` Thomas Petazzoni
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=20140420080924.6ef37e79@core2quad.morethan.org \
--to=minimod@morethan.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.