From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain: Bump ARC tools to arc-2016.09-eng008
Date: Wed, 10 Aug 2016 22:31:32 +0200 [thread overview]
Message-ID: <20160810223132.29fd6aff@free-electrons.com> (raw)
In-Reply-To: <1470857474.3428.41.camel@synopsys.com>
Hello,
On Wed, 10 Aug 2016 19:32:57 +0000, Alexey Brodkin wrote:
> > Beware that using GCC 6 is causing to cause a number of issues related
> > to GCC 6 itself and not to ARC. We already have one GCC 6 toolchain for
> > ARM, and we have a number of build failures caused by this toolchain
> > due to the use of GCC 6.
>
> That bump will for sure introduce new breakages while fixing some we already
> know about. But we had to make that bold movement at some point because that
> make us use almost upstream GCC with very few off-the-tree patches for ARC.
Sure, makes sense.
> And indeed our goal is to find and fix as many issues as we can in that new
> toolchain. So we'll continue to monitor BR autobuilder failures on daily basis.
So this means we'll get more help from you guys to fix GCC 6 related
issues ? :-)
> As usual it would be good to rebuild BR pre-built tools for ARC out of this
> commit so we have better coverage in running build jobs.
Sure. As soon as I merge the commit, I'll re-spin the pre-built ARC
toolchain(s).
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-08-10 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 17:10 [Buildroot] [PATCH] toolchain: Bump ARC tools to arc-2016.09-eng008 Vlad Zakharov
2016-08-10 19:27 ` Thomas Petazzoni
2016-08-10 19:32 ` Alexey Brodkin
2016-08-10 20:31 ` 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=20160810223132.29fd6aff@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.