public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/19595] [4.0 only] eor does not work
Date: Tue, 03 May 2005 19:41:00 -0000 [thread overview]
Message-ID: <20050503194014.7574.qmail@sourceware.org> (raw)
In-Reply-To: <20050123205037.19595.Thomas.Koenig@online.de>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-05-03 19:40 -------
Subject: Bug 19595
CVSROOT: /cvs/gcc
Module name: gcc
Branch: gcc-4_0-branch
Changes by: tkoenig@gcc.gnu.org 2005-05-03 19:39:36
Modified files:
libgfortran : ChangeLog
libgfortran/io : transfer.c
gcc/testsuite : ChangeLog
Added files:
gcc/testsuite/gfortran.dg: eor_handling_1.f90 eor_handling_2.f90
eor_handling_3.f90 eor_handling_4.f90
eor_handling_5.f90 noadv_size.f90
pad_no.f90
Log message:
2005-05-03 Thomas Koenig <Thomas.Koenig@online.de>
Backport from mainline:
PR libfortran/17992
PR libfortran/19568
PR libfortran/19595
PR libfortran/20005
PR libfortran/20092
PR libfortran/20131
PR libfortran/20661
PR libfortran/20744
* io/transfer.c (top level): eor_condition: New static variable.
(read_sf): Remove unnecessary zeroing of buffer (there is enough
information in its length).
Return a string of length 0 (to be padded by caller) if EOR was
seen previously.
Remove erroneous special casing of EOR for standard input.
Set eor_condition for non-advancing I/O if an end of line was
detected.
Increment ioparm.size if necessary.
(formatted_transfer): Skip the function if there is an EOR condition.
(data_transfer_init): Initialize eor_condition to zero (false).
(next_record_r): Clear sf_seen_eor if a \n has been seen already.
(finalize_transfer): If there is an EOR condition, raise the error.
2005-05-03 Thomas Koenig <Thomas.Koenig@online.de>
Backport from mainline:
* eor_handling_1.f90: New test case.
* eor_handling_2.f90: New test case.
* eor_handling_3.f90: New test case.
* eor_handling_4.f90: New test case.
* eor_handling_5.f90: New test case.
* noadv_size.f90: New test case.
* pad_no.f90: New test case.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.163.2.22&r2=1.163.2.23
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/transfer.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.32.2.2&r2=1.32.2.3
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.5084.2.156&r2=1.5084.2.157
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/eor_handling_1.f90.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=NONE&r2=1.1.6.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/eor_handling_2.f90.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=NONE&r2=1.1.6.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/eor_handling_3.f90.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=NONE&r2=1.1.6.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/eor_handling_4.f90.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=NONE&r2=1.1.6.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/eor_handling_5.f90.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=NONE&r2=1.1.6.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/noadv_size.f90.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=NONE&r2=1.1.6.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/pad_no.f90.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=NONE&r2=1.1.6.1
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19595
next prev parent reply other threads:[~2005-05-03 19:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-23 20:50 [Bug libfortran/19595] New: eor and advance="yes" should not mix Thomas dot Koenig at online dot de
2005-01-24 8:13 ` [Bug libfortran/19595] " Thomas dot Koenig at online dot de
2005-01-24 20:38 ` Thomas dot Koenig at online dot de
2005-01-25 12:45 ` Thomas dot Koenig at online dot de
2005-01-26 21:43 ` [Bug libfortran/19595] eor does not work Thomas dot Koenig at online dot de
2005-01-26 21:48 ` pinskia at gcc dot gnu dot org
2005-01-29 15:45 ` cvs-commit at gcc dot gnu dot org
2005-01-29 15:46 ` pbrook at gcc dot gnu dot org
2005-01-29 15:47 ` pbrook at gcc dot gnu dot org
2005-01-29 15:47 ` pbrook at gcc dot gnu dot org
2005-01-30 14:41 ` pinskia at gcc dot gnu dot org
2005-02-13 0:20 ` pinskia at gcc dot gnu dot org
2005-04-10 8:36 ` cvs-commit at gcc dot gnu dot org
2005-04-10 8:39 ` tkoenig at gcc dot gnu dot org
2005-05-03 19:41 ` cvs-commit at gcc dot gnu dot org [this message]
2005-05-03 19:45 ` [Bug libfortran/19595] [4.0 only] " tkoenig at gcc dot gnu dot org
2005-05-03 19:51 ` tkoenig at gcc dot gnu dot org
2005-05-03 19:51 ` tkoenig at gcc dot gnu dot org
2005-06-05 7:44 ` pinskia 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=20050503194014.7574.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).