Closed Antwy closed 2 years ago
@JonathanSalwan, could you run CI, please?
Is it something that can differ from capstone v4 and v5?
Is it something that can differ from capstone v4 and v5?
According to CI, I've my answer. Maybe you should add ifdef
to add the enum only on capstone v5. For example: https://github.com/JonathanSalwan/Triton/blob/master/src/libtriton/arch/x86/x86Specifications.cpp#L158-L162
I've updated the Linux CI to test capstone v4 and v5 otherwise with such #if ... #endif
we can't test the new code. Once CIs are finished to process I will merge your MR, then the new CI will test your code once merged.
I've pushed on dev-v1.0
fixes to support Capstone v4 and v5 as well as updated CIs to test both versions.
Thanks :)
In capstone ARM64_INS_SUBS key (809) differs from ARM64_INS_SUB (805), so capstoneInstructionToTritonInstruction sets invalid instruction type for subs instructions
upd: found the same for adds