From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gcc 4.8.3: add patch for PR60155
Date: Wed, 2 Jul 2014 16:35:22 +0200 [thread overview]
Message-ID: <20140702163522.3c0f7794@free-electrons.com> (raw)
In-Reply-To: <53B415CE.5090109@zacarias.com.ar>
Dear Gustavo Zacarias,
On Wed, 02 Jul 2014 11:23:10 -0300, Gustavo Zacarias wrote:
> Yes, gcc 4.9.0 doesn't need it.
Cool.
> IMHO it should have been in 4.8.3 since the bug was resolved in April 4
> and gcc was released on May 22, but i don't know their release policies
> so who knows.
OK.
> Regarding CT-NG that's up to Yann, and yes an exception is in order,
> though if you look at other failures it does affect internal toolchains
> as well so the fix alone will make errors go down albeit not all of them.
Yes, sure. I'll work on the autobuilder exception.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-02 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 13:43 [Buildroot] [PATCH] gcc 4.8.3: add patch for PR60155 Gustavo Zacarias
2014-07-02 14:18 ` Thomas Petazzoni
2014-07-02 14:23 ` Gustavo Zacarias
2014-07-02 14:35 ` Thomas Petazzoni [this message]
2014-07-02 15:14 ` Peter Korsgaard
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=20140702163522.3c0f7794@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 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.