Re: [r16-5897 Regression] FAIL: gcc.dg/torture/pr99782-1.c -Os (test for excess errors) on Linux/x86_64

On Fri, Dec 5, 2025 at 1:00 AM Haochen Jiang <[email protected]> wrote:
>
> On Linux/x86_64,
>
> e148a21f38327f7c0e1040bf28c676dd0d13ca38 is the first bad commit
> commit e148a21f38327f7c0e1040bf28c676dd0d13ca38
> Author: Andrew Pinski <[email protected]>
> Date:   Thu Oct 23 21:20:24 2025 -0700
>
>     x86/aarch64: Fix compile time hog with ccmp [PR99782]
>
> caused
>
> FAIL: gcc.dg/torture/pr99782-1.c   -O0  (test for excess errors)
> FAIL: gcc.dg/torture/pr99782-1.c   -O1  (test for excess errors)
> FAIL: gcc.dg/torture/pr99782-1.c   -O2 -flto -fno-use-linker-plugin -flto-partition=none  (test for excess errors)
> FAIL: gcc.dg/torture/pr99782-1.c   -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects  (test for excess errors)
> FAIL: gcc.dg/torture/pr99782-1.c   -O2  (test for excess errors)
> FAIL: gcc.dg/torture/pr99782-1.c   -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions  (test for excess errors)
> FAIL: gcc.dg/torture/pr99782-1.c   -O3 -g  (test for excess errors)
> FAIL: gcc.dg/torture/pr99782-1.c   -Os  (test for excess errors)

I will deal with this in the morning. The testcase just needs `{
target int128 }` on the dg-compile.

>
> with GCC configured with
>
> ../../gcc/configure --prefix=/export/users3/haochenj/src/gcc-bisect/master/master/r16-5897/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-torture.exp=gcc.dg/torture/pr99782-1.c --target_board='unix{-m32}'"
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg-torture.exp=gcc.dg/torture/pr99782-1.c --target_board='unix{-m32\ -march=cascadelake}'"
>
> (Please directly reply to this email for question about this report.)
> (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.)