public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugs at dhbailey dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/65757] New: gfortran gives incorrect result for anint with real*16 argument
Date: Mon, 13 Apr 2015 23:33:00 -0000 [thread overview]
Message-ID: <bug-65757-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65757
Bug ID: 65757
Summary: gfortran gives incorrect result for anint with real*16
argument
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: bugs at dhbailey dot com
gfortran gives an incorrect result for the anint (nearest whole number)
function for certain real*16 arguments. Here is a simple example:
program anintbug
implicit none
real (kind (0.q0)) q1, q2, q3
q1 = 233181505644407.99996948242187500000q0
q2 = anint (q1)
q3 = 233181505644408.00000000000000000000q0
write (6, '(f50.25)') q1, q2, q3
write (6, '(z35)') q1, q2, q3
stop
end
When compiled with "gfortran anintbug.f90", this program produces the following
output. The second result should equal the third result, but does not.
233181505644407.9999694824218750000000000
233181505644407.9999694824218750000000000
233181505644408.0000000000000000000000000
402EA827999FCEEFFFFC000000000000
402EA827999FCEEFFFFC000000000000
402EA827999FCEF00000000000000000
next reply other threads:[~2015-04-13 23:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 23:33 bugs at dhbailey dot com [this message]
2015-04-14 1:38 ` [Bug libquadmath/65757] " kargl at gcc dot gnu.org
2015-04-14 17:26 ` sgk at troutmask dot apl.washington.edu
2015-04-22 23:19 ` bugs at dhbailey dot com
2015-04-23 0:49 ` jvdelisle at gcc dot gnu.org
2015-04-23 0:55 ` sgk at troutmask dot apl.washington.edu
2015-04-23 1:31 ` jvdelisle at gcc dot gnu.org
2015-04-23 8:05 ` dominiq at lps dot ens.fr
2015-04-23 19:54 ` bugs at dhbailey dot com
2015-04-28 17:32 ` joseph at codesourcery dot com
2015-04-28 21:55 ` sgk at troutmask dot apl.washington.edu
2015-04-28 22:09 ` joseph at codesourcery dot com
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-65757-4@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).