From: Tulio Magno Quites Machado Filho via Libc-alpha <libc-alpha@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Subject: Re: POWER build failure due to scv instruction
Date: Thu, 21 Jan 2021 14:55:37 -0300 [thread overview]
Message-ID: <874kja41k6.fsf@linux.ibm.com> (raw)
In-Reply-To: <87y2gmtekt.fsf@oldenburg.str.redhat.com>
Florian Weimer via Libc-alpha <libc-alpha@sourceware.org> writes:
> 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.
I haven't seen this yet.
Using ".machine power9" in this code will require Binutils 2.27.
We already have other places doing the same thing and that's why I proposed
this patch:
https://patchwork.sourceware.org/project/glibc/patch/20201202225602.1085609-1-tuliom@linux.ibm.com/
I'm afraid that's too late for glibc 2.33, but I plan to submit it for 2.34.
> In any case, NEWS and INSTALL need to be updated with the appropriate
> binutils version requirement. If scv instruction support is required,
> that would be 2.29, I think, but better double-check this.
That's indeed Binutils 2.27.
An alternative solution is to use a .long with the scv 0 instruction.
--
Tulio Magno
prev parent reply other threads:[~2021-01-21 17:55 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
2021-01-21 17:55 ` Tulio Magno Quites Machado Filho via Libc-alpha [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
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=874kja41k6.fsf@linux.ibm.com \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.com \
--cc=tuliom@linux.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).