[Bug target/118815] [15 Regression] Getting `Vector size conflicts between AVX10.1 and AVX512, using 512 as max vector size` warning with -Wsystem-headers

[cvs-commit at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118815

--- Comment #9 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Haochen Jiang <jian...@gcc.gnu.org>:

https://gcc.gnu.org/g:e15216046dba02ffa1c3ae367cdc86d5fd3df0be

commit r15-7582-ge15216046dba02ffa1c3ae367cdc86d5fd3df0be
Author: Haochen Jiang <haochen.ji...@intel.com>
Date:   Mon Feb 10 16:53:27 2025 +0800

    i386: Do not check vector size conflict when AVX512 is not explicitly set
[PR 118815]

    When AVX512 is not explicitly set, we should not take EVEX512 bit into
    consideration when checking vector size. It will solve the intrin header
    file reporting warnings when compiling with -Wsystem-headers.

    However, there is side effect on the usage for '-march=xxx -mavx10.1-256',
    where xxx is with AVX512. It will not report warning on vector size for
now.
    Since it is a rare usage, we will take it.

    gcc/ChangeLog:

            PR target/118815
            * config/i386/i386-options.cc (ix86_option_override_internal):
            Do not check vector size conflict when AVX512 is not explicitly
            set.

    gcc/testsuite/ChangeLog:

            PR target/118815
            * gcc.target/i386/pr118815.c: New test.