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

Fix registry access on cmov instructions #1727

Merged
merged 7 commits into from
Mar 7, 2021

Conversation

keenk
Copy link
Contributor

@keenk keenk commented Feb 20, 2021

The destination operand of the conditional move (cmov...) instructions incorrectly states that they are READ | WRITE. These instructions actually do not read the destination operand at all, but instead rely on the associated flag set in EFLAGS.

Re-fix operand access of three mov instructions
The python script for generating constants in the bindings does not know how to handle the #if 0 statements included in these files.
Pulling from upstream
Registry access for the destination operand of the conditional move (cmov) opcodes were incorrectly listed as READ | WRITE. Although you would expect the two operands to be compared in this opcode, it instead relies on the associated flag in EFLAGS regardless of the value in the destination operand.
@aquynh aquynh merged commit dba65a6 into capstone-engine:next Mar 7, 2021
@aquynh
Copy link
Collaborator

aquynh commented Mar 7, 2021

merged, thanks!

@riptl riptl mentioned this pull request Jul 22, 2022
6 tasks
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

Successfully merging this pull request may close these issues.

2 participants