https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124656
--- Comment #7 from David Binderman <dcb314 at hotmail dot com> ---
(In reply to anlauf from comment #6)
> Thanks for the concise report and for confirming the patch!
You are welcome. Given the size and coverage of the Fujitsu
Fortran test suite compared to llvm and gcc, it looks a good thing
to do some testing with it.
I check for compile time errors. I use a variant of this
shell script:
FOR="~/gcc/results/bin/gfortran"
FORFLAGS="-g1 -O3 -march=native -Wall"
find ~/fujitsu/trunk/Fortran -type f -print | grep -iE
"\.f$|\.f[0-9][0-9]$|\.for$" | sort > file.f.list
wc -l file.f.list
for i in `cat file.f.list`
do
$FOR $FORFLAGS -c -o /dev/null $i
done
I only run it with UBSAN on x86_64 and ARM-32, but ASAN and
other architectures would be good.
I haven't got as far as testing the executables produced.
Just some ideas for improved testing.
