https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118815
--- Comment #5 from Haochen Jiang <haochen.jiang at intel dot com> --- It is caused by the EVEX512 set and condition judge on warnings. EVEX512 should not be set or taken into consideration if AVX512 not explicitly enabled.