On Tue, Jun 16, 2026 at 5:44 AM Haochen Jiang <[email protected]> wrote: > > On Linux/x86_64, > > 7659926b80deaf0523d9ccee51446b4187f978cb is the first bad commit > commit 7659926b80deaf0523d9ccee51446b4187f978cb > Author: Avinash Jayakar <[email protected]> > Date: Wed Jun 10 12:46:50 2026 +0530 > > match.pd: Recognize integer spaceship operator patterns > > caused > > FAIL: gcc.dg/spaceship_mixed_variants.c scan-tree-dump-times optimized > "\\.SPACESHIP \\([^,]+, [^,]+, -1\\)" 64 > > with GCC configured with > > ../../gcc/configure > --prefix=/export/users3/haochenj/src/gcc-bisect/master/master/r17-1582/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/spaceship_mixed_variants.c > --target_board='unix{-m32}'" > $ cd {build_dir}/gcc && make check > RUNTESTFLAGS="dg.exp=gcc.dg/spaceship_mixed_variants.c > --target_board='unix{-m32\ -march=cascadelake}'"
I see what I missed in the review here; spaceship_mixed_variants.c will fail for ilp32 targets. And maybe for int16 targets. We should split up spaceship_mixed_variants.c into a part that does not have `long long` in it and one which has `long long` in it. and run the `long long` part only for !ilp32 && !int16 targets. That would fix the issue here. Thanks, Andrea > > (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.)
