public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "john.harper at vuw dot ac.nz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/111022] ES0.0E0 format gave ES0.dE0 output with d too high.
Date: Mon, 04 Sep 2023 22:32:38 +0000	[thread overview]
Message-ID: <bug-111022-4-AojylunkPn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111022-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111022

--- Comment #20 from john.harper at vuw dot ac.nz ---
With the first test case all the EN outputs were 666. but the Fortran 2018
standard 13.7.2.3.4 paragraph 2 requires that EN0.0 produce 666.E+0 but 
Table 13.2 first ENw.d line appears to require either 666.E+00 or 666.+000 
unless my copy of F2018 is out of date. (I note that the F2023 standard 
removed the ambiguity by including "with w > 0" in the offending line of 
Table 13.2.) However F2018 is unambiguous and agrees with F2023 on 
EN0.0E0, requiring 666.E+0

With the second test case, which used 66600, I think all Jerry's outputs 
are correct.

On Mon, 4 Sep 2023, jvdelisle at gcc dot gnu.org wrote:

> Date: Mon, 4 Sep 2023 17:12:30 +0000
> From: jvdelisle at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org>
> To: John Harper <john.harper@vuw.ac.nz>
> Subject: [Bug libfortran/111022] ES0.0E0 format gave ES0.dE0 output with d too
>      high.
> Resent-Date: Tue, 5 Sep 2023 05:12:45 +1200 (NZST)
> Resent-From: <john.harper@vuw.ac.nz>
> 
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111022
>
> --- Comment #18 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
> With Johns test case from Comment #15 and the patch in Comment #17 I get the
> following:
>
> $ ./a.out
> real kinds 4 8 10 16
> With (A,1X,EN0.0  ) 666.
> With (A,1X,EN0.0  ) 666.
> With (A,1X,EN0.0  ) 666.
> With (A,1X,EN0.0  ) 666.
> With (A,1X,EN0.0E0) 666.
> With (A,1X,EN0.0E0) 666.
> With (A,1X,EN0.0E0) 666.
> With (A,1X,EN0.0E0) 666.
> With (A,1X,ES0.0  ) 7.E+2
> With (A,1X,ES0.0  ) 7.E+2
> With (A,1X,ES0.0  ) 7.E+2
> With (A,1X,ES0.0  ) 7.E+2
> With (A,1X,ES0.0E0) 7.E+2
> With (A,1X,ES0.0E0) 7.E+2
> With (A,1X,ES0.0E0) 7.E+2
> With (A,1X,ES0.0E0) 7.E+2
> ERROR STOP Scale factor out of range in format specifier 'E' or 'D'
>
> Notice that the width of exponents is also minimized and where the exponent is
> zero it is not shown at all.  If I do specify an exponent width it shown. For
> example with exponent width of 4 and changing the value to 66600 I get:
>
> $ ./a.out
> real kinds 4 8 10 16
> With (A,1X,EN0.0  ) 67.E+3
> With (A,1X,EN0.0  ) 67.E+3
> With (A,1X,EN0.0  ) 67.E+3
> With (A,1X,EN0.0  ) 67.E+3
> With (A,1X,EN0.0E4) 67.E+0003
> With (A,1X,EN0.0E4) 67.E+0003
> With (A,1X,EN0.0E4) 67.E+0003
> With (A,1X,EN0.0E4) 67.E+0003
> With (A,1X,ES0.0  ) 7.E+4
> With (A,1X,ES0.0  ) 7.E+4
> With (A,1X,ES0.0  ) 7.E+4
> With (A,1X,ES0.0  ) 7.E+4
> With (A,1X,ES0.0E4) 7.E+0004
> With (A,1X,ES0.0E4) 7.E+0004
> With (A,1X,ES0.0E4) 7.E+0004
> With (A,1X,ES0.0E4) 7.E+0004
> ERROR STOP Scale factor out of range in format specifier 'E' or 'D'
>
> This seems reasonable to me. Other opinions?
>
> -- 
> You are receiving this mail because:
> You reported the bug.
>


-- John Harper, School of Mathematics and Statistics
Victoria Univ. of Wellington, PO Box 600, Wellington 6140, New Zealand.
e-mail john.harper@vuw.ac.nz

  parent reply	other threads:[~2023-09-04 22:32 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15  4:41 [Bug fortran/111022] New: " john.harper at vuw dot ac.nz
2023-08-15 19:45 ` [Bug libfortran/111022] " anlauf at gcc dot gnu.org
2023-08-15 23:49 ` john.harper at vuw dot ac.nz
2023-08-16  0:15 ` jvdelisle at gcc dot gnu.org
2023-08-16  3:39 ` jvdelisle at gcc dot gnu.org
2023-08-23  5:46 ` john.harper at vuw dot ac.nz
2023-08-25  0:48 ` jvdelisle at gcc dot gnu.org
2023-08-26  4:26 ` jvdelisle at gcc dot gnu.org
2023-08-26  5:40 ` john.harper at vuw dot ac.nz
2023-08-27 15:38 ` jvdelisle at gcc dot gnu.org
2023-08-27 19:41 ` anlauf at gcc dot gnu.org
2023-08-27 21:40 ` john.harper at vuw dot ac.nz
2023-08-27 22:17 ` jvdelisle at gcc dot gnu.org
2023-08-28  1:26 ` john.harper at vuw dot ac.nz
2023-08-28  1:44 ` john.harper at vuw dot ac.nz
2023-08-29 23:45 ` john.harper at vuw dot ac.nz
2023-08-30  0:30 ` jvdelisle at gcc dot gnu.org
2023-09-03 16:20 ` jvdelisle at gcc dot gnu.org
2023-09-04 17:12 ` jvdelisle at gcc dot gnu.org
2023-09-04 18:38 ` anlauf at gcc dot gnu.org
2023-09-04 22:32 ` john.harper at vuw dot ac.nz [this message]
2023-09-05  2:57 ` jvdelisle at gcc dot gnu.org
2023-10-15  2:12 ` jvdelisle at gcc dot gnu.org
2023-10-15  7:03 ` john.harper at vuw dot ac.nz
2024-01-25 22:21 ` jvdelisle at gcc dot gnu.org
2024-01-26  5:24 ` john.harper at vuw dot ac.nz
2024-01-26 18:29 ` anlauf at gcc dot gnu.org
2024-01-26 18:50 ` jvdelisle at gcc dot gnu.org
2024-01-30 13:19 ` jvdelisle at gcc dot gnu.org
2024-02-03 17:33 ` cvs-commit at gcc dot gnu.org
2024-02-11 22:19 ` nightstrike at gmail dot com
2024-02-11 22:21 ` anlauf at gcc dot gnu.org
2024-02-11 22:25 ` nightstrike at gmail dot com
2024-02-11 22:30 ` nightstrike at gmail dot com
2024-02-11 22:58 ` anlauf at gcc dot gnu.org
2024-02-12  2:40 ` nightstrike at gmail dot com
2024-02-12 20:12 ` jvdelisle at gcc dot gnu.org
2024-02-13  0:42 ` cvs-commit at gcc dot gnu.org
2024-02-13  0:43 ` 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-111022-4-AojylunkPn@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).