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/47434] Wrong field width for NaN with (F0.n) formatting
Date: Thu, 27 Jan 2011 14:01:00 -0000	[thread overview]
Message-ID: <bug-47434-4-XLUOPCzZGc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47434-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Thomas Henlich <thenlich at users dot sourceforge.net> 2011-01-27 13:25:15 UTC ---
(In reply to comment #3)
> The copy of the F2008 standard I have says in 10.7.2.3.2 F editing:
> 
> "When w is zero, the processor selects the field width."

My interpretation is this:

Section 10.7.2.1 (General rules) applies to these cases, which demands
specifically:

"... the processor selects the smallest positive actual field width that does
not result in a field filled with asterisks. ..."

The statement from 10.7.2.3.2 "When w is zero, the processor selects the field
width." does only refer to this. IMHO it does not suggest the possibility to
include optional characters (a leading decimal zero or plus sign) which make
the field width larger than required.

In the examples, since w=3 ("F3.2") does not result in a field filled with
asterisks, and is the smallest possible such value, the processor must select a
field width of 3.

Also, it is inconsistent that the following commands should result in a
different output:

print "(F0.2)", 0.0
print "(F0.2)", tiny(0.0)

0.00
.00


  parent reply	other threads:[~2011-01-27 13:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 13:19 [Bug libfortran/47434] New: " thenlich at users dot sourceforge.net
2011-01-24 13:26 ` [Bug libfortran/47434] " jvdelisle at gcc dot gnu.org
2011-01-24 14:49 ` thenlich at users dot sourceforge.net
2011-01-27 13:23 ` jvdelisle at gcc dot gnu.org
2011-01-27 13:30 ` burnus at gcc dot gnu.org
2011-01-27 14:01 ` thenlich at users dot sourceforge.net [this message]
2011-01-27 14:03 ` burnus at gcc dot gnu.org
2011-01-27 16:51 ` jvdelisle at gcc dot gnu.org
2011-01-27 17:29 ` burnus at gcc dot gnu.org
2011-01-27 18:31 ` thenlich at users dot sourceforge.net
2011-01-29 17:37 ` jvdelisle at gcc dot gnu.org
2011-01-29 17:40 ` jvdelisle at gcc dot gnu.org
2011-01-29 19:29 ` jvdelisle at gcc dot gnu.org
2011-02-02 18:15 ` dnovillo at gcc dot gnu.org
2011-02-02 18:16 ` dnovillo 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-47434-4-XLUOPCzZGc@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).