[PATCH 3/5] x86: support AVX10.1/512

[Jiang, Haochen]

> But of course the question remains on whether this is needed in the first
> place. Personally I'd favor making AES a prereq of VAES (and PCLMULQDQ one
> of VPCLMULQDQ); if we decided to go that route, I'd make that change a

For PCLMULQDQ and VPCLMULQDQ, the imply should be ok. Actually, I have
added that in GCC in April, but I forgot to check Binutils at that time:

https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=4246611d1915f1664c01f286dbeb946dd06e2a4d

For AES/VAES, I am conservative on that at that time because not all the insts are
included in VAES:

https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=24a8acc1662c37003a7b54814bf840019fec2190

But I suppose the reason why AESIMC/AESKEYGENASSIST are not included might
be one key length is 128 bit while generating/transforming two at the same time
and putting them into ymm register is not quite needed.

I am both ok on whether to imply or not since it would be simple if implied.

Thx,
Haochen

> separate prereq patch. Yet before that a clarification in the AVX10 spec
> (or even in the SDM itself) would of course be quite helpful, albeit of
> course we have some leeway here, as there's some level of discretion that
> we have as to what exact effects -march= / .arch have.
> 
> Jan