[Bug libfortran/24945] calling two open statements (same unit) without close fails
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|--- |4.1.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24945
[Bug libfortran/24945] calling two open statements (same unit) without close fails
--- Comment #7 from jb at gcc dot gnu dot org 2005-12-04 22:39 --- No problems have been reported with the patch, closing the bug as fixed. -- jb at gcc dot gnu dot org changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24945
[Bug libfortran/24945] calling two open statements (same unit) without close fails
--- Comment #3 from jb at gcc dot gnu dot org 2005-11-26 08:52 --- *** Bug 25036 has been marked as a duplicate of this bug. *** -- jb at gcc dot gnu dot org changed: What|Removed |Added CC||jb at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24945
[Bug libfortran/24945] calling two open statements (same unit) without close fails
--- Comment #4 from jb at gcc dot gnu dot org 2005-11-26 09:12 --- Subject: Bug 24945 Author: jb Date: Sat Nov 26 09:12:36 2005 New Revision: 107538 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=107538 Log: libgfortran ChangeLog: 2005-11-26 Janne Blomqvist [EMAIL PROTECTED] PR libgfortran/24945 * io/open.c (edit_modes): Check for STATUS_UNKNOWN flag. testsuite ChangeLog 2005-11-26 Janne Blomqvist [EMAIL PROTECTED] PR libgfortran/24945 * gfortran.dg/open_status_2.f90: New test. Added: trunk/gcc/testsuite/gfortran.dg/open_status_2.f90 Modified: trunk/gcc/testsuite/ChangeLog trunk/libgfortran/ChangeLog trunk/libgfortran/io/open.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24945
[Bug libfortran/24945] calling two open statements (same unit) without close fails
--- Comment #5 from jb at gcc dot gnu dot org 2005-11-26 09:27 --- Subject: Bug 24945 Author: jb Date: Sat Nov 26 09:27:22 2005 New Revision: 107539 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=107539 Log: libgfortran ChangeLog: 2005-11-26 Janne Blomqvist [EMAIL PROTECTED] PR libgfortran/24945 * io/open.c (edit_modes): Check for STATUS_UNKNOWN flag. testsuite ChangeLog 2005-11-26 Janne Blomqvist [EMAIL PROTECTED] PR libgfortran/24945 * gfortran.dg/open_status_2.f90: New test. Added: branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/open_status_2.f90 - copied, changed from r107538, trunk/gcc/testsuite/gfortran.dg/open_status_2.f90 Modified: branches/gcc-4_1-branch/gcc/testsuite/ChangeLog branches/gcc-4_1-branch/libgfortran/ChangeLog branches/gcc-4_1-branch/libgfortran/io/open.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24945
[Bug libfortran/24945] calling two open statements (same unit) without close fails
--- Comment #6 from jb at gcc dot gnu dot org 2005-11-26 09:32 --- Subject: Bug 24945 Author: jb Date: Sat Nov 26 09:32:21 2005 New Revision: 107540 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=107540 Log: testsuite ChangeLog: 2005-11-26 Janne Blomqvist [EMAIL PROTECTED] PR libgfortran/24945 * gfortran.dg/open_status_2.f90: Fix wrong PR number in comment. Modified: trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gfortran.dg/open_status_2.f90 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24945
[Bug libfortran/24945] calling two open statements (same unit) without close fails
--- Comment #1 from fxcoudert at gcc dot gnu dot org 2005-11-19 22:32 --- Confirmed (though I don't know why it should work and how it should behave). Intel accepts this too. -- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added CC||fxcoudert at gcc dot gnu dot ||org OtherBugsDependingO||19292 nThis|| Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|-00-00 00:00:00 |2005-11-19 22:32:17 date|| Version|unknown |4.2.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24945
[Bug libfortran/24945] calling two open statements (same unit) without close fails
--- Comment #2 from kargl at gcc dot gnu dot org 2005-11-20 01:16 --- See 9.3.4 from the standard. If a unit is connected to a file that exists, execution of an OPEN statement for that unit is permitted. If the FILE= specifier is not included in such an OPEN statement, the file to be connected to the unit is the same as the file to which the unit is already connected. If the file to be connected to the unit does not exist but is the same as the file to which the unit is preconnected, the properties specified by an OPEN statement become a part of the connection. If the file to be connected to the unit is not the same as the file to which the unit is connected, the effect is as if a CLOSE statement without a STATUS= specifier had been executed for the unit immediately prior to th execution of an OPEN statement. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24945
