public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/49296] [4.6/4.7 Regression] Wrong END OF FILE error for list-directed I/O with strings Date: Sun, 03 Jul 2011 15:55:00 -0000 [thread overview] Message-ID: <bug-49296-4-CYDNud4tQG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49296-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49296 --- Comment #12 from Janne Blomqvist <jb at gcc dot gnu.org> 2011-07-03 15:54:05 UTC --- Author: jb Date: Sun Jul 3 15:54:02 2011 New Revision: 175787 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=175787 Log: PR 48296 Accept EOF as separator when reading string with list format. 2011-07-03 Janne Blomqvist <jb@gcc.gnu.org> Backport from mainline: PR libfortran/49296 * io/list_read.c (read_character): Accept EOF as a separator when reading string. 2011-07-03 Janne Blomqvist <jb@gcc.gnu.org> Backport from mainline: PR libfortran/48296 * gfortran.dg/read_list_eof_1.f90: New test. Added: branches/gcc-4_6-branch/gcc/testsuite/gfortran.dg/read_list_eof_1.f90 Modified: branches/gcc-4_6-branch/gcc/testsuite/ChangeLog branches/gcc-4_6-branch/libgfortran/ChangeLog branches/gcc-4_6-branch/libgfortran/io/list_read.c
next prev parent reply other threads:[~2011-07-03 15:55 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-06 6:16 [Bug fortran/49296] New: [4.6/4.7 Regression] Wrong I/O END OF FILE burnus at gcc dot gnu.org 2011-06-06 6:16 ` [Bug fortran/49296] " burnus at gcc dot gnu.org 2011-06-06 9:42 ` [Bug fortran/49296] [4.6/4.7 Regression] Wrong END OF FILE error for list-directed I/O with strings burnus at gcc dot gnu.org 2011-06-06 10:28 ` dominiq at lps dot ens.fr 2011-06-06 10:37 ` dominiq at lps dot ens.fr 2011-06-06 10:43 ` burnus at gcc dot gnu.org 2011-06-06 12:12 ` dominiq at lps dot ens.fr 2011-06-06 12:12 ` [Bug libfortran/49296] " dominiq at lps dot ens.fr 2011-06-06 12:21 ` jvdelisle at gcc dot gnu.org 2011-06-11 8:42 ` jb at gcc dot gnu.org 2011-06-12 13:47 ` rguenth at gcc dot gnu.org 2011-06-17 19:11 ` jb at gcc dot gnu.org 2011-06-18 7:53 ` jb at gcc dot gnu.org 2011-06-20 14:32 ` burnus at gcc dot gnu.org 2011-07-03 15:55 ` jb at gcc dot gnu.org [this message] 2011-07-03 16:01 ` jb at gcc dot gnu.org 2011-07-03 17:38 ` jb at gcc dot gnu.org 2011-07-03 17:40 ` jb at gcc dot gnu.org 2011-07-13 18:48 ` jb at gcc dot gnu.org 2011-07-13 18:53 ` jb at gcc dot gnu.org 2011-07-13 18:54 ` jb 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-49296-4-CYDNud4tQG@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).