From: Segher Boessenkool <segher@kernel.crashing.org>
To: Paul E Murphy <murphyp@linux.ibm.com>
Cc: gcc@gcc.gnu.org, libc-alpha@sourceware.org,
linuxppc-dev@lists.ozlabs.org,
Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [RFC Linux patch] powerpc: add documentation for HWCAPs
Date: Fri, 20 May 2022 12:42:50 -0500 [thread overview]
Message-ID: <20220520174250.GG25951@gate.crashing.org> (raw)
In-Reply-To: <c1f6c6c9-4cc7-0dcb-360d-9ae0df6378b4@linux.ibm.com>
On Fri, May 20, 2022 at 09:21:43AM -0500, Paul E Murphy wrote:
> >+PPC_FEATURE_HAS_ALTIVEC
> >+ Vector (aka Altivec, VSX) facility is available.
>
> I think "(aka Altivec, VSX)" might be more accurately stated as "(aka
> Altivec)"?
"Also known as AltiVec or VMX", yes.
> >+PPC_FEATURE_HAS_DFP
> >+ DFP facility is available.
>
> Maybe something like "Decimal floating point instructions are available
> to userspace. Individual instruction availability is dependent on the
> reported architecture version."?
That is true for *all* facilities, and even the base architecture! This
is not only hypothetical, either.
Segher
next prev parent reply other threads:[~2022-05-20 17:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 5:15 [RFC Linux patch] powerpc: add documentation for HWCAPs Nicholas Piggin
2022-05-20 9:21 ` Michael Ellerman
2022-05-20 12:06 ` Nicholas Piggin
2022-05-20 14:21 ` Paul E Murphy
2022-05-20 17:42 ` Segher Boessenkool [this message]
2022-05-21 0:11 ` Nicholas Piggin
2022-05-23 14:19 ` Paul E Murphy
2022-05-20 16:58 ` Peter Bergner
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=20220520174250.GG25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc@gcc.gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=murphyp@linux.ibm.com \
--cc=npiggin@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.