public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <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: Thu, 25 Jan 2024 22:21:01 +0000 [thread overview] Message-ID: <bug-111022-4-Y4biELLgY1@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 #24 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> --- Currently gfortran does the following: character(20) :: fmt character(9) :: buffer fmt = "(1a1,d0.2,1a1)" write(buffer,fmt) ">", 3.0, "<" print *, buffer fmt = "(1a1,e0.2,1a1)" write(buffer,fmt) ">", 3.0, "<" print *, buffer end $ gfc question.f90 $ ./a.out >0.30D+1< >0.30E+1< Why not: $ ./a.out >3.00D+0< >3.00E+0< What does Intel do?
next prev parent reply other threads:[~2024-01-25 22:21 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 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 [this message] 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-Y4biELLgY1@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: linkBe 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).