public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle2 at gmail dot com" <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: Fri, 06 May 2022 01:32:34 +0000 [thread overview] Message-ID: <bug-105361-4-75UOXu23f8@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 Jerry DeLisle <jvdelisle2 at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jvdelisle2 at gmail dot com --- Comment #3 from Jerry DeLisle <jvdelisle2 at gmail dot com> --- Hi Thomas, this is another one I would like to look at since I implemented a lot of this in the beginning. I want to look at the dump and see why the condition is not being set. I have a hunch on this. It has to do with the DTP structure where the status kept.
next prev parent reply other threads:[~2022-05-06 1:32 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 ` [Bug libfortran/105361] " tkoenig at gcc dot gnu.org 2022-04-24 20:04 ` tkoenig at gcc dot gnu.org 2022-05-06 1:32 ` jvdelisle2 at gmail dot com [this message] 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-75UOXu23f8@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).