You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the XED command interface (in verbose mode) or the xed-ex4 example with an instruction like "vaddpd zmm0 {k1}, zmm1, zmm2", the first operand is printed as
0 REG0/W/ZF64/EXPLICIT/NT_LOOKUP_FN/ZMM_R3
It would be helpful if the W could be changed to RCW, which is the output of the xed_decoded_inst_operand_action() function for this example.
The text was updated successfully, but these errors were encountered:
This was done somewhat intentionally. There is a chart in xed_decoded_inst_operand_action() that explains what is going on (mostly). The operands' action is mediated by the mask register used. The debug message is printing essentially some internal stuff, which is normally directly usable, but in this case it requires further interpretation.
When using the XED command interface (in verbose mode) or the xed-ex4 example with an instruction like "vaddpd zmm0 {k1}, zmm1, zmm2", the first operand is printed as
It would be helpful if the W could be changed to RCW, which is the output of the xed_decoded_inst_operand_action() function for this example.
The text was updated successfully, but these errors were encountered: