The fail is expected since -march=cascadelake -mavx10.1-256 will lead to a
warning.
Also, we could not use -mno-avx512f with -mavx10.1-256, which also lead to a
warning.
> -----Original Message-----
> From: haochen.jiang <haoch...@ecsmtp.sh.intel.com>
> Sent: Monday, June 3, 2024 10:22 PM
> To: Jiang, Haochen <haochen.ji...@intel.com>; gcc-regress...@gcc.gnu.org;
> gcc-patches@gcc.gnu.org
> Subject: [r15-983 Regression] FAIL: gcc.target/i386/avx10_1-25.c (test for
> excess errors) on Linux/x86_64
>
> On Linux/x86_64,
>
> 1f2ca510065a2033bac408eb5a960ef0126f25cc is the first bad commit
> commit 1f2ca510065a2033bac408eb5a960ef0126f25cc
> Author: Haochen Jiang <haochen.ji...@intel.com>
> Date: Mon May 20 15:52:32 2024 +0800
>
> Add AVX10.1 target_clones support
>
> caused
>
> FAIL: gcc.target/i386/avx10_1-25.c (test for excess errors)
>
> with GCC configured with
>
> ../../gcc/configure --prefix=/export/users/haochenj/src/gcc-
> bisect/master/master/r15-983/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/avx10_1-25.c --
> target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="i386.exp=gcc.target/i386/avx10_1-25.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.)
