aboutsummaryrefslogtreecommitdiff
path: root/gcc/cse.c
diff options
context:
space:
mode:
authorHans-Peter Nilsson <hp@axis.com>2019-05-23 02:18:49 +0000
committerHans-Peter Nilsson <hp@gcc.gnu.org>2019-05-23 02:18:49 +0000
commit6dac25d1ee4644deaea053911f0f3da84fa8cb6d (patch)
tree4e44faad216ca6095e0d221045002e2661cfc1fa /gcc/cse.c
parent30d3ba5142311df568e8f62a374d83d0bdab42bf (diff)
downloadgcc-6dac25d1ee4644deaea053911f0f3da84fa8cb6d.zip
gcc-6dac25d1ee4644deaea053911f0f3da84fa8cb6d.tar.gz
gcc-6dac25d1ee4644deaea053911f0f3da84fa8cb6d.tar.bz2
There was a regression for gfortran.dg/fmt_en.f90 for cris-elf that on...
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. From-SVN: r271536
Diffstat (limited to 'gcc/cse.c')
0 files changed, 0 insertions, 0 deletions