[RFC PATCH] _gfortran_{ioparm,filename,line} vs. thread-safety

Thomas Koenig Thomas.Koenig@online.de
Thu Oct 6 22:32:00 GMT 2005


On Tue, Oct 04, 2005 at 06:52:34PM -0400, Jakub Jelinek wrote:
> The patch below already has the corresponding Fortran backend changes
> and even 100% passes make check-gfortran on x86_64-linux.
> What I wrote on Monday below still holds, but the further changes
> shouldn't hopefully impact library's ABI (except maybe for the size of
> the libgfortran's private area in st_parameter_dt).

If we go about changing the ABI anyway, should we also put in a way to
correctly read/write integer(kind=8) variables, so -fdefault-integer-8
can work (PR 21647)?

We also need integer(kind=8) variables for inquire(iolength=) for
>2 GB record sizes.  OK, so inquire(iolength) should probably
be implemented in the front end...

	Thomas



More information about the Fortran mailing list