[Top][All Lists]

[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: Tue, 15 May 2018 07:46:27 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0

On 05/15/2018 06:25 AM, Peter Maydell wrote:
> On 15 May 2018 at 14:13, Stefan Weil <address@hidden> wrote:
>> This is fixed in upstream vixl, in fact:
>> https://git.linaro.org/arm/vixl.git/commit/?id=de326f850f736c3a337fda52845ed3d2e620cc02
>> That fix will work for the moment, but is not sufficient for the future
>> because it only supports gcc 7.x, but not gcc 8.x or later:
>> +#elif __GNUC__ == 7
>> How do we proceed with the code in QEMU? Do you have a plan to update the
>> vixl code? As vixl is obviously no longer maintained on GitHub, I am not
>> sure whom I could contact.
> The github page points you to the linaro repo which is the new upstream.
> 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...

> I guess that having the compiler check is better than finding them
> later with coverity. It's a shame gcc doesn't support the standard
> mechanism of using /* fallthrough */ to mark these, though.

It does.  Apparently not by default anymore, however:

@item @option{-Wimplicit-fallthrough=0} disables the warning altogether.

@item @option{-Wimplicit-fallthrough=1} matches @code{.*} regular
expression, any comment is used as fallthrough comment.

@item @option{-Wimplicit-fallthrough=2} case insensitively matches
@code{.*falls?[ \t-]*thr(ough|u).*} regular expression.

@item @option{-Wimplicit-fallthrough=3} case sensitively matches one of the
following regular expressions:

I think either =2 or =1 would work for us in QEMU.


reply via email to

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