Article View: gnu.misc.discuss
Article #2270Re: Q: Fortran unformatted i/o with GNU f2c/gcc problem.
From: Toon Moene
Date: Fri, 02 Oct 1998 00:00
Date: Fri, 02 Oct 1998 00:00
21 lines
1523 bytes
1523 bytes
Raymond Toy <toy@rtp.ericsson.se> wrote: > >>>>> "Chris" == Chris Metzler <metzler@oddjob.uchicago.edu> writes: > Chris> Anyway, thanks for cluing me in re: unformatted file strucutre. > There is one more option, but that would probably require a fair > number of changes to you code. Use unformatted, random access files. > Most compilers that I've used support this, and they produce exactly > the data: no record separators or anything---just exactly what you > said to write. Indeed, and it even works for g77 (tried it down to a - four byte - integer). However, this is woefully expensive in (CPU|I/O) time. -- Toon Moene (mailto:toon@moene.indiv.nluug.nl) Saturnushof 14, 3738 XG Maartensdijk, The Netherlands Phone: +31 346 214290; Fax: +31 346 214286 g77 Support: mailto:fortran@gnu.org; egcs: mailto:egcs-bugs@cygnus.com
Technical Details
Message-ID:
<6v35k2$9br$1@newnews.nl.uu.net>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<F02psK.Apn@midway.uchicago.edu> <lpaF02tvI.5Aw@netcom.com> <F041A8.Ix@midway.uchicago.edu> <4nn27evqdk.fsf@rtp.ericsson.se>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 11318c,e0781954572e0423 X-Google-Attributes: gid11318c,public X-Google-Thread: 1025b4,e0781954572e0423 X-Google-Attributes: gid1025b4,public From: Toon Moene <toon@moene.indiv.nluug.nl> Subject: Re: Q: Fortran unformatted i/o with GNU f2c/gcc problem. Date: 1998/10/02 Message-ID: <6v35k2$9br$1@newnews.nl.uu.net> X-Deja-AN: 397119009 References: <F02psK.Apn@midway.uchicago.edu> <lpaF02tvI.5Aw@netcom.com> <F041A8.Ix@midway.uchicago.edu> <4nn27evqdk.fsf@rtp.ericsson.se> Organization: Moene Computational Physics, Maartensdijk, The Netherlands Newsgroups: gnu.misc.discuss,gnu.gcc.help