Add support for new EVM opcodes

[andelf]

• Mark this if you consider it ready to merge
• I've added tests (optional)
• I wrote some lines in the book (optional)

This is blocked by: capstone-engine/capstone#2602

The repo URL is temperorily changed to my fork, use the following to build with the new EVM support:

sys/install.sh --with-capstone-next

Description

• The Ethereum Virtual Machine (EVM) has introduced new opcodes since the original whitepaper's publication. This pull request incorporates these missing opcodes.
• Opcode types are now revised for better visual distinction. All chain-related opcodes are marked as "CRYPTO" for easier identification.

Question

It is required to back-port these changes to capstone v4 and v5 using patch files?

[trufae]

[trufae]

if you think it's worth backporting (i dont think so) you can do it. i would opt for wrapping those cases with an ifdef depending on the version of capstone linked to radare2. I think it's fine to assume that r2 wont be able to use those instructions if you are linking to capstone 4 or 5 because distros need to update those packages when cs6 is out (dunno when will this happen).

[andelf]

@trufae Thanks for the heads up! I'll plan to add the required patches once capstone-engine/capstone#2602 lands.

UPDATE/EDIT: I was thinking it's required to make evm.c/evm.h compatible with the arch.evm plugin(capstone part). If it doesn't matter, then ifdef approach is acceptable.