public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/105361] Incorrect end-of-file condition for derived-type I/O Date: Sun, 24 Apr 2022 19:57:05 +0000 [thread overview] Message-ID: <bug-105361-4-imcKazg0bj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105361-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105361 --- Comment #1 from Thomas Koenig <tkoenig at gcc dot gnu.org> --- This "fixes" the bug in question, but is almost certainly entirely incorrect for a lot of other cases. Will have to look a bit further. --- a/libgfortran/io/list_read.c +++ b/libgfortran/io/list_read.c @@ -2364,13 +2364,13 @@ finish_list_read (st_parameter_dt *dtp) if (likely (dtp->u.p.child_saved_iostat == LIBERROR_OK)) { c = next_char (dtp); if (c == EOF) { free_line (dtp); - hit_eof (dtp); + // hit_eof (dtp); return; } if (c != '\n') eat_line (dtp); } }
next prev parent reply other threads:[~2022-04-24 19:57 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-23 16:29 [Bug libfortran/105361] New: " tkoenig at gcc dot gnu.org 2022-04-24 19:57 ` tkoenig at gcc dot gnu.org [this message] 2022-04-24 20:04 ` [Bug libfortran/105361] " tkoenig at gcc dot gnu.org 2022-05-06 1:32 ` jvdelisle2 at gmail dot com 2024-03-06 2:53 ` jvdelisle at gcc dot gnu.org 2024-03-12 1:08 ` 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-105361-4-imcKazg0bj@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).