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/29627] partial unformatted reads shouldn't succeed
Date: Sun, 29 Oct 2006 11:59:00 -0000 [thread overview]
Message-ID: <20061029115917.1569.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29627-10391@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from tkoenig at gcc dot gnu dot org 2006-10-29 11:59 -------
(In reply to comment #3)
Hi Jerry,
> Now
> that we are in 4.3 this is a good time to do some cleanup. Overall, the
> prelminary patch approach looks good, but I have not tested yet.
There's another reason why I want the cleanup: For implementing Intel
record markers (PR 29568). Interleaving stream and record I/O would
lead to so many if statements that I'd never get this right :-)
Thomas
--
tkoenig at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
OtherBugsDependingO| |29568
nThis| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29627
next prev parent reply other threads:[~2006-10-29 11:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-28 18:10 [Bug libfortran/29627] New: " tkoenig at gcc dot gnu dot org
2006-10-28 18:11 ` [Bug libfortran/29627] " tkoenig at gcc dot gnu dot org
2006-10-28 19:30 ` tkoenig at gcc dot gnu dot org
2006-10-28 21:24 ` tkoenig at gcc dot gnu dot org
2006-10-28 23:21 ` jvdelisle at gcc dot gnu dot org
2006-10-29 11:49 ` tkoenig at gcc dot gnu dot org
2006-10-29 11:59 ` tkoenig at gcc dot gnu dot org [this message]
2006-10-31 20:58 ` tkoenig at gcc dot gnu dot org
2006-11-01 10:17 ` [Bug libfortran/29627] [4.2/4.1 only] " tkoenig at gcc dot gnu dot org
2006-11-03 11:22 ` tkoenig at gcc dot gnu dot org
2006-11-03 11:30 ` [Bug libfortran/29627] [4.1 " tkoenig at gcc dot gnu dot org
2006-11-04 14:04 ` tkoenig at gcc dot gnu dot org
2006-11-04 14:05 ` tkoenig at gcc dot gnu dot org
2006-11-30 19:26 ` chaoyingfu 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=20061029115917.1569.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: link
Be 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).