public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: FX <fxcoudert@gmail.com>
To: Mikael Morin <morin-mikael@orange.fr>
Cc: Fortran <fortran@gcc.gnu.org>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fortran 2018 rounding modes changes
Date: Mon, 19 Sep 2022 19:29:47 +0200	[thread overview]
Message-ID: <99C0538F-658C-4A7C-92B9-29E0C38A28CE@gmail.com> (raw)
In-Reply-To: <c6cd7bee-01c1-afee-6520-ae67189f0487@orange.fr>

Hi,

> Hmm, not really convinced, but that's a possible interpretation, I guess.

It seems to me to be in line with the handling of all other IEEE intrinsics: the user is responsible for querying support before calling any relevant routine. I admit that there is no explicit language in the case of the rounding mode, I will try to find time to ask for an official interpretation.


> My sentence was about IEEE_*S*ET_ROUNDING_MODE actually.
> My point that we previously reported an error (at compile time) to a user that would try to pass a radix 10 while we now silently do... something else that was requested (i.e. set the radix 2 rounding mode).

Oh sorry, I see what you mean and you’re totally right. This is an easy improvement, and while I believe it is undefined behaviour in any case, we can easily improve that.


> I think it's worth at least documenting that only radix 2 is supported.

That also makes sense. I’ll propose a patch.

Thanks,
FX

  reply	other threads:[~2022-09-19 17:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31 18:29 FX
2022-08-31 20:42 ` Bernhard Reutner-Fischer
2022-08-31 21:23   ` FX
2022-09-10 10:21 ` FX
2022-09-19 12:26   ` FX
2022-09-19 15:35 ` Mikael Morin
2022-09-19 16:17   ` FX
2022-09-19 17:09     ` Mikael Morin
2022-09-19 17:29       ` FX [this message]
2022-09-21  9:15         ` FX

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=99C0538F-658C-4A7C-92B9-29E0C38A28CE@gmail.com \
    --to=fxcoudert@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=morin-mikael@orange.fr \
    /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).