public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/17871] libgfortran, g77: regression, zero has non-zero exponent
Date: Wed, 20 Apr 2005 06:51:00 -0000 [thread overview]
Message-ID: <20050420065103.13705.qmail@sourceware.org> (raw)
In-Reply-To: <20041006212730.17871.anlauf@hep.tu-darmstadt.de>
------- Additional Comments From fxcoudert at gcc dot gnu dot org 2005-04-20 06:51 -------
On i386-linux, PR 20480 is fixed (see below). If you can confirm on a fresh
built that it is not, please reopen it and state what your platform is.
$ cat a.f
write (*,10) 0.0
10 format (ES12.3)
end
$ gfortran a.f && ./a.out
0.000E+00
$ gfortran -v
Using built-in specs.
Target: i386-linux
Configured with: ../gcc/configure --prefix=/tmp/gfortran-20050419/irun
--enable-languages=c,f95 --host=i386-linux
Thread model: posix
gcc version 4.1.0 20050419 (experimental)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17871
prev parent reply other threads:[~2005-04-20 6:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 21:27 [Bug libfortran/17871] New: libgfortran, g77: regression, P edit descriptor, funny output anlauf at hep dot tu-darmstadt dot de
2004-10-07 13:07 ` [Bug libfortran/17871] " reichelt at gcc dot gnu dot org
2004-10-07 15:41 ` tobi at gcc dot gnu dot org
2005-01-06 14:41 ` tobi at gcc dot gnu dot org
2005-03-13 19:13 ` tobi at gcc dot gnu dot org
2005-03-16 13:24 ` [Bug libfortran/17871] libgfortran, g77: regression, zero has non-zero exponent fxcoudert at gcc dot gnu dot org
2005-03-16 13:50 ` anlauf at hep dot tu-darmstadt dot de
2005-03-16 14:02 ` fxcoudert at gcc dot gnu dot org
2005-03-16 14:31 ` tobi at gcc dot gnu dot org
2005-04-20 2:17 ` pinskia at gcc dot gnu dot org
2005-04-20 6:51 ` fxcoudert at gcc dot gnu dot org [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=20050420065103.13705.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).