--- Comment #3 from fxcoudert at gcc dot gnu dot org 2006-10-22 07:15
---
(In reply to comment #1)
> - A compile-time-error is shown (probably fixed by FX patch, not checked)
Yes, it's fixed by my patch. Confirming this bug.
Tobias, if you want to submit a global patch to resolve thes
--- Comment #4 from patchapp at dberlin dot org 2006-10-26 08:27 ---
Subject: Bug number PR29452
A patch for this bug has been added to the patch tracker.
The mailing list url for the patch is
http://gcc.gnu.org/ml/gcc-patches/2006-10/msg01327.html
--
http://gcc.gnu.org/bugzilla/sh
--- Comment #5 from burnus at gcc dot gnu dot org 2006-10-30 14:17 ---
Subject: Bug 29452
Author: burnus
Date: Mon Oct 30 14:17:15 2006
New Revision: 118184
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=118184
Log:
fortran/
2006-10-26 Tobias Burnus <[EMAIL PROTECTED]>
--- Comment #6 from burnus at gcc dot gnu dot org 2006-10-30 14:19 ---
Accept bug
--
burnus at gcc dot gnu dot org changed:
What|Removed |Added
AssignedTo|unassig
--- Comment #7 from burnus at gcc dot gnu dot org 2006-10-30 14:21 ---
And mark as fixed.
Hopefully, we won't forget to add checks also to the following specifiers as
soon as we implement them.
WRITE/READ (some only in READ allowed; those are not yet implemented in
gfortran):
- ASYNCHR
--- Comment #1 from tobias dot burnus at physik dot fu-berlin dot de
2006-10-13 10:13 ---
Some tests show:
open(13,file='foo',form='format')
close(13,status='del')
compiles and runs in gfortran.
Expected:
- A run-time error is shown.
- A compile-time-error is shown (probably fixed
--- Comment #2 from tobias dot burnus at physik dot fu-berlin dot de
2006-10-17 15:31 ---
The library problems are due to an error in the string comparison; one only
compares the first (fortran string length) characters, but never checks whether
the strings are of identical length.
Pat
