From: Segher Boessenkool <segher@kernel.crashing.org>
To: 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 2/3] Fix IEEE 128-bit min/max test.
Date: Fri, 25 Jun 2021 12:46:37 -0500 [thread overview]
Message-ID: <20210625174637.GM5077@gate.crashing.org> (raw)
In-Reply-To: <20210617201140.GA9392@ibm-toto.the-meissners.org>
On Thu, Jun 17, 2021 at 04:11:40PM -0400, Michael Meissner wrote:
> On Thu, Jun 17, 2021 at 01:11:58PM -0500, Segher Boessenkool wrote:
> > > --- a/gcc/testsuite/gcc.target/powerpc/float128-minmax.c
> > > +++ b/gcc/testsuite/gcc.target/powerpc/float128-minmax.c
> > > @@ -1,6 +1,5 @@
> > > -/* { dg-do compile { target lp64 } } */
> >
> > Does that work? Why was it there before?
>
> The lp64 eliminates 32-bit, which does not support hardware IEEE 128-bit due to
> the lack of TImode.
I still do not understand this. Why would support for QP float require
TImode? "Need an integer mode of the same size" is not a convincing
argument, since double-double is a 16 byte mode as well.
> The test was written before the ppc_float128_hw test. Now
> that we have ppc_float128_hw, we don't need an explicit lp64.
Ah good, some progress. Well, it *is* an improvement, a better
abstraction, but on the other hand it only hides the actual problems
deeper :-/
> > > /* { dg-require-effective-target powerpc_p9vector_ok } */
> > > -/* { dg-require-effective-target float128 } */
> > > +/* { dg-require-effective-target ppc_float128_hw } */
> >
> > Why is it okay to no longer run this test where it ran before?
>
> The ppc_float128_hw test is a more precise test than just float128 and power9.
You did not delete the p9 test though.
Segher
next prev parent reply other threads:[~2021-06-25 17:47 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
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 [this message]
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=20210625174637.GM5077@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=meissner@linux.ibm.com \
--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).