From: Tulio Magno Quites Machado Filho via Libc-alpha <libc-alpha@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>,
Segher Boessenkool <segher@kernel.crashing.org>
Cc: , libc-alpha@sourceware.org, "Paul A. Clarke" <pc@us.ibm.com>
Subject: Re: [PATCH v2 3/3] powerpc64le: Add glibc-hwcaps support
Date: Mon, 16 Nov 2020 11:51:27 -0300 [thread overview]
Message-ID: <87pn4de4nk.fsf@linux.ibm.com> (raw)
In-Reply-To: <87ft5p5xvy.fsf@oldenburg2.str.redhat.com>
Florian Weimer <fweimer@redhat.com> writes:
> GCC defines __MMA__ for -mcpu=power10, and source code will evenually be
> sensitive to that macro.
>
> I think it is important that -mcpu=power10 and the "power10"
> subdirectory mean the same thing.
I agree to stick with -mcpu values.
It was a bad interpretation of my part when I used OpenPOWER Foundation's
documents to explain the availability of features on GCC. These are different
usages.
GCC uses -mcpu to:
... specify a specific processor. Code generated under those options
runs best on that processor, and may not run at all on others.
So, -mcpu=power10 is the IBM POWER10 processor that supports MMA.
But then, we're back to this point you had raised:
> I think we need documentation what it means for a processor to implement
> ISA 3.0, and not altivec.
Unfortunately, I think this documentation will only exist after a new -mcpu
value is created.
--
Tulio Magno
next prev parent reply other threads:[~2020-11-16 14:51 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 via Libc-alpha
2020-10-12 15:21 ` [PATCH 1/3] elf: Add " Florian Weimer via Libc-alpha
2020-10-13 16:28 ` Paul A. Clarke via Libc-alpha
2020-10-14 13:58 ` Florian Weimer via Libc-alpha
2020-10-14 15:14 ` Paul A. Clarke via Libc-alpha
2020-10-14 15:19 ` Florian Weimer via Libc-alpha
2020-10-20 17:23 ` Paul A. Clarke via Libc-alpha
2020-10-12 15:21 ` [PATCH v2 2/3] x86_64: Add glibc-hwcaps support Florian Weimer via Libc-alpha
2020-10-12 18:11 ` H.J. Lu via Libc-alpha
2020-10-13 9:29 ` Florian Weimer via Libc-alpha
2020-10-13 11:02 ` H.J. Lu via Libc-alpha
2020-10-13 11:24 ` Florian Weimer via Libc-alpha
2020-10-13 11:43 ` H.J. Lu via Libc-alpha
2020-10-12 15:22 ` [PATCH v2 3/3] powerpc64le: " Florian Weimer via Libc-alpha
2020-10-13 16:36 ` Paul A. Clarke via Libc-alpha
2020-10-20 17:23 ` Paul A. Clarke via Libc-alpha
2020-10-29 16:26 ` Florian Weimer via Libc-alpha
2020-10-30 23:10 ` Tulio Magno Quites Machado Filho via Libc-alpha
2020-11-02 10:15 ` Florian Weimer via Libc-alpha
2020-11-03 15:14 ` Tulio Magno Quites Machado Filho via Libc-alpha
2020-11-03 16:29 ` Florian Weimer via Libc-alpha
2020-11-03 23:02 ` Segher Boessenkool
2020-11-04 8:28 ` Florian Weimer via Libc-alpha
2020-11-04 19:36 ` Segher Boessenkool
2020-11-04 19:56 ` Florian Weimer via Libc-alpha
2020-11-04 21:58 ` Segher Boessenkool
2020-11-05 11:40 ` Florian Weimer via Libc-alpha
2020-11-05 21:42 ` Segher Boessenkool
2020-11-09 18:32 ` Florian Weimer via Libc-alpha
2020-11-16 14:51 ` Tulio Magno Quites Machado Filho via Libc-alpha [this message]
2020-11-16 19:35 ` Segher Boessenkool
2020-11-23 10:20 ` Florian Weimer 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=87pn4de4nk.fsf@linux.ibm.com \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.com \
--cc=pc@us.ibm.com \
--cc=segher@kernel.crashing.org \
--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).