[r15-7894 Regression] FAIL: gcc.dg/Wreturn-mismatch-6.c (test for warnings, line 40) on Linux/x86_64

[haochen.jiang]

On Linux/x86_64,

cf65235e03d2eb1667624943eae8f7fc355bceaf is the first bad commit
commit cf65235e03d2eb1667624943eae8f7fc355bceaf
Author: Andrew Pinski <quic_apinski@quicinc.com>
Date:   Thu Mar 6 16:07:02 2025 -0800

    c: Fix warning after an error on a return statment [PR60440]

caused

FAIL: gcc.dg/Wreturn-mismatch-2a.c  (test for warnings, line 40)
FAIL: gcc.dg/Wreturn-mismatch-6.c  (test for warnings, line 40)

with GCC configured with

../../gcc/configure --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r15-7894/usr --enable-clocale=gnu --with-system-zlib --with-demangler-in-ld --with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl --enable-libmpx x86_64-linux --disable-bootstrap

To reproduce:

$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-2a.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-2a.c --target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-2a.c --target_board='unix{-m64}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-2a.c --target_board='unix{-m64\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-6.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-6.c --target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-6.c --target_board='unix{-m64}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-6.c --target_board='unix{-m64\ -march=cascadelake}'"

(Please do not reply to this email, for question about this report, contact me at haochen dot jiang at intel.com.)
(If you met problems with cascadelake related, disabling AVX512F in command line might save that.)
(However, please make sure that there is no potential problems with AVX512.)