This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: g77: read/write file access
- To: toon at moene dot indiv dot nluug dot nl
- Subject: Re: g77: read/write file access
- From: Eli Zaretskii <eliz at delorie dot com>
- Date: Tue, 9 Jan 2001 03:26:27 -0500 (EST)
- CC: henlich at mmers1 dot mw dot tu-dresden dot de, gcc-bugs at gcc dot gnu dot org
- References: <20010108165827.A5811@mmepc14.mw.tu-dresden.de> <3A5A3975.56095576@moene.indiv.nluug.nl>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> Date: Mon, 08 Jan 2001 23:04:37 +0100
> From: Toon Moene <toon@moene.indiv.nluug.nl>
>
> Thomas Henlich wrote:
>
> > I noticed the following bug in g77 (gcc-2.95,2, DOS/djgpp and Windows
> > NT/mingw32 ports):
>
> Hmmmm, it does work correctly for me, on Debian GNU/Linux 2.2 (potato):
[snip]
> toon@laptop:~/g77-bugs$ ./a.out
> toon@laptop:~/g77-bugs$ cat tst.txt
> one
> 2
>
> which makes it quite plausible that the connection between libg2c (the
> Fortran run-time library) and the underlying OS is not functioning
> correctly.
>
> (Un)fortunately, I do not have access to ports to MS OS's, so I cannot
> find out why this is the case.
>
> 1/2 :-)
I do have access to MS OS's, but don't have the Fortran compiler
installed to dig into this ;-)
If someone can tell what C library functions are called by this
Fortran program to read/write the file, and in what order, I can at
least hypothesize about possible reasons for the problem on non-Unix
systems, and maybe even run some simple C test programs to see what's
going on.