[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 application is that

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

2007-08-12 Thread Andrew Pinski
On 12 Aug 2007 22:45:07 -, steven dot chapel at sbcglobal dot net [EMAIL PROTECTED] wrote: The code above works with gcc 3.4.5. Which means it worked in g77 and not in gfortran (which is new for 4.0.0). Now we have this weird thing about how gfortran is a new front-end and g77 was removed.

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

2007-08-12 Thread pinskia at gmail dot com
--- Comment #26 from pinskia at gmail dot com 2007-08-12 23:07 --- Subject: Re: [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist On 12 Aug 2007 22:45:07 -, steven dot chapel at sbcglobal dot net [EMAIL PROTECTED] wrote: The code

[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 version of

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

2007-08-11 Thread jvdelisle at gcc dot gnu dot org
--- Comment #21 from jvdelisle at gcc dot gnu dot org 2007-08-11 15:38 --- Changing to enhancement. STANDARD I/O works fine. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[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-08-11 Thread kargl at gcc dot gnu dot org
--- Comment #23 from kargl at gcc dot gnu dot org 2007-08-11 16:11 --- (In reply to comment #22) This is *not* an enhancement. It is a *regression* that causes an important application not to work. A regression with respect to what version of gfortran? A scan of the audit trail

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

2007-08-11 Thread jvdelisle at gcc dot gnu dot org
--- Comment #24 from jvdelisle at gcc dot gnu dot org 2007-08-11 17:49 --- Sorry for the spin up here. I have a patch ready, still trying to test. -- 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-25 Thread jvdelisle at gcc dot gnu dot org
--- Comment #18 from jvdelisle at gcc dot gnu dot org 2007-07-25 23:00 --- More info for everyone. Under Cygwin, reading and writing from/to /dev/conin$ and /dev/conout$ respectively works fine with gfortran now. (Thanks David Korn for info) I think this is sufficient for Cygwin.

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

2007-07-25 Thread jvdelisle at gcc dot gnu dot org
--- Comment #19 from jvdelisle at gcc dot gnu dot org 2007-07-25 23:35 --- Regarding my comment #18 on cygwin. There should be no dollar signs in the device name. Thus: /dev/conout and /dev/conin -- 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-25 Thread dannysmith at users dot sourceforge dot net
--- 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

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

2007-07-23 Thread dannysmith at users dot sourceforge dot net
--- Comment #17 from dannysmith at users dot sourceforge dot net 2007-07-23 08:04 --- (In reply to comment #16) Maybe we should make it match con with case ignored. No, please. con, nul, prn (with or without suffix) are reserved device names on windows. (eg gcc -v -dM -E nul.c

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

2007-07-22 Thread dannysmith at users dot sourceforge dot net
--- Comment #11 from dannysmith at users dot sourceforge dot net 2007-07-22 08:42 --- (In reply to comment #10) Here is a complete patch, tested on Cygwin. I need to test on mingw. Can anyone help with that? open(unit=29,file='CONOUT$') write(29,100) 100

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

2007-07-22 Thread jvdelisle at gcc dot gnu dot org
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2007-07-22 14:21 --- Yes, I found similar on Cygwin, so I am still at it on this one. -- 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-22 Thread jvdelisle at gcc dot gnu dot org
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2007-07-23 02:59 --- Created an attachment (id=13950) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13950action=view) Patch to provide conio support Danny, can you please check this new patch. Works on Cygwin as far as I can

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

2007-07-22 Thread jvdelisle at gcc dot gnu dot org
--- Comment #14 from jvdelisle at gcc dot gnu dot org 2007-07-23 04:41 --- Created an attachment (id=13951) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13951action=view) Update patch This one does not fail when there is no filename, :) --

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

2007-07-22 Thread dannysmith at users dot sourceforge dot net
--- Comment #15 from dannysmith at users dot sourceforge dot net 2007-07-23 04:44 --- (In reply to comment #13) Created an attachment (id=13950) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13950action=view) [edit] Patch to provide conio support Danny, can you please check

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

2007-07-22 Thread jvdelisle at gcc dot gnu dot org
--- Comment #16 from jvdelisle at gcc dot gnu dot org 2007-07-23 05:46 --- I tried my latest updated patch in DOS terminal window as you suggested and it works OK, provided the file name is CONOUT$. If it is con or CON, I get an error of file already exists. I will think about that

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

2007-07-21 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2007-07-21 19:39 --- The following simple patch enables gfortran to run for the tet case. I need to get the proper #ifdef #endif condition set up and do a similar thing for CONIN$ and CONERR$ ( or whatever the windows equivalents

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

2007-07-21 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2007-07-21 23:08 --- Here is a complete patch, tested on Cygwin. I need to test on mingw. Can anyone help with that? Index: unix.c === --- unix.c (revision

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

2007-07-17 Thread dannysmith at users dot sourceforge dot net
--- Comment #6 from dannysmith at users dot sourceforge dot net 2007-07-17 08:43 --- (In reply to comment #4) What name should I change 'con' to so that the write statement writes to the console? I think it should be CONOUT$ (ie you had it right the first time). The following works

[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 been written that way so that

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

2007-07-17 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2007-07-18 02:54 --- I can't get anything to work, but I have some ideas. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

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

2007-07-16 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-07-16 22:15 --- This is a windows only issue as using special files (device files) under GNU/Linux works just fine. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added

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

2007-07-16 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2007-07-17 02:25 --- Under Cygwin we get: $ ./a.exe At line 4 of file test.f90 (unit = 29, file = '') Fortran runtime error: File 'con' already exists con is a reserved device name from MS DOS: See

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

2007-07-16 Thread pinskia at gcc dot gnu dot org
--- Comment #3 from pinskia at gcc dot gnu dot org 2007-07-17 02:37 --- Except con should be the console aka /dev/pts/?? . -- 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-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 changing the name,

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

2007-07-16 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2007-07-17 04:38 --- I will investigate further, but if all its trying to do is WRITE to the console use WRITE(unit=6) and don't give it a filename at all. You don't even need to OPEN it. It will be OPENed implicitly for you. READ