public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bdavis at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/19872] New: closed and re-opened file not overwriten Date: Thu, 10 Feb 2005 15:37:00 -0000 [thread overview] Message-ID: <20050210095616.19872.bdavis@gcc.gnu.org> (raw) program wtest implicit none open(1,file='wtest.out') write(1,'("1 2 3 4 5 6 7 8 9")') close(1) open(1,file='wtest.out') write(1,'("9 8 7 6")') close(1) end [bdavis@localhost gfortran]$ gfc a.f [bdavis@localhost gfortran]$ ./a.out [bdavis@localhost gfortran]$ cat wtest.out 9 8 7 6 1 2 3 4 5 6 7 8 9 [bdavis@localhost gfortran]$ g77 a.f [bdavis@localhost gfortran]$ ./a.out [bdavis@localhost gfortran]$ cat wtest.out 9 8 7 6 -- Summary: closed and re-opened file not overwriten Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libfortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: bdavis at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19872
next reply other threads:[~2005-02-10 9:56 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-02-10 15:37 bdavis at gcc dot gnu dot org [this message] 2005-02-20 15:19 ` [Bug libfortran/19872] " bdavis at gcc dot gnu dot org 2005-02-20 15:37 ` pinskia at gcc dot gnu dot org 2005-04-10 3:43 ` cvs-commit at gcc dot gnu dot org 2005-04-10 3:52 ` kargl at gcc dot gnu dot org 2005-04-10 9:37 ` [Bug libfortran/19872] [4.0 only] " tkoenig at gcc dot gnu dot org 2005-04-10 15:14 ` kargl at gcc dot gnu dot org 2005-04-16 22:03 ` pinskia at gcc dot gnu dot org 2005-05-21 20:34 ` tkoenig at gcc dot gnu dot org 2005-09-11 18:40 ` fxcoudert at gcc dot gnu dot org 2005-09-11 18:55 ` cvs-commit at gcc dot gnu dot org 2005-09-11 19:39 ` cvs-commit at gcc dot gnu dot org 2005-09-11 21:50 ` pinskia 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=20050210095616.19872.bdavis@gcc.gnu.org \ --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).