[Bug fortran/38122] New: "file already opened in another unit" error when opening /dev/null or /dev/tty twice

2008-11-14 Thread steven dot chapel at sbcglobal dot net
ng /dev/null or /dev/tty twice Product: gcc Version: 4.3.2 Status: UNCONFIRMED Severity: minor Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: steven dot chapel at

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

2007-08-12 Thread steven dot chapel at sbcglobal dot net
--- Comment #27 from steven dot chapel at sbcglobal dot net 2007-08-12 23:23 --- (In reply to comment #26) > Which means it worked in g77 and not in gfortran. I don't know if it never worked in gfortran. Until a few days ago, the only MinGW build of gfortran was a trunk ve

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

2007-08-12 Thread steven dot chapel at sbcglobal dot net
--- Comment #25 from steven dot chapel at sbcglobal dot net 2007-08-12 22:45 --- > A regression with respect to what version of gfortran? A scan of the > audit trail did not reveal the working version. The code above works with gcc 3.4.5. > If the important applicatio

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

2007-08-11 Thread steven dot chapel at sbcglobal dot net
--- Comment #22 from steven dot chapel at sbcglobal dot net 2007-08-11 15:54 --- This is *not* an enhancement. It is a *regression* that causes an important application not to work. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32784

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

2007-07-17 Thread steven dot chapel at sbcglobal dot net
--- Comment #7 from steven dot chapel at sbcglobal dot net 2007-07-17 12:49 --- (In reply to comment #5) > if all its trying to do is WRITE to the console > use WRITE(unit=6) and don't give it a filename at all. > > Will this work for you? Not really. It's be

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

2007-07-16 Thread steven dot chapel at sbcglobal dot net
--- Comment #4 from steven dot chapel at sbcglobal dot net 2007-07-17 02:52 --- What name should I change 'con' to so that the write statement writes to the console? I asked on the gfortran mailing list, and I was told to submit this bug report. If it's as simple as ch

[Bug fortran/32784] New: Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

2007-07-16 Thread steven dot chapel at sbcglobal dot net
error: File 'con' does not exist Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: major Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: steven dot chapel at sbcglobal dot net http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32784