The listed operand access modes for cmov instructions in capstone/arch/X86/X86MappingInsnOp_reduce.inc look incorrect. They're listed as:
{ CS_AC_READ | CS_AC_WRITE, CS_AC_READ, 0 }
I would expect the access mode to be the same as for regular mov, i.e.:
{ CS_AC_WRITE, CS_AC_READ, 0 }
If this is not a bug, I would be interested in the reasoning behind marking cmov's destination operand as being read. As far as I know it can only be written (copied from the source operand) or left unchanged.
The listed operand access modes for cmov instructions in capstone/arch/X86/X86MappingInsnOp_reduce.inc look incorrect. They're listed as:
{ CS_AC_READ | CS_AC_WRITE, CS_AC_READ, 0 }I would expect the access mode to be the same as for regular mov, i.e.:
{ CS_AC_WRITE, CS_AC_READ, 0 }If this is not a bug, I would be interested in the reasoning behind marking cmov's destination operand as being read. As far as I know it can only be written (copied from the source operand) or left unchanged.