Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain: Bump ARC tools to arc-2016.09-eng008
Date: Wed, 10 Aug 2016 19:32:57 +0000	[thread overview]
Message-ID: <1470857474.3428.41.camel@synopsys.com> (raw)
In-Reply-To: <20160810212736.6a814ad9@free-electrons.com>

Hi Thomas,

On Wed, 2016-08-10 at 21:27 +0200, Thomas Petazzoni wrote:
> Hello,
> 
> Thanks for this new update!
> 
> On Wed, 10 Aug 2016 20:10:40 +0300, Vlad Zakharov wrote:
> > 
> > As described at:
> > 4520524ba055706236db9f00dd79f1b2e2e87fde
> > this commit continues a series of updates of ARC tools.
> > This time we're updating tools to arc-2016.09-eng008.
> > 
> > Main updates were made for gcc. It was switched to GCC 6 and to
> > OSABI v4.
> 
> 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.

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.

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.

-Alexey

  reply	other threads:[~2016-08-10 19:32 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 [this message]
2016-08-10 20:31     ` 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=1470857474.3428.41.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.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