[Bug libfortran/19478] reading back from /dev/null

2005-05-11 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-11 11:18 --- Fixed. -- What|Removed |Added Status|NEW |RESOLVED

[Bug libfortran/19478] reading back from /dev/null

2005-05-11 Thread cvs-commit at gcc dot gnu dot org
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-05-11 10:39 --- Subject: Bug 19478 CVSROOT:/cvs/gcc Module name:gcc Branch: gcc-4_0-branch Changes by: [EMAIL PROTECTED] 2005-05-11 10:39:49 Modified files: gcc/testsuite : Change

[Bug libfortran/19478] reading back from /dev/null

2005-05-11 Thread cvs-commit at gcc dot gnu dot org
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-05-11 10:34 --- Subject: Bug 19478 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-05-11 10:34:06 Modified files: gcc/testsuite : ChangeLog libgfortran: C

[Bug libfortran/19478] reading back from /dev/null

2005-01-30 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-30 15:30 --- Confirmed. -- What|Removed |Added Status|UNCONFIRMED |NEW E

[Bug libfortran/19478] reading back from /dev/null

2005-01-30 Thread bdavis at gcc dot gnu dot org
--- Additional Comments From bdavis at gcc dot gnu dot org 2005-01-30 15:24 --- proposed patch: http://gcc.gnu.org/ml/fortran/2005-01/msg00329.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19478

[Bug libfortran/19478] reading back from /dev/null

2005-01-25 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-01-25 21:09 --- This may be legal according to the Fortran standard (which knows nothing about /dev/null), but it 1. breaks /dev/null semantics 2. viloates the principle of least surprise 3. is different from g77 4.

[Bug libfortran/19478] reading back from /dev/null

2005-01-25 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-01-25 10:37 --- I do not believe this to be a bug: An end-of-file condition occurs when no more records exist in a file during a sequential read, or when an end-of-file record produced by the ENDFILE statement is encounter