From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
To: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Cc: Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>
Subject: Re: POWER build failure due to scv instruction
Date: Thu, 21 Jan 2021 18:40:05 +0100 [thread overview]
Message-ID: <87czxytci2.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <87y2gmtekt.fsf@oldenburg.str.redhat.com> (Florian Weimer via Libc-alpha's message of "Thu, 21 Jan 2021 17:55:14 +0100")
* Florian Weimer via Libc-alpha:
> Building libc-start.o fails on powerpc64le-linux-gnu with:
>
> …/csu/libc-start.s:623: Error: unrecognized opcode: `scv'
>
> And indeed this can be reproduced with:
>
> .machine power8
> .text
> scv 0
>
> This seems to happen with only some binutils versions. Specifically, I
> see it with 4100e6999664833defb8ee038f75812d9b85f9c7 from
> binutils-2_35-branch, but oddly enough not with Fedora's 2.35.1-21.fc34
> version, which is why I haven't reported this so far.
It's powerpc64-linux-gnu vs powerpc64le-linux-gnu.
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
next prev parent reply other threads:[~2021-01-21 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 16:55 POWER build failure due to scv instruction Florian Weimer via Libc-alpha
2021-01-21 17:40 ` Florian Weimer via Libc-alpha [this message]
2021-01-21 17:55 ` Tulio Magno Quites Machado Filho via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87czxytci2.fsf@oldenburg.str.redhat.com \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.com \
--cc=tuliom@linux.vnet.ibm.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).