RE: [PATCH] x86: rename avx10.1aux to avx10v1aux

> From: Jan Beulich <[email protected]>
> Sent: Wednesday, August 19, 2026 4:53 PM
> 
> On 19.08.2026 10:18, Rohan Shenoy wrote:
> > Align with GCC/Clang naming (-mavx10v2aux) as discussed [1].
> 
> This could do with a little bit more of an explanation. I don't quite see how
> compiler command line options and assembler directive operands are in direct
> need to be fully in sync.
> 
> So what about the avx10.1 and avx10.2 operands then? Are we meaning to
> become
> inconsistent just because Clang and later maybe gcc are? In both I see -
> mavx10.1
> and -mavx10.2. How does that fit with -mavx10v2aux (which Clang trunk, as
> available on godbolt.org, doesn't even recognize yet, as opposed to gcc
> trunk)?

Clang did not land on trunk, while GCC lands currently.

> As that's still under development, may I suggest that instead Clang / gcc
> reconsider the naming used?
> 
> If they don't want to switch to consistent naming, my next best suggestion for
> gas would then be to recognize both avx10.1aux and avx10v1aux (and
> subsequently similarly for v2-aux).
> 

I am okay with that. I am not a big fan of the current aux naming convention in
CPUID from the very beginning.

Rohan, it is up to your (or AMD) call.

Thx,
Haochen