From: Michael Meissner <meissner@linux.ibm.com>
To: Michael Meissner <meissner@linux.ibm.com>,
Joseph Myers <joseph@codesourcery.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
"Kewen.Lin" <linkw@linux.ibm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
David Edelsohn <dje.gcc@gmail.com>,
Jakub Jelinek <jakub@redhat.com>,
Peter Bergner <bergner@linux.ibm.com>,
Richard Biener <richard.guenther@gmail.com>,
Richard Sandiford <richard.sandiford@arm.com>
Subject: Re: [RFC/PATCH] Remove the workaround for _Float128 precision [PR107299]
Date: Mon, 9 Jan 2023 22:21:52 -0500 [thread overview]
Message-ID: <Y7zZ0JAZG7UUBsr4@toto.the-meissners.org> (raw)
In-Reply-To: <Y7i/o3sr0Q8N3ASw@toto.the-meissners.org>
On Fri, Jan 06, 2023 at 07:41:07PM -0500, Michael Meissner wrote:
> On Wed, Dec 21, 2022 at 09:40:24PM +0000, Joseph Myers wrote:
> > On Wed, 21 Dec 2022, Segher Boessenkool wrote:
> >
> > > > --- a/gcc/tree.cc
> > > > +++ b/gcc/tree.cc
> > > > @@ -9442,15 +9442,6 @@ build_common_tree_nodes (bool signed_char)
> > > > if (!targetm.floatn_mode (n, extended).exists (&mode))
> > > > continue;
> > > > int precision = GET_MODE_PRECISION (mode);
> > > > - /* Work around the rs6000 KFmode having precision 113 not
> > > > - 128. */
> > >
> > > It has precision 126 now fwiw.
> > >
> > > Joseph: what do you think about this patch? Is the workaround it
> > > removes still useful in any way, do we need to do that some other way if
> > > we remove this?
> >
> > I think it's best for the TYPE_PRECISION, for any type with the binary128
> > format, to be 128 (not 126).
> >
> > It's necessary that _Float128, _Float64x and long double all have the same
> > TYPE_PRECISION when they have the same (binary128) format, or at least
> > that TYPE_PRECISION for _Float128 >= that for long double >= that for
> > _Float64x, so that the rules in c_common_type apply properly.
> >
> > How the TYPE_PRECISION compares to that of __ibm128, or of long double
> > when that's double-double, is less important.
>
> I spent a few days on working on this. I have patches to make the 3 128-bit
> types to all have TYPE_PRECISION of 128. To do this, I added a new mode macro
> (FRACTIONAL_FLOAT_MODE_NO_WIDEN) that takes the same arguments as
> FRACTIONAL_FLOAT_MODE.
...
I had the patches to change the precision to 128, and I just ran them. C and
C++ do not seem to be bothered by changing the precision to 128 (once I got it
to build, etc.). But Fortran on the other hand does actually use the precision
to differentiate between IBM extended double and IEEE 128-bit. In particular,
the following 3 tests fail when long double is IBM extended double:
gfortran.dg/PR100914.f90
gfortran.dg/c-interop/typecodes-array-float128.f90
gfortran.dg/c-interop/typecodes-scalar-float128.f90
I tried adding code to use the old precisions for Fortran, but not for C/C++,
but it didn't seem to work.
So while it might be possible to use a single 128 for the precision, it needs
more work and attention, particularly on the Fortran side.
I'm not sure it is worth it to try and change things.
--
Michael Meissner, IBM
PO Box 98, Ayer, Massachusetts, USA, 01432
email: meissner@linux.ibm.com
next prev parent reply other threads:[~2023-01-10 3:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 9:02 Kewen.Lin
2022-12-21 21:24 ` Segher Boessenkool
2022-12-21 21:40 ` Joseph Myers
2022-12-21 22:45 ` Jakub Jelinek
2022-12-22 6:37 ` Kewen.Lin
2022-12-22 18:18 ` Segher Boessenkool
2022-12-22 19:48 ` Joseph Myers
2022-12-22 22:09 ` Segher Boessenkool
2023-01-03 23:27 ` Michael Meissner
2023-01-07 0:41 ` Michael Meissner
2023-01-10 3:21 ` Michael Meissner [this message]
2023-01-10 18:23 ` Jakub Jelinek
2023-01-11 20:26 ` Michael Meissner
2022-12-22 6:07 ` Kewen.Lin
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=Y7zZ0JAZG7UUBsr4@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=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=linkw@linux.ibm.com \
--cc=richard.guenther@gmail.com \
--cc=richard.sandiford@arm.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).