From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Harald Anlauf via Fortran <fortran@gcc.gnu.org>
Cc: FX Coudert <fxcoudert@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fortran: add Fortran 2018 IEEE_{MIN,MAX} functions
Date: Wed, 7 Jun 2023 11:50:09 -0700 [thread overview]
Message-ID: <ZIDRYe0E8Nn3xr7t@troutmask.apl.washington.edu> (raw)
In-Reply-To: <e86fcad6-b016-c9d8-f215-e35830d23d74@gmx.de>
On Wed, Jun 07, 2023 at 08:31:35PM +0200, Harald Anlauf via Fortran wrote:
> Hi FX,
>
> On 6/6/23 21:11, FX Coudert via Gcc-patches wrote:
> > Hi,
> >
> > > I cannot see if there is proper support for kind=17 in your patch;
> > > at least the libgfortran/ieee/ieee_arithmetic.F90 part does not
> > > seem to have any related code.
> >
> > Can real(kind=17) ever be an IEEE mode? If so, something seriously wrong happened, because the IEEE modules have no kind=17 mention in them anywhere.
> >
> > Actually, where is the kind=17 documented?
> >
> > FX
>
> I was hoping for Thomas to come forward with some comment, as
> he was quite involved in related work.
>
> There are several threads on IEEE128 for Power on the fortran ML
> e.g. around November/December 2021, January 2022.
>
> I wasn't meaning to block your work, just wondering if the Power
> platform needs more attention here.
>
% cd gcc/gccx/libgfortran
% grep HAVE_GFC_REAL_17 ieee/*
% troutmask:sgk[219] ls ieee
% ieee_arithmetic.F90 ieee_features.F90
% ieee_exceptions.F90 ieee_helper.c
There are zero hits for REAL(17) in the IEEE code. If REAL(17)
is intended to be an IEEE-754 type, then it seems gfortran's
support was never added for it. If anyone has access to a
power system, it's easy to test
program foo
use ieee_arithmetic
print *, ieee_support_datatype(1.e_17)
end program foo
--
Steve
next prev parent reply other threads:[~2023-06-07 18:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 13:19 FX
2023-06-06 15:43 ` Steve Kargl
2023-06-06 15:51 ` Steve Kargl
2023-06-06 18:21 ` Steve Kargl
2023-06-06 19:00 ` Harald Anlauf
2023-06-06 19:11 ` FX Coudert
2023-06-07 18:31 ` Harald Anlauf
2023-06-07 18:50 ` Steve Kargl [this message]
2023-06-08 10:17 ` Thomas Koenig
2023-06-08 10:21 ` FX Coudert
2023-06-08 11:24 ` Thomas Koenig
2023-06-08 16:31 ` Steve Kargl
2023-06-08 18:17 ` Thomas Koenig
2023-06-10 15:24 ` FX Coudert
2023-06-11 9:50 ` Thomas Koenig
2023-06-11 13:43 ` FX Coudert
2023-06-06 19:35 ` FX Coudert
2023-06-07 3:15 ` Steve Kargl
2023-06-10 15:42 ` FX Coudert
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=ZIDRYe0E8Nn3xr7t@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.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).