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 sbcglobal dot net
GCC build triplet: i386-redhat-linux
--- 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 application
--- 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 version
--- 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
--- 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 been written that way so
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
--- 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 changing the name
