public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebay.20.tedlap at spamgourmet dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/48602] Invalid F conversion of G descriptor for values close to powers of 10
Date: Wed, 04 May 2011 12:17:00 -0000 [thread overview]
Message-ID: <bug-48602-4-0A8Qpccre8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48602-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48602
Lionel GUEZ <ebay.20.tedlap at spamgourmet dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ebay.20.tedlap at
| |spamgourmet dot com
--- Comment #47 from Lionel GUEZ <ebay.20.tedlap at spamgourmet dot com> 2011-05-04 12:15:16 UTC ---
(In reply to comment #46)
> I have started on the second phase of this effort which is to get rid of the
> floating point issue on -m32 machines.
Hello. I have noticed a bug which seems related to the one you are describing.
According to the Fortran 95 standard, printing the number 0.96 with the format
1pg7.1 should give the same result than with format f3.0. Thus, the result
should be 1., but Gfortran produces the surprising result 0. Is it the same
bug?
Sincerely,
Lionel GUEZ
next prev parent reply other threads:[~2011-05-04 12:17 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 8:02 [Bug libfortran/48602] New: " thenlich at users dot sourceforge.net
2011-04-14 15:20 ` [Bug libfortran/48602] " jvdelisle at gcc dot gnu.org
2011-04-15 19:37 ` jvdelisle at gcc dot gnu.org
2011-04-15 20:01 ` thenlich at users dot sourceforge.net
2011-04-15 20:15 ` jvdelisle at gcc dot gnu.org
2011-04-15 20:42 ` thenlich at users dot sourceforge.net
2011-04-15 21:00 ` jvdelisle at gcc dot gnu.org
2011-04-16 4:30 ` jvdelisle at gcc dot gnu.org
2011-04-16 6:43 ` thenlich at users dot sourceforge.net
2011-04-16 14:38 ` jvdelisle at frontier dot com
2011-04-16 15:46 ` thenlich at users dot sourceforge.net
2011-04-16 16:03 ` jvdelisle at gcc dot gnu.org
2011-04-16 16:11 ` jvdelisle at gcc dot gnu.org
2011-04-16 17:07 ` jvdelisle at gcc dot gnu.org
2011-04-16 17:28 ` thenlich at users dot sourceforge.net
2011-04-16 17:45 ` thenlich at users dot sourceforge.net
2011-04-17 12:40 ` jvdelisle at gcc dot gnu.org
2011-04-17 13:26 ` thenlich at users dot sourceforge.net
2011-04-17 13:47 ` Jerry DeLisle
2011-04-17 13:47 ` jvdelisle at frontier dot com
2011-04-18 3:51 ` jvdelisle at gcc dot gnu.org
2011-04-18 3:53 ` jvdelisle at gcc dot gnu.org
2011-04-18 3:58 ` jvdelisle at gcc dot gnu.org
2011-04-18 6:01 ` thenlich at users dot sourceforge.net
2011-04-18 6:02 ` thenlich at users dot sourceforge.net
2011-04-18 6:32 ` thenlich at users dot sourceforge.net
2011-04-18 8:42 ` thenlich at users dot sourceforge.net
2011-04-18 8:43 ` thenlich at users dot sourceforge.net
2011-04-18 8:54 ` mikael at gcc dot gnu.org
2011-04-18 18:46 ` jvdelisle at gcc dot gnu.org
2011-04-18 18:57 ` jvdelisle at gcc dot gnu.org
2011-04-19 2:07 ` jvdelisle at gcc dot gnu.org
2011-04-19 6:07 ` burnus at gcc dot gnu.org
2011-04-19 6:09 ` thenlich at users dot sourceforge.net
2011-04-19 15:29 ` jvdelisle at gcc dot gnu.org
2011-04-19 16:23 ` burnus at gcc dot gnu.org
2011-04-19 20:03 ` jvdelisle at gcc dot gnu.org
2011-04-20 4:19 ` jvdelisle at gcc dot gnu.org
2011-04-20 6:44 ` thenlich at users dot sourceforge.net
2011-04-20 12:39 ` thenlich at users dot sourceforge.net
2011-04-20 13:02 ` burnus at gcc dot gnu.org
2011-04-21 12:45 ` jvdelisle at gcc dot gnu.org
2011-04-21 16:37 ` thenlich at users dot sourceforge.net
2011-04-21 19:09 ` jvdelisle at gcc dot gnu.org
2011-04-23 11:45 ` thenlich at users dot sourceforge.net
2011-04-29 15:00 ` jvdelisle at gcc dot gnu.org
2011-04-29 15:17 ` jvdelisle at gcc dot gnu.org
2011-05-02 12:53 ` jvdelisle at gcc dot gnu.org
2011-05-04 12:17 ` ebay.20.tedlap at spamgourmet dot com [this message]
2011-05-04 12:50 ` thenlich at users dot sourceforge.net
2011-05-04 13:05 ` jvdelisle at frontier dot com
2011-05-05 10:48 ` ebay.20.tedlap at spamgourmet dot com
2011-05-05 10:54 ` ebay.20.tedlap at spamgourmet dot com
2011-05-05 12:34 ` jvdelisle at frontier dot com
2011-05-05 12:41 ` jvdelisle at gcc dot gnu.org
2011-05-06 1:33 ` jvdelisle 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-48602-4-0A8Qpccre8@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).