https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113656
--- Comment #2 from Haochen Jiang <haochen.jiang at intel dot com> --- Actually it is caused by option -funsafe-math-optimizations but not -mavx10.1. Before my commit, while using option: -frounding-math -O3 -mavx512fp16 -mavx512vl -funsafe-math-optimizations It will also report ICE. In GCC13.2, it won't, which means it is introduced in GCC14. You got that bisect result since it is when avx10.1 first introduced. -mavx10.1 will enable -mavx512fp16 and -mavx512vl. When we eliminate -funsafe-math-optimizations, it will be ok. Also if we are only using -mavx512vl, everything is ok. Seems like something got disabled under -mavx512fp16. Need more bisect with option: -frounding-math -O3 -mavx512fp16 -mavx512vl -funsafe-math-optimizations to find out why.
