unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org, "Paul A. Clarke" <pc@us.ibm.com>
Subject: Re: [PATCH v2 3/3] powerpc64le: Add glibc-hwcaps support
Date: Wed, 4 Nov 2020 13:36:27 -0600	[thread overview]
Message-ID: <20201104193627.GT2672@gate.crashing.org> (raw)
In-Reply-To: <87ft5p5xvy.fsf@oldenburg2.str.redhat.com>

Hi Florian,

On Wed, Nov 04, 2020 at 09:28:33AM +0100, Florian Weimer wrote:
> * Segher Boessenkool:
> 
> > Not going to happen.  A new powerpc64le-linux-novec triple (or whatever
> > naming, this is just an example) can be made of course, but the existing
> > name will keep standing for the existing ABI!
> 
> Fine with me.
> 
> >> >> 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.
> >
> > No.
> >
> > -mcpu=power10 enables MMA.  If you do not want all Power10 features, you
> > should not use -mcpu=power10.  It is that simple.
> 
> Then we need a different name, or require MMA for the "power10"
> glibc-hwcaps subdirectory.

Or do nothing.  Glibc doesn't use any MMA code, does it?  This is never
generated automatically, you need to really ask for it in your source
code.

> > Since powerpc64le-linux requires Power8 or later, you always have VMX
> > and VSX enabled there.  In exactly that same way.
> >
> > GCC never generates anything MMA that the user did not explicitly ask
> > for in the source code (with builtins, say), so this is not an issue.
> > Compare this with hardware DFP.
> 
> GCC defines __MMA__ for -mcpu=power10, and source code will evenually be
> sensitive to that macro.

That macro simply says that source code can use MMA builtins and the
like.  Is it important for glibc whether user code uses MMA?

> I think it is important that -mcpu=power10 and the "power10"
> subdirectory mean the same thing.

-mcpu=power10 means "generate code optimised for power10" (and: "it will
probably not run on cpus not compatible to power10").

Is that what that subdir holds as well?


Segher

  reply	other threads:[~2020-11-04 19:37 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 [this message]
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
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=20201104193627.GT2672@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=pc@us.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).