gfortran io
FX
fxcoudert@gmail.com
Fri Feb 1 18:18:00 GMT 2008
Hello,
> This bug seams to be still present (i.e wrong output for x=1.0 and x=7.0)
> with the latest gcc 2.2 snapshot ?
I take it you meant 4.2. I've checked and this bug is not present in
4.1.2, 4.2.2 or the current branch (to become 4.3.0) on linux. I have
also checked and it does not appear on mingw for 4.3.0. So, this is a
mingw-only, 4.2-only bug, is that correct?
> gcc version 4.2.3 20080123 (prerelease)
Are you building this snapshot yourself or
> It seams to be ok with the following gcc-4.3 ... but I cannot use
> gcc-4.3 which seams to give me crashes elsewhere in my program.
I'll be more than happy to help you find out the possible bugs in
gfortran-4.3 or the possible bugs in your code exposed by
gfortran-4.3, if you start down that path. As a side note: mingw
doesn't officially support gcc-4.x for any value of x smaller than 3.
> Can I expect this bug to be solved in the 4.2.3 version ?
No. The 4.2.3 release process has begun and the version should be
officialy released in the next 24 hours.
For a possible 4.2.4 fix, the rule is that we only fix regressions: if
that was working on the 4.1 branch, we can consider fixing it on a
later released branch. Otherwise, we would need a particularly
compelling reason.
> or is it possible to backport to gcc 4.2 the correction from gcc 4.3 ?
Do you have a PR number for this bug? Or does this ring a bell to
someone? I don't know who fixed that issue (nor if he did so
intentionally).
Regards,
François-Xavier
--
FX Coudert
http://www.homepages.ucl.ac.uk/~uccafco/
More information about the Fortran
mailing list