public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/96711] Internal Compiler Error on NINT() Function
Date: Wed, 19 Aug 2020 19:37:56 +0000 [thread overview]
Message-ID: <bug-96711-4-VsXEyzcBoP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96711-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96711
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |anlauf at gcc dot gnu.org
--- Comment #6 from anlauf at gcc dot gnu.org ---
(In reply to kargl from comment #5)
> m = anint(y)
>
> This will use libquadmath to round y to a quad precision
> floating point integral number, and then the rounded value
> will assigned to m where type conversion occurs.
gfc_conv_intrinsic_aint has the following comment:
/* Round a real value using the specified rounding mode.
We use a temporary integer of that same kind size as the result.
...
This seems not to be done in gfc_conv_intrinsic_int, which is invoked
for nint.
next prev parent reply other threads:[~2020-08-19 19:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 15:18 [Bug fortran/96711] New: " bre08 at eggen dot co.uk
2020-08-19 15:21 ` [Bug fortran/96711] " bre08 at eggen dot co.uk
2020-08-19 15:25 ` bre08 at eggen dot co.uk
2020-08-19 15:26 ` bre08 at eggen dot co.uk
2020-08-19 17:28 ` kargl at gcc dot gnu.org
2020-08-19 18:12 ` kargl at gcc dot gnu.org
2020-08-19 19:37 ` anlauf at gcc dot gnu.org [this message]
2020-08-19 20:11 ` toon at moene dot org
2020-08-19 21:36 ` anlauf at gcc dot gnu.org
2020-08-19 22:04 ` sgk at troutmask dot apl.washington.edu
2020-08-20 13:47 ` bre08 at eggen dot co.uk
2020-08-20 15:39 ` sgk at troutmask dot apl.washington.edu
2020-08-20 15:54 ` bre08 at eggen dot co.uk
2020-08-20 16:58 ` sgk at troutmask dot apl.washington.edu
2020-08-25 20:29 ` anlauf at gcc dot gnu.org
2020-09-07 19:42 ` cvs-commit at gcc dot gnu.org
2020-10-07 7:19 ` schwab@linux-m68k.org
2020-10-07 14:53 ` sgk at troutmask dot apl.washington.edu
2020-10-07 14:59 ` schwab@linux-m68k.org
2020-10-07 15:22 ` kargl at gcc dot gnu.org
2020-10-07 15:26 ` schwab@linux-m68k.org
2020-10-07 21:32 ` anlauf at gcc dot gnu.org
2021-05-20 8:12 ` burnus at gcc dot gnu.org
2021-05-20 9:21 ` bernd.eggen at gmail dot com
2021-07-23 19:59 ` anlauf at gcc dot gnu.org
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=bug-96711-4-VsXEyzcBoP@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).