From: Florian Weimer <fweimer@redhat.com>
To: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>
Cc: libc-alpha@sourceware.org, "Paul A. Clarke" <pc@us.ibm.com>
Subject: Re: [PATCH v2 3/3] powerpc64le: Add glibc-hwcaps support
Date: Tue, 03 Nov 2020 17:29:08 +0100 [thread overview]
Message-ID: <87361q8kvf.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <87mtzyfp5g.fsf@linux.ibm.com> (Tulio Magno Quites Machado Filho's message of "Tue, 03 Nov 2020 12:14:51 -0300")
* Tulio Magno Quites Machado Filho:
> Florian Weimer <fweimer@redhat.com> writes:
>
>> I think we need documentation what it means for a processor to implement
>> ISA 3.0, and not altivec. Or for that matter, what an implementation of
>> powerpc64le-*-linux-gnu without altivec looks like. Presumably, it will
>> be different yet again from the original hardware used during
>> architecture bring-up.
>
> I think we already have this documented in a couple of places in different
> documents from the OpenPOWER Foundation.
Yes, but all those documents say that Altivec + VSX are required for
powerpc64le-*-linux-gnu. Your summary below seems to re-confirm that.
My point was that if we want powerpc64le-*-linux-gnu to stand for
something different (without Altivec/VSX), we need (new) documentation
that says what it means.
>> ISA features that cannot automatically and pervasively used by compilers
>> can be excluded as well. MMA could be in that category, and I think
>> cryptography-related instructions generally are.
>
> MMA is indeed optional for Linux.
> AFAICS, cryptography-related instructions are part of SIMD and should be
> required for Linux.
Then I think we should change GCC not to enable MMA with -mcpu=power10.
The other change is that I should check for PPC_FEATURE2_HAS_IEEE128 for
power9, and add a comment that ALTIVEC and VSX are implied by the place
in the source tree (I deliberately made all this specific to
powerpc64le-*-linux-gnu on the glibc side, like we didn't define new ABI
levels for i386).
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:[~2020-11-03 16:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 15:21 [PATCH v2 0/3] glibc-hwcaps support for LD_LIBRARY_PATH Florian Weimer
2020-10-12 15:21 ` [PATCH 1/3] elf: Add " Florian Weimer
2020-10-13 16:28 ` Paul A. Clarke
2020-10-14 13:58 ` Florian Weimer
2020-10-14 15:14 ` Paul A. Clarke
2020-10-14 15:19 ` Florian Weimer
2020-10-20 17:23 ` Paul A. Clarke
2020-10-12 15:21 ` [PATCH v2 2/3] x86_64: Add glibc-hwcaps support Florian Weimer
2020-10-12 18:11 ` H.J. Lu
2020-10-13 9:29 ` Florian Weimer
2020-10-13 11:02 ` H.J. Lu
2020-10-13 11:24 ` Florian Weimer
2020-10-13 11:43 ` H.J. Lu
2020-10-12 15:22 ` [PATCH v2 3/3] powerpc64le: " Florian Weimer
2020-10-13 16:36 ` Paul A. Clarke
2020-10-20 17:23 ` Paul A. Clarke
2020-10-29 16:26 ` Florian Weimer
2020-10-30 23:10 ` Tulio Magno Quites Machado Filho
2020-11-02 10:15 ` Florian Weimer
2020-11-03 15:14 ` Tulio Magno Quites Machado Filho
2020-11-03 16:29 ` Florian Weimer [this message]
2020-11-03 23:02 ` Segher Boessenkool
2020-11-04 8:28 ` Florian Weimer
2020-11-04 19:36 ` Segher Boessenkool
2020-11-04 19:56 ` Florian Weimer
2020-11-04 21:58 ` Segher Boessenkool
2020-11-05 11:40 ` Florian Weimer
2020-11-05 21:42 ` Segher Boessenkool
2020-11-09 18:32 ` Florian Weimer
2020-11-16 14:51 ` Tulio Magno Quites Machado Filho
2020-11-16 19:35 ` Segher Boessenkool
2020-11-23 10:20 ` Florian Weimer
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=87361q8kvf.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=pc@us.ibm.com \
--cc=tuliom@ascii.art.br \
/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).