Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use xed_decoded_inst_operand_action() for CLI/examples #223

Open
andreas-abel opened this issue Apr 26, 2020 · 1 comment
Open

Use xed_decoded_inst_operand_action() for CLI/examples #223

andreas-abel opened this issue Apr 26, 2020 · 1 comment

Comments

@andreas-abel
Copy link
Contributor

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.

@markcharney
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants