From: Segher Boessenkool <segher@kernel.crashing.org>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: Florian Weimer <fweimer@redhat.com>,
gcc@gcc.gnu.org, libc-alpha@sourceware.org,
linuxppc-dev@lists.ozlabs.org,
Paul E Murphy <murphyp@linux.ibm.com>
Subject: Re: [PATCH Linux] powerpc: add documentation for HWCAPs
Date: Fri, 15 Jul 2022 09:35:54 -0500 [thread overview]
Message-ID: <20220715143554.GY25951@gate.crashing.org> (raw)
In-Reply-To: <1657846871.9qtz2ahf6c.astroid@bobo.none>
On Fri, Jul 15, 2022 at 11:17:24AM +1000, Nicholas Piggin wrote:
> Excerpts from Segher Boessenkool's message of May 25, 2022 4:32 am:
> > Linux runs on ISA 1.xx and ISA 2.01 machines still. "Category" wasn't
> > invented for either yet either, but similar concepts did exist of
> > course.
>
> Not sure what to say about this. It now also has "Compliancy Subset"
> although maybe that's more like a set of features rather than
> incompatible features or modes such as some of the category stuff
> seems to be. I'll try add something.
The compliancy subset stuff is an attempt to simplify things again.
In most cases you want to require a whole swath of feature at once,
if you really try to support fine-grained optional features you need to
test thousands of configurations, while you really can test only ten
(if you are lucky!)
Maybe it is best to just be a bit vague here?
Segher
next prev parent reply other threads:[~2022-07-15 14:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 9:38 Nicholas Piggin
2022-05-24 9:52 ` Florian Weimer
2022-05-24 18:32 ` Segher Boessenkool
2022-07-15 1:17 ` Nicholas Piggin
2022-07-15 14:35 ` Segher Boessenkool [this message]
2022-05-24 17:38 ` Segher Boessenkool
2022-07-15 1:00 ` Nicholas Piggin
2023-06-06 14:49 ` Passing the complex args in the GPR's Umesh Kalappa
2023-06-06 14:58 ` Andrew Pinski
2023-06-06 15:05 ` Umesh Kalappa
2023-06-06 15:16 ` Andrew Pinski
2023-06-06 16:42 ` Segher Boessenkool
2023-06-06 17:07 ` Umesh Kalappa
2023-06-06 17:33 ` David Edelsohn
2023-06-07 13:17 ` Michael Matz
2023-06-06 17:18 ` Joseph Myers
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=20220715143554.GY25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=fweimer@redhat.com \
--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 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).