public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/33985] access="stream",form="unformatted" doesn't buffer Date: Sat, 03 Nov 2007 01:18:00 -0000 [thread overview] Message-ID: <20071103011750.5755.qmail@sourceware.org> (raw) In-Reply-To: <bug-33985-10391@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from jvdelisle at gcc dot gnu dot org 2007-11-03 01:17 ------- I have discovered something that may make this easy to fix. -- jvdelisle at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |jvdelisle at gcc dot gnu dot |dot org |org Status|NEW |ASSIGNED Last reconfirmed|2007-11-02 22:43:14 |2007-11-03 01:17:50 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33985
next prev parent reply other threads:[~2007-11-03 1:18 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-11-02 22:18 [Bug libfortran/33985] New: " tkoenig at gcc dot gnu dot org 2007-11-02 22:43 ` [Bug libfortran/33985] " fxcoudert at gcc dot gnu dot org 2007-11-03 0:42 ` jvdelisle at gcc dot gnu dot org 2007-11-03 1:18 ` jvdelisle at gcc dot gnu dot org [this message] 2007-11-03 14:57 ` jvdelisle at gcc dot gnu dot org 2007-11-03 15:06 ` jvdelisle at gcc dot gnu dot org 2007-11-06 2:41 ` jvdelisle at gcc dot gnu dot org 2007-11-06 16:17 ` dominiq at lps dot ens dot fr 2007-11-06 23:39 ` jvdelisle at gcc dot gnu dot org 2007-11-07 2:44 ` jvdelisle at gcc dot gnu dot org 2007-11-14 1:22 ` jvdelisle at gcc dot gnu dot org 2007-11-30 22:28 ` tkoenig at gcc dot gnu dot org 2007-11-30 22:45 ` jvdelisle at gcc dot gnu dot org 2007-11-30 22:57 ` tkoenig at gcc dot gnu dot org 2007-11-30 23:55 ` jvdelisle at gcc dot gnu dot org 2007-12-01 4:22 ` jvdelisle at gcc dot gnu dot org 2007-12-01 4:28 ` howarth at nitro dot med dot uc dot edu 2007-12-01 4:34 ` jvdelisle at gcc dot gnu dot org 2007-12-01 7:34 ` kargl at gcc dot gnu dot org 2007-12-01 21:30 ` tkoenig at gcc dot gnu dot org 2007-12-01 21:50 ` howarth at nitro dot med dot uc dot edu 2007-12-01 21:53 ` tkoenig at gcc dot gnu dot org 2007-12-01 22:07 ` jvdelisle at gcc dot gnu dot org 2007-12-01 22:08 ` kargl at gcc dot gnu dot org 2007-12-01 22:19 ` tkoenig at gcc dot gnu dot org 2007-12-02 2:05 ` Jerry DeLisle 2007-12-02 2:05 ` jvdelisle at verizon dot net 2007-12-02 18:45 ` jvdelisle at gcc dot gnu dot org 2007-12-02 18:55 ` jvdelisle at gcc dot gnu dot org 2007-12-02 18:57 ` jvdelisle at gcc dot gnu dot org 2007-12-02 18:57 ` jvdelisle at gcc dot gnu dot org 2007-12-02 19:05 ` jvdelisle at gcc dot gnu dot org 2007-12-02 20:11 ` tkoenig at gcc dot gnu dot org 2007-12-02 20:58 ` jvdelisle at verizon dot net 2007-12-02 21:20 ` tkoenig at gcc dot gnu dot org 2007-12-02 23:17 ` jvdelisle at gcc dot gnu dot org 2007-12-02 23:32 ` 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=20071103011750.5755.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).