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/35293] [4.4 Regression] truncation errors with gfortran.dg/streamio_11.f90, 3, 4 and 15. Date: Tue, 26 Feb 2008 23:19:00 -0000 [thread overview] Message-ID: <20080226231904.21520.qmail@sourceware.org> (raw) In-Reply-To: <bug-35293-507@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from tkoenig at gcc dot gnu dot org 2008-02-26 23:19 ------- (In reply to comment #8) > > b) fail at runtime (noisily) and xfail the > > corresponding test cases > > *sigh* ok, I'll do it, except for the noise. Thanks a lot! You'll probably want to make the truncate a no-op if we are at the end of file already. IIRC, there may be a few places in the library where we call ftruncate() even if we don't really need to. > As I mentioned, there are a few > bugs there anyway, but nobody commented on that. We know :-( The alloc stream facility has quite a few bugs in unexpected places that tend to be exposed by seemingly harmless changes far away. It needs to be replaced someday, but so far nobody has made a start on this. This is PR 25561, dated 2005-12-25. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35293
next prev parent reply other threads:[~2008-02-26 23:19 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-22 7:52 [Bug libfortran/35293] New: " hp at gcc dot gnu dot org 2008-02-22 14:11 ` [Bug libfortran/35293] " jvdelisle at gcc dot gnu dot org 2008-02-22 14:20 ` jvdelisle at gcc dot gnu dot org 2008-02-24 20:15 ` hp at gcc dot gnu dot org 2008-02-24 20:18 ` hp at gcc dot gnu dot org 2008-02-24 20:26 ` hp at gcc dot gnu dot org 2008-02-24 20:50 ` jvdelisle at gcc dot gnu dot org 2008-02-26 21:45 ` tkoenig at gcc dot gnu dot org 2008-02-26 22:48 ` hp at gcc dot gnu dot org 2008-02-26 23:19 ` tkoenig at gcc dot gnu dot org [this message] 2008-02-26 23:38 ` hp at gcc dot gnu dot org 2008-03-04 18:12 ` hp at gcc dot gnu dot org 2008-03-05 1:52 ` hp at gcc dot gnu dot org 2008-03-05 1:56 ` hp at gcc dot gnu dot org 2008-03-05 1:59 ` hp 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=20080226231904.21520.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).