public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp 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: Sun, 24 Feb 2008 20:15:00 -0000 [thread overview]
Message-ID: <20080224201444.1507.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35293-507@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from hp at gcc dot gnu dot org 2008-02-24 20:14 -------
(In reply to comment #1)
> Are you testing
> with a simulator on x86_64-unknown-linux-gnu? I am trying to understand the
> environment. :)
Hm, I thought I was clear enough with the bug report unambiguously indicating a
cross target, with the *-elf indicating and the message pointed to saying
"(remember, cris-elf is one of those challenged newlib simulator targets)" but
to wit: yes, your reading is correct. If there's a clearer way of saying it,
send patches.
For the pr35132.f90 attachment, abort is called and "hexdump -C foo.txt"
produces:
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000010 00 00 00 00 00 31 32 33 34 35 36 0a 61 62 63 64 |.....123456.abcd|
00000020 65 66 0a 71 77 65 72 74 79 0a |ef.qwerty.|
0000002a
(foo.txt will also be attached as-is for your enjoyment)
I'll work on a patch to unix.c:fd_truncate.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35293
next prev parent reply other threads:[~2008-02-24 20:15 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 [this message]
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
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=20080224201444.1507.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).