public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Janne Blomqvist <blomqvist.janne@gmail.com>
To: Fortran List <fortran@gcc.gnu.org>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, libfortran] PR 49296 List read of file without EOR
Date: Tue, 12 Jul 2011 09:05:00 -0000	[thread overview]
Message-ID: <CAO9iq9HQDNyM9zmRKRG09VJN7D13R7gb_PM=Whn8hO-u+sq-nA@mail.gmail.com> (raw)
In-Reply-To: <CAO9iq9HxGBkH4v=viKn=3Eojkginsd8XgvAkP_NUXPzedb+OyQ@mail.gmail.com>

PING

On Mon, Jul 4, 2011 at 00:57, Janne Blomqvist <blomqvist.janne@gmail.com> wrote:
> Hi,
>
> the attached patch fixes the remaining cases of handling input that
> ends in EOF instead of a normal separator for list formatted read of
> the primitive types. Ok for trunk and 4.6?
>
> 2011-07-04  Janne Blomqvist  <jb@gcc.gnu.org>
>
>        PR libfortran/49296
>        * io/list_read.c (read_logical): Don't error out if a valid value
>        is followed by EOF instead of a normal separator.
>        (read_integer): Likewise.
>
> testsuite:
>
> 2011-07-04  Janne Blomqvist  <jb@gcc.gnu.org>
>
>        PR libfortran/49296
>        * gfortran.dg/read_list_eof_1.f90: Add tests for integer, real,
>        and logical reads.
>
>
> --
> Janne Blomqvist
>



-- 
Janne Blomqvist

  reply	other threads:[~2011-07-12  8:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-03 21:57 Janne Blomqvist
2011-07-12  9:05 ` Janne Blomqvist [this message]
2011-07-12 12:32   ` Jerry DeLisle
  -- strict thread matches above, loose matches on Subject: below --
2011-06-11 10:22 Janne Blomqvist
2011-06-17 19:24 ` Janne Blomqvist
2011-06-18  1:29   ` jerry DeLisle

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='CAO9iq9HQDNyM9zmRKRG09VJN7D13R7gb_PM=Whn8hO-u+sq-nA@mail.gmail.com' \
    --to=blomqvist.janne@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@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).