This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/21570] Unformatted sequential read/write
- From: "blime at cox dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 15 May 2005 13:59:43 -0000
- Subject: [Bug fortran/21570] Unformatted sequential read/write
- References: <20050514160259.21570.blime@cox.net>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From blime at cox dot net 2005-05-15 13:59 -------
Subject: Re: Unformatted sequential read/write
Okay - Its 32 bit -- but sorry I don't understand portable (one computer
involved) or target? What I have been doing over
the last couple of months is testing the gfortran compiler on a large
simulation, and comparing results with those produced
by the same inputs and the program compiled with g77 (used for several
years). There are four modules involved and I
tested the use of the g77 binary output from the first module as input
for the second module compiled with gfortran.
Thus far he gfortran compiler has identified a couple of bugs - but I
could do a lot more testing if bug #20236 (T edit descriptor)
were fixed - the code uses this convention in many places, and it is no
small task to change to the X edit descriptor.
Thanks for responding.
blime
pinskia at gcc dot gnu dot org wrote:
>------- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-14 16:34 -------
>Is this with a 64bit target?
>
>I don't think we should consider this a bug because binary files are never portable between targets.
>
>
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21570