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 17:29:00 -0000 [thread overview]
Message-ID: <bug-47434-4-ZHVuTobZZq@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 #8 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-01-27 17:21:24 UTC ---
(In reply to comment #7)
> I remember the discussion when we first implemented this and we wanted the + on
> Inf to be consistent with -Inf.
Well, the following is in any case wrong:
real :: inf
inf = 0
inf = 1/inf
print "(sp,F0.2)", inf ! SIGN=PLUS
print "(ss,F0.2)", inf ! SIGN=SUPPRESS
print "(s, F0.2)", inf ! SIGN=PROCESSOR_DEFINED
end
The same result for "F4.2": Three times "+Inf". (Ditto for g95.)
For SIGN=SUPPRESS it should just print "Inf", whether "Inf" or "+Inf" is
correct for PROCESSOR_DEFINED is another question. For consistency with the
other compilers - and for consistency with 10.7.2.1(6), one should probably
remove the "+".
For "F4.2" also the other compilers do not seem to print a + with
sign='PROCESSOR_DEFINED' though I am not sure that I like
Intel's/pathscale's/open64's "Infi" for S and SS better. NAG and Sunf95 have "
Inf" for S/SS.
Regarding "0.00" vs ".00" with "F0.2": I do not have any real preference;
following 10.7.2.1(6) I am slightly inclined that ".00" is better.
next prev parent reply other threads:[~2011-01-27 17:21 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
2011-01-27 16:51 ` jvdelisle at gcc dot gnu.org
2011-01-27 17:29 ` burnus at gcc dot gnu.org [this message]
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-ZHVuTobZZq@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).