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 fortran/56803] New: EOF with namelist read give INTERNAL error instead of END OF FILE error Date: Mon, 01 Apr 2013 19:18:00 -0000 [thread overview] Message-ID: <bug-56803-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56803 Bug #: 56803 Summary: EOF with namelist read give INTERNAL error instead of END OF FILE error Classification: Unclassified Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: burnus@gcc.gnu.org CC: jvdelisle@gcc.gnu.org Blocks: 56744 Follow up to PR56660 comment 19, see also PR56660. The following program - which lacks a "/" - gives with GCC 4.1: Fortran runtime error: End of file But with GCC 4.3 to 4.9 it gives: Fortran runtime error: Internal namelist read error Expected: END of file. Which I also get with NAG, Pathscale, PGI and Crayftn. implicit none integer :: ii namelist /nml/ ii open(99, status="scratch") write(99,'(a)') "&nml ii=55" rewind(99) read(99, nml=nml) print *, ii end
next reply other threads:[~2013-04-01 19:18 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-01 19:18 burnus at gcc dot gnu.org [this message] 2013-04-01 20:10 ` [Bug fortran/56803] " jvdelisle at gcc dot gnu.org 2013-04-01 20:26 ` burnus 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-56803-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).