Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain: bump ARC tools to arc-2019.03 release
Date: Sat, 22 Jun 2019 07:49:21 +0200	[thread overview]
Message-ID: <20190622074921.43631db1@windsurf> (raw)
In-Reply-To: <20190619092532.40543-1-Evgeniy.Didin@synopsys.com>

Hello,

On Wed, 19 Jun 2019 12:25:32 +0300
Evgeniy Didin <Evgeniy.Didin@synopsys.com> wrote:

> This commit finally bumps ARC tools to the most recent arc-2018.09 release version.
> 
> ARC GNU tools of version arc-2018.09 bring some quite significant changes like:
>  * Binutils v2.32.51.20190308 with additional ARC patches
>  * GCC 8.3.1 with additional ARC patches
>  * glibc 2.29 with additional ARC patches
> More information on this release could be found here:
>  https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases/tag/arc-2019.03-release

This release seems to have a new compiler bug, affecting a number of
packages. The failure looks like this:

   internal compiler error: in arc_legitimize_pic_address, at config/arc/arc.c:6104

See:

  http://autobuild.buildroot.net/results/288/28860e57593db31438d8516c0d3c6c3d6403c07e/build-end.log
  http://autobuild.buildroot.net/results/bd6/bd6bddbc20c98e9c903e1c9defebc2f5ddef7abc/build-end.log
  http://autobuild.buildroot.net/results/4b6/4b688cecce61ef885ea1f3f72ac50d8bfb2364b6/build-end.log

Did you already notice those failures ?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      parent reply	other threads:[~2019-06-22  5:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-19  9:25 [Buildroot] [PATCH] toolchain: bump ARC tools to arc-2019.03 release Evgeniy Didin
2019-06-19  9:39 ` Baruch Siach
2019-06-19 11:50 ` Thomas Petazzoni
2019-06-22  5:49 ` 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=20190622074921.43631db1@windsurf \
    --to=thomas.petazzoni@bootlin.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