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/34411] hang-up during read of non-expected input Date: Mon, 10 Dec 2007 02:16:00 -0000 [thread overview] Message-ID: <20071210021645.26957.qmail@sourceware.org> (raw) In-Reply-To: <bug-34411-15493@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from jvdelisle at gcc dot gnu dot org 2007-12-10 02:16 ------- First, you are relying on non-portable behavior: F95 Standard 9.4.1.5 Error branch - subpart (2)-> "The position of the file specified in the input/output statement becomes indeterminate" So gfortran does not try to change the file position after the read and the subsequent reads continue to read bad values and ad-infinitum. The loop is in your program. Second, as a Quality of Implementation issue, and under these conditions we can do whatever we want, I have a patch testing that moves the file to the next record position. :) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34411
next prev parent reply other threads:[~2007-12-10 2:16 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-12-09 19:59 [Bug fortran/34411] New: " hroch at physics dot muni dot cz 2007-12-09 21:03 ` [Bug fortran/34411] " burnus at gcc dot gnu dot org 2007-12-09 22:31 ` jvdelisle at gcc dot gnu dot org 2007-12-10 2:16 ` jvdelisle at gcc dot gnu dot org [this message] 2007-12-10 6:44 ` burnus at gcc dot gnu dot org 2007-12-10 19:49 ` dominiq at lps dot ens dot fr 2007-12-11 3:50 ` jvdelisle at gcc dot gnu dot org 2007-12-11 3:56 ` jvdelisle at gcc dot gnu dot org 2007-12-14 19:26 ` 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=20071210021645.26957.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).