[r16-7456 Regression] FAIL: gcc.dg/vect/no-section-anchors-vect-64.c -flto -ffat-lto-objects scan-tree-dump-times vect "Vectorizing an unaligned access" 0 on Linux/x86_64
Haochen Jiang <[email protected]>
| Newsgroups | gmane.comp.gcc.patches,gmane.comp.gcc.regression |
|---|---|
| Message-ID | <[email protected]> |
On Linux/x86_64, 86c00670914f7383c8c1f920d376493459b7aafb is the first bad commit commit 86c00670914f7383c8c1f920d376493459b7aafb Author: Richard Biener <[email protected]> Date: Wed Feb 11 09:50:55 2026 +0100 Use dg-additional-options in vect.exp, simplify file globbing caused FAIL: gcc.dg/vect/no-section-anchors-vect-31.c -flto -ffat-lto-objects scan-tree-dump-times vect "Alignment of access forced using peeling" 2 FAIL: gcc.dg/vect/no-section-anchors-vect-31.c -flto -ffat-lto-objects scan-tree-dump-times vect "Vectorizing an unaligned access" 0 FAIL: gcc.dg/vect/no-section-anchors-vect-31.c scan-tree-dump-times vect "Alignment of access forced using peeling" 2 FAIL: gcc.dg/vect/no-section-anchors-vect-31.c scan-tree-dump-times vect "Vectorizing an unaligned access" 0 FAIL: gcc.dg/vect/no-section-anchors-vect-64.c -flto -ffat-lto-objects scan-tree-dump-times vect "Alignment of access forced using peeling" 2 FAIL: gcc.dg/vect/no-section-anchors-vect-64.c -flto -ffat-lto-objects scan-tree-dump-times vect "Vectorizing an unaligned access" 0 FAIL: gcc.dg/vect/no-section-anchors-vect-64.c scan-tree-dump-times vect "Alignment of access forced using peeling" 2 FAIL: gcc.dg/vect/no-section-anchors-vect-64.c scan-tree-dump-times vect "Vectorizing an unaligned access" 0 with GCC configured with ../../gcc/configure --prefix=/export/users3/haochenj/src/gcc-bisect/master/master/r16-7456/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="vect.exp=gcc.dg/vect/no-section-anchors-vect-31.c --target_board='unix{-m32\ -march=cascadelake}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="vect.exp=gcc.dg/vect/no-section-anchors-vect-31.c --target_board='unix{-m64\ -march=cascadelake}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="vect.exp=gcc.dg/vect/no-section-anchors-vect-64.c --target_board='unix{-m32\ -march=cascadelake}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="vect.exp=gcc.dg/vect/no-section-anchors-vect-64.c --target_board='unix{-m64\ -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.)