public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <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:03:00 -0000	[thread overview]
Message-ID: <bug-47434-4-ewFti3mFek@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 #6 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-01-27 13:30:30 UTC ---
(In reply to comment #4)
> (In reply to comment #3)
> > Regarding the other cases:
> > Similarly for the '+' sign on Inf.  Until now we have chosen to emit the
> > optional characters.

There seems to be a bug with regards to S:

  print "(s,F0.2)", inf

still prints "+Inf". ("The edit descriptors SS, SP, and S set the sign mode
corresponding to the SIGN= specifier values SUPPRESS, PLUS, and
PROCESSOR_DEFINED, respectively.")


"(6) On output, with I, B, O, Z, F, and G editing, the specified value of the
field width w may be zero. In such cases, the processor selects the smallest
positive actual field width that does not result in a field filled with
asterisks" (10.7.2.1 General rules)

I have to agree with Thomas here: ".00" and "Inf" are the shorted possible
strings, unless SP (sign="PLUS") is used; then "+.00" and "+Inf" are the
shortest possible strings.

In that sense, none of my 10 compiler gets it right ...


  parent reply	other threads:[~2011-01-27 13:30 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
2011-01-27 14:03 ` burnus at gcc dot gnu.org [this message]
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-ewFti3mFek@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).