[RFC,0/2] x86: don't enable deprecated ISA extensions by default

Message ID 3ffc6c0b-4779-4dd7-90a7-150ed74b85dc@suse.com
Headers
Series x86: don't enable deprecated ISA extensions by default |

Message

Jan Beulich Nov. 15, 2024, 10:57 a.m. UTC
  IMO it has been a mistake from the beginning that all ISA extensions are
enabled by default. This way possible flaws e.g. in the compiler simply
go unnoticed. But that ship has sailed. However, for extensions where
support was removed from the compiler, we should at least consider whether
to disable them by default. That's what this series proposes (but see a
timing related RFC remark in patch 2).

Beyond that there are further discontinued extensions, which however gcc
still supports: HLE and VP2INTERSECT on the Intel side, TBM, XOP, FMA4,
and LWP for AMD. Question is what (if anything) to do there, which may
depend on what gcc's plans are.

1: default to not accepting MPX insns
2: default to not accepting Xeon Phi insns

Jan
  

Comments

Jiang, Haochen Nov. 21, 2024, 7 a.m. UTC | #1
> From: Jan Beulich <jbeulich@suse.com>
> Sent: Friday, November 15, 2024 6:58 PM
> 
> Beyond that there are further discontinued extensions, which however gcc still
> supports: HLE and VP2INTERSECT on the Intel side, TBM, XOP, FMA4, and LWP
> for AMD. Question is what (if anything) to do there, which may depend on
> what gcc's plans are.
> 

I agree. If GCC removed them, it should be the time not enabling them by default
in Binutils.

BTW, VP2INTERSECT should be on Zen5 if I remember correctly, it won't be removed
In the near future.

Thx,
Haochen