[PATCH 4/6] Rename Opcode Space Name Evexmap5 to xVexmap5

[Jiang, Haochen]

> From: Jan Beulich <jbeulich@suse.com>
> Sent: Wednesday, November 13, 2024 5:28 PM
> 
> On 13.11.2024 09:44, Haochen Jiang wrote:
> > From: "Hu, Lin1" <lin1.hu@intel.com>
> >
> > Nit: Currently this patch is based on all AVX10.2 instructions, if
> > the AVX10.2 insts are checked in after this patch, I will remove those
> > insts.
> 
> This looks largely okay, albeit conflicting with the Map7 renaming that's
> also in-flight. Taken together both bear the question: Might we be better
> off renaming _all_ {VEX,EVEX}MAP<n> to just MAP<n>? There's no way to
> legacy-encode anything in maps 4-7, and hence there should be little or
> no confusion from omitting the prefixes altogether.

It seems ok for me. I don't think there would be legacy encoding for Map4-7.

We could only do the rename first, when there are instructions under VexMap4
or VexMap6, then it is the time to add the whole table. (BTW, At least for Map4,
in the near future, I suppose there won't be a Vex version coming.)

Thx,
Haochen