> This test, after the update on 4.8 in r209070 when the test-case was
> modified substantially (not really covered by the ChangeLog entry) to be
> identical to that on trunk, apparently takes a different route in the
> fortran run-time library on 4.8 compared to trunk.  For 4.8, it requires
> more run-time support on the target system, trigging the tell-tale error
> message found in gfortran.log: "Fortran runtime error: required ftruncate
> or chsize support not present" on some targets, then aborting and flagged
> as a regression as it passed before that commit.  Committed to 4.8 as
> obvious.  Again, this is not required on trunk.

IMO this the change is far from obvious and defeats the purpose the changes 
in the test case which was to run the test on ALL targets.

I need to know what are the affected targets, what part of the test 
triggers the failure, and if it exists a work-around.

Cheers,

Dominique

PS I made a mistake in the SVN entry (it is correct in 
gcc/testsuite/ChangeLog). Is there a way to fix it?

Reply via email to