From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-08-10
Date: Wed, 12 Aug 2015 10:18:06 +0200 [thread overview]
Message-ID: <20150812101806.72f55a1a@free-electrons.com> (raw)
In-Reply-To: <20150812043418.GJ8475@waldemar-brodkorb.de>
Dear Waldemar Brodkorb,
On Wed, 12 Aug 2015 06:34:18 +0200, Waldemar Brodkorb wrote:
> > sh4 | mplayer-1.1.1 | NOK | http://autobuild.buildroot.net/results/f373f0b20cf127b3e54970ed50d45fc5c38991a7/
>
> There is a patch for gcc in the bugtracker for this.
> Should we add it to gcc 4.9.3?
If you look at the GCC PR for this bug, I restarted the discussion a
few days ago. My worry is that the patch proposed in the bug tracker
has not been merged in any gcc branch for now, as far as I know. So it
has never been tested by the gcc regression tests and so on.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-08-12 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-08-10 Thomas Petazzoni
2015-08-12 4:34 ` Waldemar Brodkorb
2015-08-12 8:18 ` Thomas Petazzoni [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=20150812101806.72f55a1a@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