qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] disas/libvixl: Fix VIXL_FALLTHROUGH macro for Q


From: Richard Henderson
Subject: Re: [Qemu-devel] [PATCH] disas/libvixl: Fix VIXL_FALLTHROUGH macro for QEMU
Date: Fri, 18 May 2018 08:57:26 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0

On 05/18/2018 03:34 AM, Peter Maydell wrote:
> On 15 May 2018 at 15:46, Richard Henderson <address@hidden> wrote:
>> On 05/15/2018 06:25 AM, Peter Maydell wrote:
>>> That said, I think we're planning to deprecate vixl now we have the
>>> capstone support. Richard, what's the status here? Could we just remove
>>> the vixl code now?
>>
>> We could just remove vixl, yes.  I'd like to see updates to capstone to 
>> support
>> instructions post v8.0, but it's not like we have those with vixl either...
> 
> Just to check my understanding: with QEMU at the moment, you
> always get the capstone disassembler unless you specifically
> turn it off by passing --disable-capstone to configure, right
> (since we provide it as a submodule)?

Correct.

> We put that in in September last year, and we haven't had a
> pile of complaints about the disassembly (or indeed any
> complaints that I can recall), so I think we can consider it
> a success, and remove both vixl and the ancient binutils arm
> disassembler.

Yep.

> It would also be interesting to try interacting with capstone
> upstream about adding support for newer instructions (for
> instance they don't do the v8M insns). Do you know if capstone
> deals with new insns via resync from LLVM or if they've
> entirely forked and just make changes locally by hand?

They seem to have entirely forked, but I'm not completely sure.


r~



reply via email to

[Prev in Thread] Current Thread [Next in Thread]