public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven dot chapel at sbcglobal dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/32784] New: Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist Date: Mon, 16 Jul 2007 21:32:00 -0000 [thread overview] Message-ID: <bug-32784-14861@http.gcc.gnu.org/bugzilla/> (raw) When this program is compiled and run: character*72 fnint data fnint /'con'/ i=index(fnint,' '); open(unit=29,file=fnint(1:i-1),status='new') write(29,100) 100 format('1Hello, world!') end It generates this error message: At line 4 of file bug.for (unit = 29, file = '') Fortran runtime error: File 'con' does not exist The same error message is generated when status='new' is omitted. Here is the info for the compiler I used (it's FX's prebuilt mingw binary): Using built-in specs. Target: i386-pc-mingw32 Configured with: ../trunk/configure --prefix=/mingw --enable-languages=c,fortran --with-gmp=/home/coudert/local --disable-nls --with-ld=/mingw/bin/ld --with-as= /mingw/bin/as --disable-werror --enable-bootstrap --enable-threads --build=i386- pc-mingw32 --disable-shared --enable-libgomp Thread model: win32 gcc version 4.3.0 20070706 (experimental) I am not able to run NONMEM <http://c255.ucsf.edu/nonmem1.html> built with gfortran because of this bug. -- Summary: Using 'con' as assigned file generates Fortran runtime 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
next reply other threads:[~2007-07-16 21:32 UTC|newest] Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-16 21:32 steven dot chapel at sbcglobal dot net [this message] 2007-07-16 22:15 ` [Bug libfortran/32784] [win32] " pinskia at gcc dot gnu dot org 2007-07-17 2:25 ` jvdelisle at gcc dot gnu dot org 2007-07-17 2:37 ` pinskia at gcc dot gnu dot org 2007-07-17 2:52 ` steven dot chapel at sbcglobal dot net 2007-07-17 4:38 ` jvdelisle at gcc dot gnu dot org 2007-07-17 8:44 ` dannysmith at users dot sourceforge dot net 2007-07-17 12:50 ` steven dot chapel at sbcglobal dot net 2007-07-18 2:54 ` jvdelisle at gcc dot gnu dot org 2007-07-21 19:39 ` jvdelisle at gcc dot gnu dot org 2007-07-21 23:08 ` jvdelisle at gcc dot gnu dot org 2007-07-22 8:42 ` dannysmith at users dot sourceforge dot net 2007-07-22 14:21 ` jvdelisle at gcc dot gnu dot org 2007-07-23 2:59 ` jvdelisle at gcc dot gnu dot org 2007-07-23 4:41 ` jvdelisle at gcc dot gnu dot org 2007-07-23 4:44 ` dannysmith at users dot sourceforge dot net 2007-07-23 5:46 ` jvdelisle at gcc dot gnu dot org 2007-07-23 8:04 ` dannysmith at users dot sourceforge dot net 2007-07-25 23:01 ` jvdelisle at gcc dot gnu dot org 2007-07-25 23:35 ` jvdelisle at gcc dot gnu dot org 2007-07-26 0:35 ` dannysmith at users dot sourceforge dot net 2007-08-11 15:38 ` jvdelisle at gcc dot gnu dot org 2007-08-11 15:54 ` steven dot chapel at sbcglobal dot net 2007-08-11 16:11 ` kargl at gcc dot gnu dot org 2007-08-11 17:49 ` jvdelisle at gcc dot gnu dot org 2007-08-12 22:46 ` steven dot chapel at sbcglobal dot net 2007-08-12 23:07 ` Andrew Pinski 2007-08-12 23:08 ` pinskia at gmail dot com 2007-08-12 23:24 ` steven dot chapel at sbcglobal dot net 2008-11-17 15:02 ` [Bug libfortran/32784] [win32] Using 'CONOUT$', 'CONIN$', or 'CONERR$' as assigned file generates Fortran runtime error: Bad file descriptor steve dot chapel at a2pg dot com 2008-11-18 3:03 ` jvdelisle at gcc dot gnu dot org 2008-11-18 13:00 ` steve dot chapel at a2pg dot com 2009-04-11 16:45 ` jvdelisle at gcc dot gnu dot org 2009-06-04 12:54 ` steven at gcc dot gnu dot org 2009-06-14 0:59 ` jvdelisle at gcc dot gnu dot org 2009-07-19 13:43 ` jvdelisle at gcc dot gnu dot org 2009-07-23 0:59 ` jvdelisle at gcc dot gnu dot org 2009-08-14 21:10 ` jvdelisle at gcc dot gnu dot org 2009-08-15 0:50 ` jvdelisle at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-32784-14861@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).