[Bug target/126581] [16/17 Regression] -mavx10.2 no longer works by r16-9456-gca889982b6f259
"hjl.tools at gmail dot com via Gcc-bugs" <[email protected]> Mon, 03 Aug 2026 02:32:05 +0000
| Newsgroups | gmane.comp.gcc.bugs |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=126581 --- Comment #12 from H.J. Lu <hjl.tools at gmail dot com> --- (In reply to H.J. Lu from comment #11) > (In reply to Hongtao Liu from comment #10) > > (In reply to H.J. Lu from comment #9) > > > > I think the aliases should be controlled by a macro. For GCC 16, they > > > > should be enabled by default. > > > > > > Something like > > > > > > #ifndef __AVX10_2_COMPATIBLE_INTRINSICS__ > > > #define __AVX10_2_COMPATIBLE_INTRINSICS__ 0/1 > > > #endif > > > > > > #if __AVX10_2_COMPATIBLE_INTRINSICS__ > > > # define compatible aliases > > > #endif > > > > I prefer just add the alias version for 16.x and 15.x, not for trunk and no > > macro for the control of those aliases. > > Then we should add a warning to 16.x and 15.x to warn the usages of these We can add deprecated attribute to these aliases. > aliases as well as add an option to 16.x and 15.x to disable these aliases > so that developers can prepare these projects for GCC 17.