[WIP] update to capstone v4 #4

[nganhkhoa]

• arm
• arm64
• evm
• m68k
• m680x
• mips
• ppc
• sparc
• systemz
• tms320c64x
• x86
• xcore.h

I also remove hardcoded number and replace with macros from c2hs.

Need tests!!!

[nganhkhoa]

Apparently, the code builds fine with stack. I still miss some #define though. I'll be writing tests for the new archs. Hope it works.

[nganhkhoa]

I should get back to this around this time. There seems to be no big update to capstone over the last year. The latest version is 4.0.2 and released on May 2020. A few fixes with the current release will be compatible then tests are to be added.

[nganhkhoa]

I'll be porting the binding test in https://github.com/aquynh/capstone/tree/v4/bindings/python into Example folder.

Then I generate the test cases in test/ by comparing the mnemonic and opcode string output.

[nganhkhoa]

Yeah, just discovered an issue with c2hs. Apparently we can use {#get struct->member#} p to make a Bool, expanded into toBool `fmap` peekByteOff p <offset> :: IO CInt. And this might not work well in some cases.

So I have to go back to all the Bool and change into toBool <$> (peekByteOff p {#offset struct->member#} :: IO Word8)

I don't know if this is intended behavior of c2hs to assume a Bool as an CInt rather then Int8. But I got issue when disassemble all the CsArmOp and found out all of them are subtracted. Same thing happens with CsArm writeback but in edge cases only. I doubted the Boolean decoding.

[nganhkhoa]

Just found out that when can replace if then () else pure (). Rewriting TestArm.

Update soon for all other tests.

[XVilka]

Capstone 5.0 is about to be released, it's better to target it instead:

• https://github.com/capstone-engine/capstone/releases
• A Letter Prior to the Official Release of Capstone v5.0 capstone-engine/capstone#2053

There is also a huge project to automate updates for different architectures to stay relevant with minimum effort, but it will bring some API differences: capstone-engine/capstone#2015

Please let us know if you have any feedback about the current state or the auto-sync project.