From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [arc-buildroot] [PATCH] toolchain: Bump ARC tools to arc-2018.09-rc1
Date: Mon, 19 Nov 2018 10:46:34 +0100 [thread overview]
Message-ID: <87h8gdl7r9.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <10340406050326f099c2688645f8dfca2b1f9b7f.camel@synopsys.com> (Alexey Brodkin's message of "Mon, 19 Nov 2018 08:14:35 +0000")
>>>>> "Alexey" == Alexey Brodkin <alexey.brodkin@synopsys.com> writes:
Hi,
>> > Any chance arc-2018.09 tools to be accepted in v2018.11 BR release?
>>
>> Sorry, I find it too late for that by now. I have instead applied it to
>> next, hopefully that is OK?
> Well, the hope was to get arc-2018.09 in BR v2018.11 release as
> we're going to cut the final release in coming days but...
> maybe it's good that we'll have a longer stabilization cycle
> for our tools in BR especially keeping in mind that we're
> switching from GCC 7.x to 8.x and there might come up some
> issues related more to GCC 8.x than to ARC port itself.
That was my thinking as well.
>> > In the meantime we've got RC2 cut just yesterday with a couple of more
>> > critical fixes so it might make sense to bump right to arc-2018.09-rc2
>> > instead but still it might be applied on top of this one so pls let us
>> > know what would you prefer.
>>
>> Please send a patch for next to bump it to RC2.
> We'll do that, sure.
Great, thanks!
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2018-11-19 9:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 11:32 [Buildroot] [PATCH] toolchain: Bump ARC tools to arc-2018.09-rc1 Evgeniy Didin
2018-11-15 3:51 ` [Buildroot] [arc-buildroot] " Alexey Brodkin
2018-11-18 19:50 ` Peter Korsgaard
2018-11-19 8:14 ` Alexey Brodkin
2018-11-19 9:46 ` Peter Korsgaard [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=87h8gdl7r9.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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.