From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gcc: Fix building on ppc64le GCC 8 host
Date: Thu, 23 Aug 2018 23:52:40 +0200 [thread overview]
Message-ID: <874lfkrbrr.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180730103630.21804-1-joel@jms.id.au> (Joel Stanley's message of "Mon, 30 Jul 2018 20:06:30 +0930")
>>>>> "Joel" == Joel Stanley <joel@jms.id.au> writes:
> When building on a ppc64le host we see this error:
> build/genmatch --gimple ../../gcc/match.pd \
>> tmp-gimple-match.c
> ../../gcc/match.pd:120:1 error: expected (, got NAME
> negative value by 0 gives -0, not +0. */
> This was reported upstream[1] and fixed on the GCC 6 [2] and GCC 7 [3]
> branches:
> Backport from mainline
> 2018-01-10 Kelvin Nilsen <kelvin@gcc.gnu.org>
> * lex.c (search_line_fast): Remove illegal coercion of an
> unaligned pointer value to vector pointer type and replace with
> use of __builtin_vec_vsx_ld () built-in function, which operates
> on unaligned pointer values.
> The patches included in Buildroot contain just the code changes, and not
> the changelog, to make it easer to manage backporting.
> Tested on Ubuntu Cosmic ppc64le.
> [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86162
> [2] https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=261621
> [3] https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=262243
> Signed-off-by: Joel Stanley <joel@jms.id.au>
Committed to 2018.02.x and 2018.05.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2018-08-23 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 10:36 [Buildroot] [PATCH] gcc: Fix building on ppc64le GCC 8 host Joel Stanley
2018-07-31 20:02 ` Thomas Petazzoni
2018-08-23 21:52 ` 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=874lfkrbrr.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