Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain: Bump ARC tools to arc-2016.09-eng005
Date: Wed, 29 Jun 2016 22:13:32 +0200	[thread overview]
Message-ID: <87lh1ng3df.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1467217375-20555-1-git-send-email-abrodkin@synopsys.com> (Alexey Brodkin's message of "Wed, 29 Jun 2016 19:22:55 +0300")

>>>>> "Alexey" == Alexey Brodkin <Alexey.Brodkin@synopsys.com> writes:

 > With this commit we're starting a series of updates of ARC tools.
 > Significantly rewritten arc-2016.03 tools introduced way too many
 > problems highlighted by Buildroot autobuilder. Now in attempt to
 > resolve as many issues as possible by the time final release of
 > arc-2016.09 tools is cut we'll be executing arc-2016.09 series
 > with engineering snapshots like this one.

 > We decided to go this way instead of applying separate patches here
 > and there because ongoing development introduces quite a lot of
 > changes and separate patches are not practical in Buildroot.

 > Moreover this will give us very clean visibility of number of
 > issues we see (hopefully it will decrease over time).

 > One of the important changes introduced in this engineering build
 > is initial set of changes for proper support of PIE on ARC in terms
 > of both building on host and running on ARC target. I expect some
 > PIE-related build breakages to go away and new ones will be treated
 > as the high-priority issues to be fixed ASAP.

 > For now we only update Binutils and GCC while keeping GDB
 > as it is of arc-2016.03 release because there're some issues
 > we'd like to resolve before releasing it to wider audience.

 > So again note this is one of the first engineering builds of
 > arc-2016.09 series and it might have all kinds of breakages,
 > please don't use it for production builds.

 > Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
 > Cc: arc-buildroot at synopsys.com
 > Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
 > Cc: Peter Korsgaard <peter@korsgaard.com>

Committed, thanks. Lets see how this goes ..

-- 
Venlig hilsen,
Peter Korsgaard 

  reply	other threads:[~2016-06-29 20:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 16:22 [Buildroot] [PATCH] toolchain: Bump ARC tools to arc-2016.09-eng005 Alexey Brodkin
2016-06-29 20:13 ` Peter Korsgaard [this message]
2016-06-30  8:13   ` Alexey Brodkin
  -- strict thread matches above, loose matches on Subject: below --
2016-07-11 16:10 Vlad Zakharov
2016-07-11 16:20 ` Vlad Zakharov
2016-07-11 16:30 ` Baruch Siach

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=87lh1ng3df.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox