From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gcc: bump to version 8.3.0
Date: Tue, 26 Feb 2019 13:10:38 +0100 [thread overview]
Message-ID: <87wolmda2p.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190224160529.6038-1-romain.naour@smile.fr> (Romain Naour's message of "Sun, 24 Feb 2019 17:05:29 +0100")
>>>>> "Romain" == Romain Naour <romain.naour@smile.fr> writes:
> Remove upsteam xtensa patches:
> https://github.com/gcc-mirror/gcc/commit/68ca69a4854af36c90531b33a4c540464dbc6a23
> https://github.com/gcc-mirror/gcc/commit/972057cb254e355805bfcd4a47d5c6f743cb76f4
> Tested using Toolchain-builder:
> https://gitlab.com/kubu93/toolchains-builder/pipelines/48904471
> Signed-off-by: Romain Naour <romain.naour@smile.fr>
> ---
> There is an existing issue between gdb 8.1.1, musl and kernel-headers
> related to aarch64 SVE support.
> See the same issue with gdb 8.2:
> http://patchwork.ozlabs.org/patch/1030704/
> http://patchwork.ozlabs.org/patch/1030703/
> The bleeding-edge toolchain I tested use kernel-headers 4.19 that
> break gdb 8.1.1 with musl toolchain.
> Using kernel-headers 4.14 build fine.
> This issue is not related to the gcc version bump.
Given that this is a bugfix release I have committed to master, thanks.
Great to see that we no longer need to carry local patches.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2019-02-26 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 16:05 [Buildroot] [PATCH] package/gcc: bump to version 8.3.0 Romain Naour
2019-02-26 12:10 ` 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=87wolmda2p.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