From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
To: 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: Thu, 05 Nov 2020 12:40:29 +0100 [thread overview]
Message-ID: <87sg9oyqtu.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <20201104215820.GV2672@gate.crashing.org> (Segher Boessenkool's message of "Wed, 4 Nov 2020 15:58:20 -0600")
* Segher Boessenkool:
> On Wed, Nov 04, 2020 at 08:56:05PM +0100, Florian Weimer wrote:
>> * Segher Boessenkool:
>>
>> >> > -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.
>>
>> glibc's internal use does not matter in this context. Programmers must
>> be able to drop their own libraries built with -mcpu=power10 into the
>> power10 subdirectory. If GCC turns on MMA by default for this switch
>> and glibc selects the power10 subdirectory without checking for MMA
>> support, then this isn't guaranteed to work.
>
> Are you saying that it is *normal* for people to put very different code
> into libc like this? Wow.
>
>> We have been through this with x86-64 already. I don't want to produce
>> the same bug.
>
> No code in libc should ever use MMA, imnsho.
Oh, I see now. I think we don't agree about the scope of the
glibc-hwcaps feature.
It's going to be used to ELF multilibs in general, not just glibc
components. So a BLAS implementation could use it and drop its
implementation DSOs into the appropriate directories.
That's why vector features such as MMA matter in this context.
Given this additional context, I hope we can agree that a rule for
programmers like “build with -mcpu=power10 for the power10 glibc-hwcaps
subdirectory“ has a lot of value.
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-05 11:40 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 [this message]
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=87sg9oyqtu.fsf@oldenburg2.str.redhat.com \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.com \
--cc=pc@us.ibm.com \
--cc=segher@kernel.crashing.org \
/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).