From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain: Bump ARC tools to arc-2017.09-eng008
Date: Thu, 14 Sep 2017 21:11:20 +0200 [thread overview]
Message-ID: <20170914211120.6817efa7@windsurf> (raw)
In-Reply-To: <1505412449.3684.5.camel@synopsys.com>
Hello,
On Thu, 14 Sep 2017 18:07:30 +0000, Alexey Brodkin wrote:
> > If those new versions are now based on upstream gcc 7.x and binutils
> > 2.29, why do we still use the Synopsys specific versions? Do you still
> > have a large stack of patches on top of the upstream versions?
>
> Well not that many now but indeed something not yet hit
> upstream release or might have been released a bit late for the last relese
> or even after.
>
> Still thw next patch of mine will allow selection of upstream GCC and
> Binutils for ARC.
>
> So for now this GitHub-hosted stuff is more for safety. I.e. once we see
> autobuilder is quite happy with upstream components we'll consider removal of
> arc-XXX stuff completely. This won't happen in this release cycle nor
> in the next I guess but in the course of the year I hope we'll be able to do it
> [if all goes well].
Fair enough. As long as it is in your plans to switch to use the
upstream gcc/binutils at some point in the not too distant future, I'm
fine with keeping an ARC-specific gcc version and binutils version.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-09-14 19:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 16:37 [Buildroot] [PATCH] toolchain: Bump ARC tools to arc-2017.09-eng008 Alexey Brodkin
2017-09-14 17:20 ` Thomas Petazzoni
2017-09-14 18:07 ` Alexey Brodkin
2017-09-14 19:11 ` 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=20170914211120.6817efa7@windsurf \
--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.