This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch, libgfortran] PR60128 Wrong ouput using en edit descriptor
- From: dominiq at lps dot ens dot fr (Dominique Dhumieres)
- To: hp at bitrange dot com, dominiq at lps dot ens dot fr
- Cc: gcc-patches at gcc dot gnu dot org, fortran at gcc dot gnu dot org
- Date: Sat, 12 Apr 2014 11:10:27 +0200
- Subject: Re: [patch, libgfortran] PR60128 Wrong ouput using en edit descriptor
- Authentication-results: sourceware.org; auth=none
- References: <EE0CEC78-9D43-4997-A81A-8C2A931F8522 at lps dot ens dot fr> <alpine dot BSF dot 2 dot 02 dot 1404081513440 dot 23831 at arjuna dot pair dot com>
> 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?