public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Thomas dot Koenig at online dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/19052] New: unit 0 not preconnected to standard error Date: Fri, 17 Dec 2004 09:05:00 -0000 [thread overview] Message-ID: <20041217090529.19052.Thomas.Koenig@online.de> (raw) This is different from g77 (and to all Unix fortran compilers that I know of). $ cat unit_0.f write (0,*) "hello" end $ rm -f fort.0 $ gfortran unit_0.f $ ./a.out $ cat fort.0 hello $ rm -f fort.0 $ g77 unit_0.f $ ./a.out hello $ cat fort.0 cat: fort.0: No such file or directory -- Summary: unit 0 not preconnected to standard error Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: libfortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: Thomas dot Koenig at online dot de CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19052
next reply other threads:[~2004-12-17 9:05 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-12-17 9:05 Thomas dot Koenig at online dot de [this message] 2004-12-17 9:05 ` [Bug libfortran/19052] " Thomas dot Koenig at online dot de 2004-12-17 12:40 ` pinskia at gcc dot gnu dot org 2005-01-06 14:43 ` tobi at gcc dot gnu dot org 2005-01-23 0:16 ` cvs-commit at gcc dot gnu dot org 2005-01-23 0:24 ` dje at gcc dot gnu dot org 2005-01-23 0:26 ` dje 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=20041217090529.19052.Thomas.Koenig@online.de \ --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).