On Wed, Jun 11, 2025, 10:17 PM haochen.jiang <haoch...@smtp.intel.com>
wrote:
> On Linux/x86_64,
>
> dcb9af06212e8bb36e84a1b8498c625c29abeb6f is the first bad commit
> commit dcb9af06212e8bb36e84a1b8498c625c29abeb6f
> Author: Gwenole Beauchesne <gb.de...@gmail.com>
> Date: Mon Jun 2 14:44:55 2025 -0700
>
> c/c++: Handle '#pragma GCC target optimize' early [PR48026]
>
> caused
>
> FAIL: gcc.target/i386/vect-pragma-target-1.c scan-assembler-times
> vpaddw.+zmm[0-9]+ 1
> FAIL: g++.target/i386/vect-pragma-target-1.C -std=gnu++17
> scan-assembler-times vpaddw.+zmm[0-9]+ 1
> FAIL: g++.target/i386/vect-pragma-target-1.C -std=gnu++26
> scan-assembler-times vpaddw.+zmm[0-9]+ 1
> FAIL: g++.target/i386/vect-pragma-target-1.C -std=gnu++98
> scan-assembler-times vpaddw.+zmm[0-9]+ 1
>
Can someone file a bug for this. It is just a testcase issue so I am
willing to let it broken until I get back from vacation.
> with GCC configured with
>
> ../../gcc/configure
> --prefix=/export/users3/haochenj/src/gcc-bisect/master/master/r16-1429/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/vect-pragma-target-1.c
> --target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="i386.exp=gcc.target/i386/vect-pragma-target-1.c
> --target_board='unix{-m64\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="i386.exp=g++.target/i386/vect-pragma-target-1.C
> --target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="i386.exp=g++.target/i386/vect-pragma-target-1.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.)
>
