Re: Disassembler location

2024-07-11 Thread Rot127
Fyi please note that LoongArch support was recently added to Capstone (https://github.com/capstone-engine/capstone/pull/2349). Also, if you want to add support for a new architecture in Capstone and it is supported in LLVM, you can use our new Auto-Sync updater. See https://github.com/capstone

Re: Disassembler location

2024-07-10 Thread Richard Henderson
On 7/10/24 14:55, Paolo Bonzini wrote: The others are not hosts, only targets.  By putting the file in target//, they do not need to add it to the "disassemblers" variable in meson.build---but they add it anyway. :) We should clean that up. :-) r~

Re: Disassembler location

2024-07-10 Thread Richard Henderson
On 7/10/24 11:02, Michael Morrell wrote: I'm working on a port to a new architecture and was noticing a discrepancy in where the disassembler code lives. There is a file "target//disas.c" for 4 architectures (avr, loongarch, openrisc, and rx), but a file "disas/.c" for 14 architectures (if I c

Re: Disassembler location

2024-07-10 Thread Paolo Bonzini
On 7/10/24 20:02, Michael Morrell wrote: I'm working on a port to a new architecture and was noticing a discrepancy in where the disassembler code lives. There is a file "target//disas.c" for 4 architectures (avr, loongarch, openrisc, and rx), but a file "disas/.c" for 14 architectures (if I cou

Disassembler location

2024-07-10 Thread Michael Morrell
I'm working on a port to a new architecture and was noticing a discrepancy in where the disassembler code lives. There is a file "target//disas.c" for 4 architectures (avr, loongarch, openrisc, and rx), but a file "disas/.c" for 14 architectures (if I counted right). It seems the 4 architectur