public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/35063] [Regression wrt g77] I/O leaks handles/memory on Windows XP Date: Sat, 09 Feb 2008 21:50:00 -0000 [thread overview] Message-ID: <20080209214927.24228.qmail@sourceware.org> (raw) In-Reply-To: <bug-35063-12481@http.gcc.gnu.org/bugzilla/> ------- Comment #33 from tkoenig at gcc dot gnu dot org 2008-02-09 21:49 ------- We should fix this in 4.3.0 (and it's a regression, too). -- tkoenig at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |4.3.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063
next prev parent reply other threads:[~2008-02-09 21:50 UTC|newest] Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-03 13:25 [Bug fortran/35063] New: write statement leaks handles/memory on windows xp mikko dot lyly at csc dot fi 2008-02-03 14:38 ` [Bug fortran/35063] " jpr at csc dot fi 2008-02-03 17:36 ` jvdelisle at gcc dot gnu dot org 2008-02-04 4:36 ` [Bug libfortran/35063] " jvdelisle at gcc dot gnu dot org 2008-02-04 7:18 ` tkoenig at gcc dot gnu dot org 2008-02-04 21:06 ` jvdelisle at gcc dot gnu dot org 2008-02-04 23:41 ` fxcoudert at gcc dot gnu dot org 2008-02-05 10:56 ` [Bug libfortran/35063] I/O leaks handles/memory on Windows XP fxcoudert at gcc dot gnu dot org 2008-02-06 1:27 ` jvdelisle at gcc dot gnu dot org 2008-02-06 11:32 ` jpr at csc dot fi 2008-02-06 20:26 ` Jerry_V_DeLisle at rl dot gov 2008-02-06 20:55 ` jpr at csc dot fi 2008-02-06 21:50 ` tkoenig at gcc dot gnu dot org 2008-02-07 5:07 ` jpr at csc dot fi 2008-02-07 6:07 ` [Bug libfortran/35063] [Regression wrt g77] " jvdelisle at gcc dot gnu dot org 2008-02-07 6:27 ` kargl at gcc dot gnu dot org 2008-02-07 9:20 ` jpr at csc dot fi 2008-02-07 15:01 ` jvdelisle at gcc dot gnu dot org 2008-02-07 15:21 ` fxcoudert at gcc dot gnu dot org 2008-02-07 15:55 ` Jerry_V_DeLisle at rl dot gov 2008-02-07 21:17 ` brian at dessent dot net 2008-02-08 3:14 ` jvdelisle at gcc dot gnu dot org 2008-02-08 5:29 ` jpr at csc dot fi 2008-02-08 8:59 ` fxcoudert at gcc dot gnu dot org 2008-02-08 12:13 ` jpr at csc dot fi 2008-02-08 14:27 ` jvdelisle at gcc dot gnu dot org 2008-02-08 14:40 ` fxcoudert at gcc dot gnu dot org 2008-02-08 14:59 ` jvdelisle at gcc dot gnu dot org 2008-02-08 16:34 ` jvdelisle at gcc dot gnu dot org 2008-02-08 18:10 ` jvdelisle at gcc dot gnu dot org 2008-02-08 22:32 ` mikko dot lyly at csc dot fi 2008-02-08 23:01 ` jvdelisle at verizon dot net 2008-02-09 6:47 ` jpr at csc dot fi 2008-02-09 21:50 ` tkoenig at gcc dot gnu dot org [this message] 2008-02-10 0:26 ` jvdelisle at gcc dot gnu dot org 2008-02-10 16:56 ` jb at gcc dot gnu dot org 2008-02-10 18:08 ` jvdelisle at gcc dot gnu dot org 2008-02-10 18:09 ` jvdelisle at gcc dot gnu dot org 2008-02-14 12:25 ` [Bug libfortran/35063] Clean up use of destroy_unit_mutex() fxcoudert at gcc dot gnu dot org 2008-02-23 16:41 ` jvdelisle at gcc dot gnu dot org 2008-02-23 18:47 ` jb at gcc dot gnu dot org 2008-02-25 20:47 ` jb at gcc dot gnu dot org 2008-03-01 10:55 ` jb at gcc dot gnu dot org 2008-03-01 12:24 ` fxcoudert at gcc dot gnu dot org 2008-03-01 17:15 ` 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=20080209214927.24228.qmail@sourceware.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).