From: FX <fxcoudert@gmail.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
Thomas Koenig <tkoenig@netcologne.de>,
fortran@gcc.gnu.org
Subject: Re: powerpc64le real(kind=16) and IEEE_{ARITHMETIC,EXCEPTIONS} modules
Date: Tue, 25 Jan 2022 16:13:53 +0100 [thread overview]
Message-ID: <DEE8E13E-FD49-4C08-8784-6B44631DDEDA@gmail.com> (raw)
In-Reply-To: <b504bc8f-3324-c91d-520b-5c185929a2aa@codesourcery.com>
> Thus, more functions could be handled in the compiler itself.
> (Likewise for INTMOD_IEEE_EXCEPTIONS, not that I know whether
> that has any relevant functions.)
In theory, there is no reason why we need an explicit .mod file in the library for any of the three IEEE modules. They would probably be better treated as compiler intrinsics in the front-end itself, in fact, like all other intrinsics. It would also be easier to adjust for generic forms, and provide better diagnostics for mismatching arguments, etc. This seems to be the way to go, as the next standard versions have added even more intrinsics, some of which really shouldn’t be function calls (comparison, ordering, etc).
The reason those modules are not fully implemented in the front-end is simple: I didn’t know how to implement them directly in the front-end, and I am not entirely sure we have the appropriate stuff for that. ISO_FORTRAN_ENV is implemented in the front-end, but its members are simpler, really.
In a way, you can see this as a call for help: if someone front-end-savvy has ideas how to do this, we could partner up ;)
FX
prev parent reply other threads:[~2022-01-25 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 11:44 Jakub Jelinek
2022-01-25 11:59 ` Tobias Burnus
2022-01-25 15:13 ` FX [this message]
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=DEE8E13E-FD49-4C08-8784-6B44631DDEDA@gmail.com \
--to=fxcoudert@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=tkoenig@netcologne.de \
--cc=tobias@codesourcery.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).