Re: RFC: Why dont we move to newer capstone?

[Richard Henderson]

On 10/5/19 3:11 AM, Lucien Murray-Pitts wrote:
> Hi folks,
> 
> Whilst working on a m68k patch I noticed that the capstone in use today (3.0)
> doesnt support the M68K and thus a hand turned disasm function is used.  
> 
> The newer capstone (5.0) appears to support a few more CPU, inc. m68k.

I don't see a capstone v5.  The latest I see is v4.1.

> Why we move to this newer capstone?

I had some patches for that floating about in May, but
it missed the merge window for qemu 4.1.

Thanks for reminding me about them.


r~