public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/38439] I/O PD edit descriptor inconsistency Date: Thu, 25 Dec 2008 19:47:00 -0000 [thread overview] Message-ID: <20081225194549.19466.qmail@sourceware.org> (raw) In-Reply-To: <bug-38439-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from jvdelisle at gcc dot gnu dot org 2008-12-25 19:45 ------- g77 runtime accepts this and prints: character(len=25) :: str str = '(1PD24.15E4)' write (*,'(1PD24.15E4)') 1.0d0 WRITE (*,str) 1.0d0 end $ g77 pr38439.f $ ./a.out 1.000000000000000E+00 1.000000000000000E+00 gfortran 4.4: $ gfc -std=legacy pr38439.f pr38439.f:3.72: write (*,'(1PD24.15E4)') 1.0d0 1 Warning: Period required in format specifier at (1) [jerry@lenova pr38439]$ ./a.out 1.000000000000000D+0000 1.000000000000000D+0000 I think I will make the run-time consistent with the compile as far as error messages, giving a runtime warning if not -std-legacy. The 'D' exponent character is different from g77, but is standard conforming. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38439
next prev parent reply other threads:[~2008-12-25 19:47 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-12-07 21:35 [Bug fortran/38439] New: " burnus at gcc dot gnu dot org 2008-12-08 0:53 ` [Bug fortran/38439] " jvdelisle at gcc dot gnu dot org 2008-12-25 19:47 ` jvdelisle at gcc dot gnu dot org [this message] 2009-01-21 6:51 ` jvdelisle at gcc dot gnu dot org 2009-01-22 3:05 ` jvdelisle at gcc dot gnu dot org 2009-01-22 10:55 ` burnus at gcc dot gnu dot org 2009-01-23 5:46 ` jvdelisle at gcc dot gnu dot org 2009-01-24 18:11 ` jvdelisle at gcc dot gnu dot org 2009-04-23 1:52 ` jvdelisle at gcc dot gnu dot org 2009-04-23 2:53 ` kargl at gcc dot gnu dot org 2009-10-11 17:38 ` jvdelisle at gcc dot gnu dot org 2009-10-11 17:41 ` jvdelisle at gcc dot gnu dot org 2009-10-11 19:20 ` jvdelisle at gcc dot gnu dot org 2009-10-12 0:53 ` jvdelisle at gcc dot gnu dot org 2009-10-12 0:54 ` jvdelisle at gcc dot gnu dot org 2009-10-12 7:39 ` dominiq at lps dot ens dot fr 2009-10-12 12:42 ` jvdelisle at gcc dot gnu dot org 2009-10-12 13:32 ` dominiq at lps dot ens dot fr 2009-10-12 13:42 ` jvdelisle at gcc dot gnu dot 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=20081225194549.19466.qmail@sourceware.org \ --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).