public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/56743] New: Namelist bug with comment and no blank Date: Tue, 26 Mar 2013 16:20:00 -0000 [thread overview] Message-ID: <bug-56743-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56743 Bug #: 56743 Summary: Namelist bug with comment and no blank Classification: Unclassified Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: janus@gcc.gnu.org Reduced test case (inspired by the one in PR 56660), originally reported by Kai Gallmeister: integer :: value = 100 namelist /nml/ value write (*, nml=nml) open (99, file='nml.dat', status="replace") write(99,*) "&nml" write(99,*) " value=1!11" write(99,*) "/" rewind(99) read (99, nml=nml) write (*, nml=nml) close (99, status="delete") end Output with 4.3, 4.7 and trunk (haven't tried other versions): &NML VALUE= 100, / &NML VALUE= 100, / Expected output: &NML VALUE= 100, / &NML VALUE= 1, / The fact that there is no blank between the number and the comment should not make any difference, right? Unfortunately it does ...
next reply other threads:[~2013-03-26 16:20 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-26 16:20 janus at gcc dot gnu.org [this message] 2013-03-26 16:27 ` [Bug fortran/56743] " dominiq at lps dot ens.fr 2013-03-26 16:58 ` burnus at gcc dot gnu.org 2013-03-30 4:08 ` jvdelisle at gcc dot gnu.org 2013-03-30 10:47 ` burnus at gcc dot gnu.org 2013-05-03 20:32 ` jvdelisle at gcc dot gnu.org 2015-04-07 19:28 ` jvdelisle at gcc dot gnu.org 2015-04-16 2:23 ` jvdelisle at gcc dot gnu.org 2015-04-21 16:14 ` jvdelisle at gcc dot gnu.org 2015-04-21 16:34 ` jvdelisle at gcc dot gnu.org 2015-04-21 16:42 ` 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-56743-4@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).