public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "thenlich at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/47567] Wrong output for small absolute values with F editing
Date: Sat, 05 Feb 2011 07:46:00 -0000	[thread overview]
Message-ID: <bug-47567-4-Vlgel7feKR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47567-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Thomas Henlich <thenlich at users dot sourceforge.net> 2011-02-05 07:45:57 UTC ---
(In reply to comment #6)
> Regardless of this choice, the following should all print the same result,
> which they currently don't.
> 
> print "(F1.0)", 0.0  ! => 0
> print "(F1.0)", 0.001 ! => *
> print "(F1.0)", 0.01  ! => *
> print "(F0.0)", 0.0   ! => 0
> print "(F0.0)", 0.001 ! => *
> print "(F0.0)", 0.01  ! => *

Sorry, but what I meant was that the following should print the same:
print "(F1.0)", 0.0  ! => 0
print "(F1.0)", 0.001 ! => *
print "(F1.0)", 0.01  ! => *

And the following should print the same:
print "(F0.0)", 0.0   ! => 0
print "(F0.0)", 0.001 ! => *
print "(F0.0)", 0.01  ! => *


  parent reply	other threads:[~2011-02-05  7:46 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01  9:42 [Bug libfortran/47567] New: " thenlich at users dot sourceforge.net
2011-02-01 11:27 ` [Bug libfortran/47567] " burnus at gcc dot gnu.org
2011-02-01 13:48 ` jvdelisle at gcc dot gnu.org
2011-02-05  1:33 ` jvdelisle at gcc dot gnu.org
2011-02-05  2:10 ` jvdelisle at gcc dot gnu.org
2011-02-05  6:22 ` jvdelisle at gcc dot gnu.org
2011-02-05  7:41 ` thenlich at users dot sourceforge.net
2011-02-05  7:46 ` thenlich at users dot sourceforge.net [this message]
2011-02-05  7:53 ` thenlich at users dot sourceforge.net
2011-02-05 13:15 ` jvdelisle at gcc dot gnu.org
2011-02-05 17:59 ` jvdelisle at gcc dot gnu.org
2011-02-06 22:15 ` jvdelisle at gcc dot gnu.org
2011-02-07  8:21 ` thenlich at users dot sourceforge.net
2011-02-08  7:17 ` thenlich at users dot sourceforge.net
2011-02-08 12:40 ` jvdelisle at gcc dot gnu.org
2011-02-17  6:51 ` jvdelisle at gcc dot gnu.org
2011-02-17 19:40 ` jvdelisle at gcc dot gnu.org
2011-02-19 15:20 ` jvdelisle at gcc dot gnu.org
2011-02-19 15:36 ` jvdelisle at gcc dot gnu.org
2011-02-19 15:53 ` jvdelisle at gcc dot gnu.org
2011-02-21 13:42 ` thenlich at users dot sourceforge.net
2011-02-21 14:30 ` jvdelisle at gcc dot gnu.org
2011-02-21 14:33 ` jvdelisle at gcc dot gnu.org
2011-02-24  5:32 ` jvdelisle at gcc dot gnu.org
2011-02-24  5:33 ` jvdelisle at gcc dot gnu.org
2011-02-24  6:59 ` jvdelisle at gcc dot gnu.org
2011-02-25 14:05 ` thenlich at users dot sourceforge.net
2011-02-25 14:08 ` thenlich at users dot sourceforge.net
2011-02-28 21:41 ` jvdelisle at gcc dot gnu.org
2011-03-01  2:25 ` jvdelisle at gcc dot gnu.org
2011-03-01  2:28 ` jvdelisle at gcc dot gnu.org
2011-03-01  2:30 ` jvdelisle at gcc dot gnu.org
2011-03-02 14:01 ` thenlich at users dot sourceforge.net

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-47567-4-Vlgel7feKR@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).