public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67509] [6 regression] FAIL: gfortran.dg/ieee/ieee_7.f90 -O0 execution test
Date: Thu, 10 Sep 2015 21:39:00 -0000 [thread overview]
Message-ID: <bug-67509-4-DErWM1vWeA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67509-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67509
--- Comment #3 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> ---
(In reply to Pat Haugen from comment #2)
> I see the same thing on both powerpc64/powerpc64le:
>
> pthaugen@genoa:~$ ~/install/gcc/trunk/bin/gfortran z.f90 && ./a.out
> 4 8 16
> 16 16
> 291
> 8
> 8
> 8
> 8
That's weird, because it would mean that the "decimal exponent range" (i.e. the
largest possible power of ten) is 291, which is smaller than the range of 307
for a regular double. I know that ppc long double is the non-IEEE "double
double" format, but this should give it the same range as double.
Can you tell me what this outputs?
print *, range(0._4), range(0._8), range(0._16)
print *, huge(0._4), huge(0._8), huge(0._16)
print *, tiny(0._4), tiny(0._8), tiny(0._16)
end
next prev parent reply other threads:[~2015-09-10 21:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 22:47 [Bug fortran/67509] New: " schwab@linux-m68k.org
2015-09-10 21:11 ` [Bug fortran/67509] " fxcoudert at gcc dot gnu.org
2015-09-10 21:27 ` pthaugen at gcc dot gnu.org
2015-09-10 21:39 ` fxcoudert at gcc dot gnu.org [this message]
2015-09-10 21:57 ` schwab@linux-m68k.org
2015-09-10 22:11 ` fxcoudert at gcc dot gnu.org
2015-09-11 13:18 ` schwab@linux-m68k.org
2015-09-14 11:12 ` rguenth 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-67509-4-DErWM1vWeA@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).