From: FX <fxcoudert@gmail.com>
To: Mikael Morin <morin-mikael@orange.fr>
Cc: Thomas Koenig <tkoenig@netcologne.de>,
gcc-patches@gcc.gnu.org, FX via Fortran <fortran@gcc.gnu.org>
Subject: Re: [PATCH] Fortran: Add IEEE_SIGNBIT and IEEE_FMA functions
Date: Sun, 11 Sep 2022 11:57:24 +0200 [thread overview]
Message-ID: <F9F2B602-79AE-4252-A5E2-1AC6E8B586D2@gmail.com> (raw)
In-Reply-To: <041d1f6b-9812-e1e3-dbd7-0416888804bc@orange.fr>
Hi Mikael,
> As a first step, one could check the use rename lists; what's done for iso_fortran_env can be used as an example.
Yes, but iso_fortran_env is handled entirely in front-end, not through external files.
This is what I plan to do when migrating the IEEE modules to front-end, but it is a big task.
> Another possibility is mimicking or modifying gfc_resolve_intrinsic, which already does a similar job for intrinsic procedures.
That’s probably the best place to put it for now, indeed. Thanks for the advice.
FX
next prev parent reply other threads:[~2022-09-11 9:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 13:46 FX
2022-08-31 14:22 ` FX
2022-09-06 13:26 ` FX
2022-09-07 5:43 ` Thomas Koenig
2022-09-07 18:57 ` FX
2022-09-09 17:50 ` FX
2022-09-10 10:14 ` FX
2022-09-11 9:49 ` Mikael Morin
2022-09-11 9:57 ` FX [this message]
2022-09-11 10:23 ` Mikael Morin
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=F9F2B602-79AE-4252-A5E2-1AC6E8B586D2@gmail.com \
--to=fxcoudert@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=morin-mikael@orange.fr \
--cc=tkoenig@netcologne.de \
/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).