Rot127
Rot127
> Do the yaml cover all the previous MS/*.cs cases ? Yes! And even way more now. Because we can generate them more reliably from the LLVM regression tests. >...
The whole way to store options should be overthought again. Currently there is no clear distinction between options for modules and whole CS. `CS_MODE_` for example gets set by the...
This would also allow to test instructions which are only used in certain modes independently. As well as instructions with changing asm text syntax. It would also allow to add...
Ah, yes. I should think while writing. Added the relevant issue as well.
> Will this issue be resolved after the modern testing https://github.com/capstone-engine/capstone/pull/2384? No. I will only copy the existing detail "tests" one to one to the new yaml test files. >...
If you want to fix it in a PR, please add a test in `issues.cs` or `issue.cs` files. I will move them to the yaml tests.
Don't add anything in the old `cstest` please. Better wait until https://github.com/capstone-engine/capstone/pull/2384 s done. I work every day on it and want to finish it soon. You can support me...
This is closely related to removing the `Makefile` build. Since the bindings partially rely on it (optionally via pkgconfig.mk).
fyi, the `next` branch has support for access information of operands as well. You might want to check, if it works there.
cc @wxrdnx At the latest I'm going to fix it in the https://github.com/capstone-engine/capstone/pull/2384 PR. But if you find time before, I would be grateful if you could take a look...