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/29568] implement unformatted files with subrecords (Intel style)
Date: Wed, 29 Nov 2006 03:58:00 -0000 [thread overview]
Message-ID: <20061129035755.12186.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29568-10391@http.gcc.gnu.org/bugzilla/>
------- Comment #27 from jvdelisle at gcc dot gnu dot org 2006-11-29 03:57 -------
Created an attachment (id=12704)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12704&action=view)
Huge+ record size unformatted write then read test
This test program exercizes patch 10 with very large record sizes. The program
executes correctly (except the recl value printed, noted elsewhere) on
x86-64-linux-gnu.
The program fails on x86-64-freebsd and never completes the first write. It
just keeps going, and going, and going .... This is a target specific issue.
My guess is that it has to do with alignment or types. Maybe mixed type
arithmetic, size_t vs gfc_offset. Is size_t 32 bits on freebsd and gfc_offset
64? I will attempt to change all new variables to gfc_offset and see if that
fixes it.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29568
next prev parent reply other threads:[~2006-11-29 3:58 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 18:17 [Bug libfortran/29568] New: " tkoenig at gcc dot gnu dot org
2006-10-23 19:49 ` [Bug libfortran/29568] " kargl at gcc dot gnu dot org
2006-10-25 20:11 ` tkoenig at gcc dot gnu dot org
2006-10-31 21:37 ` tobias dot burnus at physik dot fu-berlin dot de
2006-11-04 14:28 ` jb at gcc dot gnu dot org
2006-11-05 21:48 ` tkoenig at gcc dot gnu dot org
2006-11-09 20:43 ` tkoenig at gcc dot gnu dot org
2006-11-13 19:11 ` tkoenig at gcc dot gnu dot org
2006-11-15 21:05 ` tkoenig at gcc dot gnu dot org
2006-11-19 20:42 ` tkoenig at gcc dot gnu dot org
2006-11-21 2:49 ` jvdelisle at gcc dot gnu dot org
2006-11-21 2:52 ` jvdelisle at gcc dot gnu dot org
2006-11-21 4:02 ` jvdelisle at gcc dot gnu dot org
2006-11-21 6:48 ` jvdelisle at gcc dot gnu dot org
2006-11-21 7:16 ` jvdelisle at gcc dot gnu dot org
2006-11-21 7:24 ` jvdelisle at gcc dot gnu dot org
2006-11-21 8:25 ` jvdelisle at gcc dot gnu dot org
2006-11-21 20:40 ` tkoenig at gcc dot gnu dot org
2006-11-22 1:36 ` jvdelisle at gcc dot gnu dot org
2006-11-22 1:56 ` jvdelisle at gcc dot gnu dot org
2006-11-25 22:59 ` tkoenig at gcc dot gnu dot org
2006-11-26 4:10 ` jvdelisle at gcc dot gnu dot org
2006-11-26 20:40 ` tkoenig at gcc dot gnu dot org
2006-11-26 20:43 ` tkoenig at gcc dot gnu dot org
2006-11-26 22:27 ` jvdelisle at verizon dot net
2006-11-27 8:24 ` jvdelisle at gcc dot gnu dot org
2006-11-27 20:43 ` tkoenig at gcc dot gnu dot org
2006-11-29 3:58 ` jvdelisle at gcc dot gnu dot org [this message]
2006-11-29 22:13 ` tkoenig at gcc dot gnu dot org
2006-11-30 3:32 ` jvdelisle at gcc dot gnu dot org
2006-11-30 6:25 ` jvdelisle at gcc dot gnu dot org
2006-11-30 20:10 ` patchapp at dberlin dot org
2006-12-01 21:05 ` tkoenig at gcc dot gnu dot org
2006-12-01 21:18 ` tkoenig at gcc dot gnu dot org
2006-12-10 22:17 ` tkoenig at gcc dot gnu dot org
2006-12-10 23:05 ` tkoenig at gcc dot gnu dot org
2006-12-13 21:37 ` tkoenig at gcc dot gnu dot org
2006-12-19 17:15 ` burnus 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=20061129035755.12186.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).