spawn -ignore SIGHUP /home/dave/gnu/gcc/objdir/gcc/xgcc -B/home/dave/gnu/gcc/obj dir/gcc/ /home/dave/gnu/gcc/gcc/gcc/testsuite/gcc.dg/torture/pr113026-1.c -fdiag nostics-plain-output -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions -Wall -S -o pr113026-1.s /home/dave/gnu/gcc/gcc/gcc/testsuite/gcc.dg/torture/pr113026-1.c: In function 'foo': /home/dave/gnu/gcc/gcc/gcc/testsuite/gcc.dg/torture/pr113026-1.c:10:12: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=] /home/dave/gnu/gcc/gcc/gcc/testsuite/gcc.dg/torture/pr113026-1.c:4:6: note: at offset 16 into destination object 'dst' of size 16 FAIL: gcc.dg/torture/pr113026-1.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for bogus messages, line 10) PASS: gcc.dg/torture/pr113026-1.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors) Only occurs at -O3.
I also see this on 32-bit Solaris/SPARC. There are testresult reports for a couple of other targets, too. This seems to be at -O3 -fomit-frame-pointer only, not plain -O3.
GCC 14.1 is being released, retargeting bugs to GCC 14.2.
FWIW, I've now found that on sparc-sun-solaris2.11 (32-bit only) the warning occurs as far back as gcc 10 with just gcc -O3 -ftracer Back in gcc 10, it would happen for both -m32 and -m64, while from gcc 11 onward, it's for -m32 only.