commit 4239dd963f74f7da402ea4de27397ceeec304508
author hp <hp@138bc75d-0d04-0410-961f-82ee72b054a4> Thu May 23 02:18:49 2019 +0000
committer hp <hp@138bc75d-0d04-0410-961f-82ee72b054a4> Thu May 23 02:18:49 2019 +0000
tree 4e44faad216ca6095e0d221045002e2661cfc1fa
parent 2593ab363444f9b69d97d1db122da8f87c7ee844

There was a regression for gfortran.dg/fmt_en.f90 for cris-elf
that on inspection was due to it having acquired a truncation
call through the runtime.  I updated that and the new tests that
had "Fortran runtime error: required ftruncate or chsize support
not present" messages in gfortran.log, ran past cris-elf and
committed as obvious.  See also
<https://gcc.gnu.org/ml/gcc-patches/2008-05/msg00975.html> from
which I copy-pasted most of this message.  (Yep, 11 years ago.)

gcc/testsuite:
	* gfortran.dg/dec_io_1.f90, gfortran.dg/dtio_1.f90,
	gfortran.dg/dtio_12.f90, gfortran.dg/fmt_en.f90,
	gfortran.dg/namelist_89.f90: Gate test on effective_target
	fd_truncate.


git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@271536 138bc75d-0d04-0410-961f-82ee72b054a4