https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88920
--- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I don't see why this should be reopened. Many of the effective target procedures leave some output in the log files, that is completely normal. Why should this one be an exception? E.g. spawn -ignore SIGHUP /home/jakub/src/gcc/obj14/gcc/testsuite/g++3/../../xg++ -B/home/jakub/src/gcc/obj14/gcc/testsuite/g++3/../../ -fsanitize=address -g -I/home/jakub/src/gcc/gcc/testsuite/../../libsanitizer/include -fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers -fdiagnostics-color=never -nostdinc++ -I/home/jakub/src/gcc/obj14/x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu -I/home/jakub/src/gcc/obj14/x86_64-pc-linux-gnu/libstdc++-v3/include -I/home/jakub/src/gcc/libstdc++-v3/libsupc++ -I/home/jakub/src/gcc/libstdc++-v3/include/backward -I/home/jakub/src/gcc/libstdc++-v3/testsuite/util -fmessage-length=0 -c -o ilp3225692.o ilp3225692.c ilp3225692.c:4:35: error: narrowing conversion of '-1' from 'int' to 'long unsigned int' [-Wnarrowing] ilp3225692.c:4:27: error: size of array 'dummy' is negative compiler exited with status 1 from failed ilp32 test, many others.
