------- Comment #4 from fxcoudert at gcc dot gnu dot org 2007-04-18 06:45
-------
(In reply to comment #3)
> Gfortran behavior matches ifort. It would be interesting to see what other
> compilers do.
Sun does the same as gfortran and Intel.
> I have not checked gfortran 4.2 yet. However, reviewing the code in
> transfer.c
> (read_block_direct) I suspect 4.2 is OK.
I tested gfortran-4.2 and it has the same behavior as gfortran-mainline. 4.1.2
gives different results, however. I'm adding the outputs of different version
as an attached tar file.
> I think the fix we have now in 4.2 and 4.3 (or similar) should be backported
> to
> the 4.1 branch.
Keeping this open.
--
fxcoudert at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[4.1 4.2 regression] |[4.1 only, regression]
|Reading after |Reading after
|ERROR_SHORT_RECORD |ERROR_SHORT_RECORD
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31409
