Rot127
Rot127
I'll add one once the ~~PPC~~ AArch64 refactor is coming to an end.
Testing the build of bindings and their correct function isn't tested in the CI jobs as well (https://github.com/capstone-engine/capstone/pull/2034#issuecomment-1568881681).
> Only having one place to stringify an instruction would streamline the update process. I very much like the idea to centralize the printing of instructions. Would you mind putting...
Just an idea how to test every possible execution path **and** generate a set of instructions which cover every possible `detail` combination. Depending on architecture the number of possible unique...
Can you check if this also happens with the `cstool`? > `CS_API_MAJOR = 3` Also please try it with Capstone v5 If this doesn't help, you can use https://github.com/capstone-engine/capstone/pull/2026 for...
Could you please provide a minimal example to run. With the output you expect and what the actual behavior is.
After #2026 is merged we can implement this easily by adding a flag. Currently always the alias syntax is used, but the detail can be selected (real vs. alias details).
~~Will add it to the AArch64 PR.~~ Never mind. There are also warnings in ARM. So it need to be its own PR.
Added it to https://github.com/capstone-engine/capstone/issues/2015
Using my branch is currently the best option you have. Because it will take a while until everything is merged into `next` and `v6` is released (see: https://github.com/capstone-engine/capstone/issues/2015 for tasks...