This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist
- From: "dannysmith at users dot sourceforge dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 26 Jul 2007 00:34:22 -0000
- Subject: [Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist
- References: <bug-32784-14861@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #20 from dannysmith at users dot sourceforge dot net 2007-07-26 00:34 -------
(In reply to comment #18)
>
> Under mingw, gfortran has some trouble. I am still experimenting and testing
> on mingw which I just got installed on my test machine here. I should be able
> to finish this when I get the time free to do it.
>
For complete testing, I suppose you we need to test GUI progs where
stdout/stdin/stderr default to bitbuckets, A windows GUI prog is compiled with
"gcc/gfortran -mwindows ..."
IMO, this is not a critical bug, so don't fritter too much time on it.
'CONOUT$' etc are non-portable identifiers that should probably only be used
in w32api context.
Danny
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32784