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/29627] [4.1 only] partial unformatted reads shouldn't succeed
Date: Sat, 04 Nov 2006 14:04:00 -0000	[thread overview]
Message-ID: <20061104140438.30829.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29627-10391@http.gcc.gnu.org/bugzilla/>



------- Comment #10 from tkoenig at gcc dot gnu dot org  2006-11-04 14:04 -------
Subject: Bug 29627

Author: tkoenig
Date: Sat Nov  4 14:04:27 2006
New Revision: 118480

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=118480
Log:
2006-11-04  Thomas Koenig  <Thomas.Koenig@online.de>

        PR libfortran/29627
        Backport from trunk
        * libgfortran.h: Add ERROR_SHORT_RECORD
        * runtime/error.c (translate_error): Add case
        for ERROR_SHORT_RECORD.
        * io/transfer.c (read_block_direct):  Remove unneeded
        tests for standard input, padding and formatted I/O.
        If the record is short, read in as much data as possible,
        then raise the error.

2006-11-04  Thomas Koenig  <Thomas.Koenig@online.de>

        PR libfortran/29627
        Backport from trunk
        * gfortran.dg/unf_short_record_1.f90:  New test.


Added:
    branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/unf_short_record_1.f90
Modified:
    branches/gcc-4_1-branch/gcc/testsuite/ChangeLog
    branches/gcc-4_1-branch/libgfortran/ChangeLog
    branches/gcc-4_1-branch/libgfortran/io/transfer.c
    branches/gcc-4_1-branch/libgfortran/libgfortran.h
    branches/gcc-4_1-branch/libgfortran/runtime/error.c


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29627


  parent reply	other threads:[~2006-11-04 14:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-28 18:10 [Bug libfortran/29627] New: " tkoenig at gcc dot gnu dot org
2006-10-28 18:11 ` [Bug libfortran/29627] " tkoenig at gcc dot gnu dot org
2006-10-28 19:30 ` tkoenig at gcc dot gnu dot org
2006-10-28 21:24 ` tkoenig at gcc dot gnu dot org
2006-10-28 23:21 ` jvdelisle at gcc dot gnu dot org
2006-10-29 11:49 ` tkoenig at gcc dot gnu dot org
2006-10-29 11:59 ` tkoenig at gcc dot gnu dot org
2006-10-31 20:58 ` tkoenig at gcc dot gnu dot org
2006-11-01 10:17 ` [Bug libfortran/29627] [4.2/4.1 only] " tkoenig at gcc dot gnu dot org
2006-11-03 11:22 ` tkoenig at gcc dot gnu dot org
2006-11-03 11:30 ` [Bug libfortran/29627] [4.1 " tkoenig at gcc dot gnu dot org
2006-11-04 14:04 ` tkoenig at gcc dot gnu dot org [this message]
2006-11-04 14:05 ` tkoenig at gcc dot gnu dot org
2006-11-30 19:26 ` chaoyingfu 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=20061104140438.30829.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: link
Be 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).