public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/35036] illegal E format descriptor produces wrong output
Date: Thu, 31 Jan 2008 14:10:00 -0000 [thread overview]
Message-ID: <20080131124609.14269.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35036-15709@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from burnus at gcc dot gnu dot org 2008-01-31 12:46 -------
(In reply to comment #9)
> Sun f95 gives:
> Error 1078: scale factor out of range
> ifort gives:
> ********
g95 and openf95 give the same result as ifort:
********
While NAG f95 follows sunf95 by giving the run-time error:
Scale factor 0 out of range for d=0
This is for "write(*, '(E8.0)') 1e5".
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35036
next prev parent reply other threads:[~2008-01-31 12:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 2:01 [Bug fortran/35036] New: " furue at hawaii dot edu
2008-01-31 2:25 ` [Bug fortran/35036] " pinskia at gcc dot gnu dot org
2008-01-31 3:06 ` kargl at gcc dot gnu dot org
2008-01-31 3:10 ` furue at hawaii dot edu
2008-01-31 4:10 ` kargl at gcc dot gnu dot org
2008-01-31 4:44 ` furue at hawaii dot edu
2008-01-31 5:46 ` kargl at gcc dot gnu dot org
2008-01-31 6:55 ` jvdelisle at gcc dot gnu dot org
2008-01-31 6:56 ` furue at hawaii dot edu
2008-01-31 8:17 ` jvdelisle at gcc dot gnu dot org
2008-01-31 14:10 ` burnus at gcc dot gnu dot org [this message]
2008-02-02 8:28 ` jvdelisle at gcc dot gnu dot org
2008-02-02 11:14 ` dominiq at lps dot ens dot fr
2008-02-02 19:37 ` jvdelisle at gcc dot gnu dot org
2008-02-03 0:07 ` jvdelisle at gcc dot gnu dot org
2008-02-21 2:21 ` jvdelisle at gcc dot gnu dot org
2008-02-21 2:24 ` jvdelisle at gcc dot gnu dot org
2008-02-21 2:24 ` jvdelisle at gcc dot gnu dot 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=20080131124609.14269.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).