From: Michael Meissner <meissner@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Michael Meissner <meissner@linux.ibm.com>,
gcc-patches@gcc.gnu.org, David Edelsohn <dje.gcc@gmail.com>,
Bill Schmidt <wschmidt@linux.ibm.com>,
Peter Bergner <bergner@linux.ibm.com>,
Will Schmidt <will_schmidt@vnet.ibm.com>
Subject: Re: [PATCH 1/3] Add IEEE 128-bit min/max support on PowerPC.
Date: Mon, 28 Jun 2021 15:00:02 -0400 [thread overview]
Message-ID: <20210628190002.GB24302@ibm-toto.the-meissners.org> (raw)
In-Reply-To: <20210623235637.GI5077@gate.crashing.org>
On Wed, Jun 23, 2021 at 06:56:37PM -0500, Segher Boessenkool wrote:
> Hi!
>
> On Thu, Jun 17, 2021 at 03:18:48PM -0400, Michael Meissner wrote:
> > > The actual insns only check TARGET_POWER10 (so no TARGET_FLOAT128_HW).
> > > Which is right, this or that?
> >
> > It should include TARGET_FLOAT128_HW.
>
> Okay, so fix that :-)
> > The problem area is a power10 running in
> > big endian mode and running 32-bit code. Because we don't have TImode, we
> > can't enable the IEEE 128-bit hardware instructions.
>
> I don't see why not?
>
> > > > +/* { dg-require-effective-target ppc_float128_hw } */
> > > > +/* { dg-require-effective-target power10_ok } */
> > > > +/* { dg-options "-mdejagnu-cpu=power10 -O2 -ffast-math" } */
> > >
> > > In testcases we can assume that float128_hw is set whenever we have a
> > > p10; we don't manually disable it to make live hard for ourselves ;-)
> >
> > Again, I put it in case somebody builds a BE power10 compiler.
>
> This should still be fixed. And yes, people do test BE p10, of course.
> And BE p10 *should* enable the QP float insns. Does it not currently?
GCC does not enable __float128 by default on BE. The reason is there are no
plans to enable all of the float128 support in glibc in BE. Without a library,
it is kind of useless to enable __float128.
If the compiler enabled __float128, It breaks things that check if __float128
is avaiable. They think __float128 is available, and then they fail when when
they can't anything besides basic arithmetic.
Because the compiler is configured not to enable __float128 in a BE context, we
don't build the __float128 emulator in libgcc.
In addition, BE GCC runs on things that does not have GLIBC (like AIX). If we
enabled it by default, it would break those environments.
A further complication is BE by default is still power4 or power5. You need
VSX support to even pass __float128 arguments. While it is possible to pass
__float128 in GPRs, you run into compatibility issues if one module is compiled
with VSX and another is compiled without setting a base cpu, because one module
will expect things in GPRs and the other in Altivec registers.
And as I've said, the issue with 32-bit move is we don't have TImode support.
Some of the machine indepenent passes want to use an appropriate integer type
to move basic types.
--
Michael Meissner, IBM
IBM, M/S 2506R, 550 King Street, Littleton, MA 01460-6245, USA
email: meissner@linux.ibm.com, phone: +1 (978) 899-4797
next prev parent reply other threads:[~2021-06-28 19:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 0:17 [PATCH 0/3] Add Power10 IEEE 128-bit min, max, conditional move Michael Meissner
2021-06-09 0:21 ` [PATCH 1/3] Add IEEE 128-bit min/max support on PowerPC Michael Meissner
2021-06-17 0:32 ` Ping: " Michael Meissner
2021-06-17 17:39 ` Segher Boessenkool
2021-06-17 19:18 ` Michael Meissner
2021-06-23 23:56 ` Segher Boessenkool
2021-06-28 19:00 ` Michael Meissner [this message]
2021-06-30 17:35 ` Segher Boessenkool
2021-06-09 0:22 ` [PATCH 2/3] Fix IEEE 128-bit min/max test Michael Meissner
2021-06-17 0:33 ` Ping: " Michael Meissner
2021-06-17 18:11 ` Segher Boessenkool
2021-06-17 19:24 ` Michael Meissner
2021-06-17 20:11 ` Michael Meissner
2021-06-25 17:46 ` Segher Boessenkool
2021-06-28 18:41 ` Michael Meissner
2021-06-17 22:56 ` [PATCH 2/3 V2] " Michael Meissner
2021-06-23 19:08 ` Ping: " Michael Meissner
2021-06-23 19:20 ` Michael Meissner
2021-06-30 0:06 ` Segher Boessenkool
2021-06-30 16:25 ` Michael Meissner
2021-06-09 0:24 ` [PATCH 3/3] Add IEEE 128-bit fp conditional move on PowerPC Michael Meissner
2021-06-17 0:34 ` Ping: " Michael Meissner
2021-06-23 19:09 ` Michael Meissner
2021-06-30 19:07 ` Segher Boessenkool
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=20210628190002.GB24302@ibm-toto.the-meissners.org \
--to=meissner@linux.ibm.com \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=will_schmidt@vnet.ibm.com \
--cc=wschmidt@linux.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).