public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/30009] Unformatted reads exceeding storage units gives EOF instead of ERR Date: Wed, 06 Dec 2006 19:26:00 -0000 [thread overview] Message-ID: <20061206192603.22858.qmail@sourceware.org> (raw) In-Reply-To: <bug-30009-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #13 from tkoenig at gcc dot gnu dot org 2006-12-06 19:26 ------- Subject: Bug 30009 Author: tkoenig Date: Wed Dec 6 19:25:44 2006 New Revision: 119592 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=119592 Log: 2006-12-06 Thomas Koenig <Thomas.Koenig@online.de> PR libfortran/30009 PR libfortran/30056 * gfortran.dg/read_eof_4.f90: Add tests. * gfortran.dg/readwrite_unf_direct_eor_1.f90: New test. * gfortran.dg/unf_read_corrupted_1.f90: New test. 2006-12-06 Thomas Koenig <Thomas.Koenig@online.de> PR libfortran/30009 PR libfortran/30056 * libgfortran.h: Add ERROR_CORRUPT_FILE to error_codes. * runtime/error.c (translate_error): Add handling for ERROR_CORRUPT_FILE. * io/transfer.c (read_block_direct): Add comment about EOR for stream files. Remove test for no bytes left for direct access files. Generate an ERROR_SHORT_RECORD if the read was short. For unformatted sequential files: Check endfile condition. Remove test for no bytes left. End of file here means that the file structure has been corrupted. Pre-position the file for the next record in case of error. (write_buf): Whitespace fix. Subtract the number of bytes written from bytes_left. Added: trunk/gcc/testsuite/gfortran.dg/readwrite_unf_direct_eor_1.f90 trunk/gcc/testsuite/gfortran.dg/unf_read_corrupted_1.f90 Modified: trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gfortran.dg/read_eof_4.f90 trunk/libgfortran/ChangeLog trunk/libgfortran/io/transfer.c trunk/libgfortran/libgfortran.h trunk/libgfortran/runtime/error.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30009
next prev parent reply other threads:[~2006-12-06 19:26 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-11-28 21:34 [Bug libfortran/30009] New: Unformatted reads exceeding one record should use the next record not give EOF burnus at gcc dot gnu dot org 2006-11-28 21:49 ` [Bug libfortran/30009] " brooks at gcc dot gnu dot org 2006-11-28 21:49 ` brooks at gcc dot gnu dot org 2006-11-28 22:23 ` tkoenig at gcc dot gnu dot org 2006-11-28 22:58 ` [Bug libfortran/30009] Unformatted reads exceeding storage units gives EOF instead of ERR burnus at gcc dot gnu dot org 2006-12-02 21:56 ` tkoenig at gcc dot gnu dot org 2006-12-02 23:32 ` jvdelisle at gcc dot gnu dot org 2006-12-03 8:32 ` burnus at gcc dot gnu dot org 2006-12-03 14:06 ` tkoenig at gcc dot gnu dot org 2006-12-03 14:17 ` burnus at gcc dot gnu dot org 2006-12-03 18:56 ` tkoenig at gcc dot gnu dot org 2006-12-03 21:02 ` tkoenig at gcc dot gnu dot org 2006-12-04 2:18 ` jvdelisle at gcc dot gnu dot org 2006-12-05 19:01 ` patchapp at dberlin dot org 2006-12-06 19:26 ` tkoenig at gcc dot gnu dot org [this message] 2006-12-10 22:17 ` tkoenig at gcc dot gnu dot org 2006-12-15 22:27 ` [Bug libfortran/30009] [4.1 only] " tkoenig at gcc dot gnu dot org 2006-12-16 0:35 ` jvdelisle at gcc dot gnu dot org 2006-12-16 8:18 ` tkoenig at gcc dot gnu dot org 2007-01-02 4:48 ` 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=20061206192603.22858.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).