[Bug libfortran/20661] End of record not detected

2005-04-10 Thread cvs-commit at gcc dot gnu dot org
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-04-10 08:36 --- Subject: Bug 20661 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-04-10 08:35:40 Modified files: libgfortran: ChangeLog libgfortran/io :

[Bug libfortran/20661] End of record not detected

2005-04-10 Thread tkoenig at gcc dot gnu dot org
--- Additional Comments From tkoenig at gcc dot gnu dot org 2005-04-10 08:44 --- Fixed in 4.1.0, waiting for 4.0 to reopen. -- What|Removed |Added Keywords|

[Bug libfortran/20661] End of record not detected

2005-04-01 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-04-01 13:34 --- This patch fixes the test case. It also includes my EOR patch for advancing I/O. This is regression-tested on mainline. I'll submit a proper patch when I have finished regression-testing it on 4.0.

[Bug libfortran/20661] End of record not detected

2005-03-29 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-29 15:11 --- I'll try and have a look. Hopefully, my copyright papers that I sent off on 2005-03-19 will come through sometime soon, because the end-of-record patch at

[Bug libfortran/20661] End of record not detected

2005-03-28 Thread tobi at gcc dot gnu dot org
--- Additional Comments From tobi at gcc dot gnu dot org 2005-03-28 17:48 --- To clarify this: ! End of record is not detected !on second READ ! iostats should be 0, 0, -2, -1 The standard says: Execution of an input/output statement containing the IOSTAT= specifier causes the

[Bug libfortran/20661] End of record not detected

2005-03-27 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-03-27 22:02 --- Confirmed. -- What|Removed |Added Status|UNCONFIRMED |NEW