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 19:20:57 +0200 [thread overview]
Message-ID: <20170914192057.701cd74c@windsurf> (raw)
In-Reply-To: <20170914163702.2316-1-abrodkin@synopsys.com>
Hello,
Thanks for this update. One question below though.
On Thu, 14 Sep 2017 19:37:02 +0300, Alexey Brodkin wrote:
> Now speaking about arc-2017.09 series it is built on top
> of upstream GCC 7.1.1 and Binutils 2.29 so please expect
> all kinds of breakages related to GCC 7.x as we saw earlier
> with move from 4.8 to 6.x :)
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?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-09-14 17:20 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 [this message]
2017-09-14 18:07 ` Alexey Brodkin
2017-09-14 19:11 ` 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=20170914192057.701cd74c@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox