Rot127

@Amoystyle In the `v5` branch `CS_OPT_ON == 3` in the Python bindings and the c header. So this might not be the reason.

@cyb3rc Can you please try it and close this one if it works for you?

`llvm-mc` seems to agree if I am not mistaken: ``` echo "0x90,0xFF,0x25,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x90" | llvm-mc-19 --disassemble --arch=x86 --x86-asm-syntax=intel --show-encoding .text nop # encoding: [0x90] jmpl *0 # encoding: [0xff,0x25,0x00,0x00,0x00,0x00] addb %al,...

The `-Wmaybe-uninitialized` is giving us false positive on some LLVM code. This is why we have disabled it. The others are of course valid. Will add the over the next...

Moved this to the `v6 - Beta` milestone. The important ones are fixed in https://github.com/capstone-engine/capstone/pull/2469. The rest should be only the `missing-prototype`. With the v6 Beta the PPC and ARM...

I cannot reproduce the fuzzing bug. Locally everything is fine (also no segfault for `0x0->0xffffffff`). ~~My guess is, it is a Python 2 issues. So I'd wait for https://github.com/capstone-engine/capstone/pull/2378 and...

@FinnWilkinson The main thing is the missing review from @kabeor and/or @aquynh. I'm currently off. But will take time in two days to rebase it and address reviewer comments.

@FinnWilkinson Please be aware that we will likely change the enum naming of `AArch64_ -> AARCH64_` in the near future. Just so you are aware of (see: https://github.com/capstone-engine/capstone/pull/2349#discussion_r1641227883). I am...

@aquynh @kabeor Please review this. I just rebase it again. The failing tests are explained here: https://github.com/capstone-engine/capstone/pull/2298#issuecomment-2151699039

@aquynh @kabeor When you review this weekend, you can skip https://github.com/capstone-engine/capstone/pull/2298/commits/0615ebb3cd51d2626d171c5361a87196f1478951. This one is only the enum name change.