[PATCH] x86: Support x86 USER_DOITM/SUP_DOITM instructions
Jan Beulich
jbeulich@suse.com
Tue Nov 17 08:55:26 GMT 2026
On 17.11.2026 09:52, Jiang, Haochen wrote:
>> From: Jan Beulich <jbeulich@suse.com>
>> Sent: Monday, November 16, 2026 8:39 PM
>>
>> On 16.11.2026 09:00, Haochen Jiang wrote:
>>> --- a/opcodes/i386-opc.tbl
>>> +++ b/opcodes/i386-opc.tbl
>>> @@ -3724,3 +3724,11 @@ vmovrs<dq>, 0xf36f, AVX10_2&MOVRS&x64,
>> Modrm|Masking|Map5|<dq:vexw>|Disp8ShiftVL
>>> vpmldsabflydq, 0x66dc, AVX10_VPMLDSABFLYDQ,
>> Modrm|Space0F3A|Src1VVVV|VexW1|Disp8ShiftVL|CheckOperandSize|No
>> Suf, { Imm8, RegXMM|RegYMM|RegZMM|Unspecified|BaseIndex,
>> RegXMM|RegYMM|RegZMM, RegXMM|RegYMM|RegZMM }
>>>
>>> // AVX10_VPMLDSABFLYDQ instructions end.
>>> +
>>> +// USER_DOITM/SUP_DOITM instructions.
>>
>> ... blanks around the slash here as well as ...
>>
>>> +rddoitm, 0xf30f1e/6, DOITM, Modrm|NoSuf, { Reg32|Reg64 }
>>> +setdoitm, 0xf30f1efc, DOITM, NoSuf, {}
>>> +wrdoitm, 0xf20f1e/6, DOITM, Modrm|NoSuf, { Reg32|Reg64 }
>>> +
>>> +// USER_DOITM/SUP_DOITM instructions end.
>>
>> ... here.
>>
>
> Do you mean it should become " USER_DOITM/ SUP_DOITM"?
>
> I did not saw a space after a slash elsewhere, or I mis-understood
> something?
// USER_DOITM / SUP_DOITM instructions
> Or let's change to "USER_DOITM and SUP_DOITM"?
That would be okay too.
Jan
More information about the Binutils
mailing list