https://gcc.gnu.org/g:31cbac836bb4f4c2172a91ee6164d8fdd32a8cb8

commit r14-11314-g31cbac836bb4f4c2172a91ee6164d8fdd32a8cb8
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.

Diff:
---
 gcc/config/i386/i386-options.cc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gcc/config/i386/i386-options.cc b/gcc/config/i386/i386-options.cc
index f6c450cc871c..a6eba1ca2b87 100644
--- a/gcc/config/i386/i386-options.cc
+++ b/gcc/config/i386/i386-options.cc
@@ -2725,6 +2725,7 @@ ix86_option_override_internal (bool main_args_p,
                        "using 512 as max vector size");
        }
       else if (TARGET_AVX512F_P (opts->x_ix86_isa_flags)
+              && (opts->x_ix86_isa_flags_explicit & OPTION_MASK_ISA_AVX512F)
               && !(OPTION_MASK_ISA2_EVEX512
                    & opts->x_ix86_isa_flags2_explicit))
        warning (0, "Vector size conflicts between AVX10.1 and AVX512, using "

Reply via email to