public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libfortran/29568]  New: implement unformatted files with subrecords (Intel style)
@ 2006-10-23 18:17 tkoenig at gcc dot gnu dot org
  2006-10-23 19:49 ` [Bug libfortran/29568] " kargl at gcc dot gnu dot org
                   ` (36 more replies)
  0 siblings, 37 replies; 38+ messages in thread
From: tkoenig at gcc dot gnu dot org @ 2006-10-23 18:17 UTC (permalink / raw)
  To: gcc-bugs

There's an on-off discussion on the gfortran mailing
list on making 4-byte record markers the default for gfortran.
This would only be acceptable if large (>2 GB) records could
be written that way.

I'm taking a shot at this.


-- 
           Summary: implement unformatted files with subrecords (Intel
                    style)
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: libfortran
        AssignedTo: tkoenig at gcc dot gnu dot org
        ReportedBy: tkoenig at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29568


^ permalink raw reply	[flat|nested] 38+ messages in thread

end of thread, other threads:[~2006-12-19 17:15 UTC | newest]

Thread overview: 38+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-10-23 18:17 [Bug libfortran/29568] New: implement unformatted files with subrecords (Intel style) 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
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

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).