Rot127
Rot127
You can leave it open. In general we should get a warning free build. But for now we just focus on getting as many archs updated as possible. Afterwards we...
Is it fine for you, if I cherry-pick your commits into the auto-sync PR? It is easier to work on it this way. Also it would probably be merged faster....
My problem is that `llvm-capstone` is out of sync and generates newer tables (with the encoding). And I am tiered of cherry picking the right commits into other branches. Also...
Sorry for letting this PR stall for so long. I looked into it quite a while, and we discussed this internally as well. Unfortunately, we won't merge it. The problem...
So after investigating it a little, I couldn't spot the problem immediately. Which means it is likely somewhere in the generated files. Because we will update to LLVM 18 soon...
It was indeed added in LLVM-18. So this will be closed once https://github.com/capstone-engine/capstone/pull/2298 is merged.
There is no general way to determine this currently. It depends on the arch. If you need to know this for ARM you can check the conditional code via `cs_arm->cc`....
Also considering https://github.com/capstone-engine/capstone/issues/1281 when generating tests.
The current MC test assume that a byte string can be disassembled independently from other byte strings. This is not true for instructions which depend on each other (IT/VPT blocks...
@kabeor @aquynh We thought about choosing `yaml` as file format for the test files. It's better to read then `json` and can be used for the bindings as well. Also...