This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [gfortran,patch] Fix PR libfortran/23262 (on mingw32)
- From: François-Xavier Coudert <fxcoudert at gmail dot com>
- To: Brooks Moses <bmoses at stanford dot edu>
- Cc: fortran at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Sun, 4 Sep 2005 09:40:31 +0200
- Subject: Re: [gfortran,patch] Fix PR libfortran/23262 (on mingw32)
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=EshK2dwl+VC2FAzkPX+fzIxOIfIEwMF0zLqXJqq48I2LM/BCYITZcFRE5wW+nJdVDpAwy47hPiXs9BAFC+1DaOxd6D8avKUK1dX6nqXOy1z3cN2088aFfRs/ItZhZo5yxn/qM+n6zlljFkXWjHHAObZMpA1zGC3xeBIjq7Bd1X0=
- References: <4319F791.9080000@gmail.com> <431A1248.2000602@stanford.edu> <431A92F5.4000201@gmail.com> <431A9AC2.6060000@stanford.edu>
- Reply-to: fxcoudert at gmail dot com
> it may not be appropriate to override the user option --
> because, if we do, a Cygwin user may not get the line ending type that
> they want.
I do agree with that. On the other hand, libgfortran is incompatible
with CRLF switch (that is, today, if a user specifies CRLF, gfortran
(indepedently of where it was compiled) will not work for him. Trivial
codes might appear to work, but any code using (for example) rewind or
sequential direct access will be broken (see PR 23262 and duplicates).
I see no way to have the Cygwin switch influence the behaviour of the
library. On the other hand, we could add a compiler switch, -fcrlf,
which would default to -fno-crlf on non-windows systems, to -fcrlf on
mingw and either (choice of the binaries maker) on cygwin.
How do people feel about that?
> I may have a chance to poke at this a bit and confirm some of this
> experimentally in the next couple of weeks; if I do, I'll report back.
Thanks. I'll hold the patch until more evidence comes in.
FX