[r16-531 Regression] FAIL: gcc.target/i386/vect-shiftv8qi.c scan-assembler-times psllw 2 on Linux/x86_64
"haochen.jiang via Gcc-regression" <[email protected]>
| Newsgroups | gmane.comp.gcc.regression,gmane.comp.gcc.patches |
|---|---|
| Message-ID | <[email protected]> |
On Linux/x86_64, 37e61c793c1b22bdcfbf142cd6086da2745be596 is the first bad commit commit 37e61c793c1b22bdcfbf142cd6086da2745be596 Author: Jan Hubicka <[email protected]> Date: Sun May 11 23:49:11 2025 +0200 i386: Fix move costs in vectorizer cost model. caused FAIL: gcc.target/i386/pr108938-3.c scan-assembler-times bswap[\t ]+ 3 FAIL: gcc.target/i386/pr111023-2.c scan-assembler (?:pcmpgtd|psrad) FAIL: gcc.target/i386/pr111023-2.c scan-assembler (?:pcmpgtw|psraw) FAIL: gcc.target/i386/pr111023-2.c scan-assembler punpckldq FAIL: gcc.target/i386/pr111023-2.c scan-assembler punpcklwd FAIL: gcc.target/i386/pr111023.c scan-assembler punpckldq FAIL: gcc.target/i386/pr111023.c scan-assembler punpcklwd FAIL: gcc.target/i386/vect-shiftv4qi.c scan-assembler-times psllw 2 FAIL: gcc.target/i386/vect-shiftv4qi.c scan-assembler-times psrlw 5 FAIL: gcc.target/i386/vect-shiftv8qi.c scan-assembler-times psllw 2 FAIL: gcc.target/i386/vect-shiftv8qi.c scan-assembler-times psrlw 5 with GCC configured with ../../gcc/configure --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r16-531/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="i386.exp=gcc.target/i386/pr108938-3.c --target_board='unix{-m32}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/pr108938-3.c --target_board='unix{-m32\ -march=cascadelake}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/pr111023-2.c --target_board='unix{-m32}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/pr111023-2.c --target_board='unix{-m32\ -march=cascadelake}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/pr111023.c --target_board='unix{-m32}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/pr111023.c --target_board='unix{-m32\ -march=cascadelake}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/vect-shiftv4qi.c --target_board='unix{-m32\ -march=cascadelake}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/vect-shiftv4qi.c --target_board='unix{-m64\ -march=cascadelake}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/vect-shiftv8qi.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.)