public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/33469] Default formats for real input are not precise enough
Date: Wed, 03 Oct 2007 19:34:00 -0000	[thread overview]
Message-ID: <20071003193436.26812.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33469-12313@http.gcc.gnu.org/bugzilla/>



------- Comment #11 from dominiq at lps dot ens dot fr  2007-10-03 19:34 -------
BTW I have forgotten to explain why I have to use an auxiliary variable 'z': if
I usenearest(0.0_8,1.0_8); I get

default_format_1_db.f90:70.29:

        if (abs(x-y)>nearest(0.0_8,1.0_8)) print *, x, y, x-y
                            1
Error: Result of NEAREST underflows its kind at (1)
default_format_1_db.f90:84.29:

        if (abs(x-y)>nearest(0.0_8,1.0_8)) print *, x, y, x-y
                            1
Error: Result of NEAREST underflows its kind at (1)
default_format_1_db.f90:93.25:

  use test_default_format
                        1
Fatal Error: Can't open module file 'test_default_format.mod' for reading at
(1): No such file or directory

Producing a hard error for an underflow is indeed an incredibely clever idea!-(

Reminds me of a compiler which crunched NaNs and Infs with delight, but aborted
on underflow, very handy for waves simulations!


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33469


      parent reply	other threads:[~2007-10-03 19:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-18  9:46 [Bug fortran/33469] New: Add one digit to the default formatted output dominiq at lps dot ens dot fr
2007-09-18  9:47 ` [Bug fortran/33469] " dominiq at lps dot ens dot fr
2007-09-18 17:57 ` burnus at gcc dot gnu dot org
2007-09-19  9:54 ` fxcoudert at gcc dot gnu dot org
2007-09-19  9:55 ` fxcoudert at gcc dot gnu dot org
2007-09-19  9:56 ` [Bug libfortran/33469] Default formats for real input are not precise enough fxcoudert at gcc dot gnu dot org
2007-09-19 12:38 ` dominiq at lps dot ens dot fr
2007-10-01 23:28 ` fxcoudert at gcc dot gnu dot org
2007-10-02  0:37 ` fxcoudert at gcc dot gnu dot org
2007-10-02  8:29 ` dominiq at lps dot ens dot fr
2007-10-02 23:28 ` fxcoudert at gcc dot gnu dot org
2007-10-02 23:31 ` fxcoudert at gcc dot gnu dot org
2007-10-03 19:30 ` dominiq at lps dot ens dot fr
2007-10-03 19:34 ` dominiq at lps dot ens dot fr [this message]

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=20071003193436.26812.qmail@sourceware.org \
    --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).