Rot127
Rot127
Regarding the CI: - The auto-sync job can fail. Since we have not yet merged the llvm-18 update - The clang-tidy errors should be fixed if it complains about changes...
> However, in LoongArch assembly, memory operands are not special i.e. they are normal register/immediate operands. I am unsure how to create MEM operands. Indeed a little tricky. I checked...
@jiegec @FuzzySecurity Before I forget. Do you have any feedback working with Auto-Sync? I would appreciate any comments and feedback on it. Especially, what to make better, what was difficult...
Due to https://github.com/capstone-engine/llvm-capstone/pull/45/commits/ee2e109d402d383a428677c920759a92e1437dd2 please generate the Disassembler tables again or just add the one line by hand.
@jiegec Did you already find time to run the fuzzing? The PR is almost done.
@jiegec See https://github.com/jiegec/capstone/pull/2 for the name change
@jiegec https://github.com/jiegec/capstone/pull/3 should fix the test. Please check the CI in the PR to be sure. ~~Additionally, rebase this one after https://github.com/capstone-engine/capstone/pull/2391 is merged.~~
Almost forgot. Please change the doxygen comment of the function to use `///` instead of `//`
Merged with https://github.com/capstone-engine/llvm-capstone/pull/45
Yes, RISC-V is one of the difficult architectures to add. Because it wasn't refactored yet to use Auto-Sync. This won't be the only crash you will encounter I think. There...