Rot127
Rot127
Thanks for pointing this out. Turns out this was accidentally pulled in, because we wanted to have the TriCore architecture being part of v5. TriCore used the new auto-sync updater...
LLVM 18 disassembles without `1`: ``` echo "0xd1,0x10" | llvm-mc-18 --disassemble --arch=x86 --show-encoding --output-asm-variant=1 .text rcl dword ptr [eax] # encoding: [0xd1,0x10] ``` Please check what is the correct syntax...
@wargio Can you please check against `llvm-mc`?
Did you compile with the `CAPSTONE_DIET` option? This disables most details.
I'd love it! @kabeor has the last say with this.
It is very unlikely that this will be fixed due to https://github.com/capstone-engine/capstone/issues/2089. In the `next` branch the instruction is disassembled correctly. Also it has many more features and is more...
Weird. Make sure that you have not `v4` installed and clean the complete capstone dir from build files. Or clone it freshly. It might be, that the Python bindings use...
Seems to be a side effect of https://github.com/capstone-engine/capstone/commit/d2a39a2ef15ce4878f1186f711e97bee68845339 When I remove the lines I get the correct result again: ```bash cd /tmp python3 -m venv venv source venv/bin/activate # Get...
@amaanq Sorry for the late answer. Have you tried to use the latest `v5` branch?
@gerph or @kabeor Please close it