From: Stefan Weil <sw@weilnetz.de>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-trivial@nongnu.org, Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] monitor: Fix warning from clang
Date: Sat, 18 Aug 2012 13:49:56 +0200 [thread overview]
Message-ID: <502F8164.2060701@weilnetz.de> (raw)
In-Reply-To: <20120817120235.7a725482@doriath.home>
Am 17.08.2012 17:02, schrieb Luiz Capitulino:
> On Fri, 17 Aug 2012 16:41:34 +0200
> Markus Armbruster <armbru@redhat.com> wrote:
>
>> Luiz Capitulino <lcapitulino@redhat.com> writes:
>>
>>> On Fri, 17 Aug 2012 16:10:12 +0200
>>> Markus Armbruster <armbru@redhat.com> wrote:
>>>
>>>> Stefan Weil <sw@weilnetz.de> writes:
>>>>
>>>>> ccc-analyzer reports these warnings:
>>>>>
>>>>> monitor.c:3532:21: warning: Division by zero
>>>>> val %= val2;
>>>>> ^
>>>>> monitor.c:3530:21: warning: Division by zero
>>>>> val /= val2;
>>>>> ^
>>>>>
>>>>> Rewriting the code fixes this (and also a style issue).
>>>>
>>>> I'm afraid this doesn't actually fix anything, because...
>>>>
>>>>> Signed-off-by: Stefan Weil <sw@weilnetz.de>
>>>>> ---
>>>>> monitor.c | 7 ++++---
>>>>> 1 file changed, 4 insertions(+), 3 deletions(-)
>>>>>
>>>>> diff --git a/monitor.c b/monitor.c
>>>>> index 0c34934..0ea2c14 100644
>>>>> --- a/monitor.c
>>>>> +++ b/monitor.c
>>>>> @@ -3524,12 +3524,13 @@ static int64_t expr_prod(Monitor *mon)
>>>>> break;
>>>>> case '/':
>>>>> case '%':
>>>>> - if (val2 == 0)
>>>>> + if (val2 == 0) {
>>>>> expr_error(mon, "division by zero");
>>>>> - if (op == '/')
>>>>> + } else if (op == '/') {
>>>>> val /= val2;
>>>>> - else
>>>>> + } else {
>>>>> val %= val2;
>>>>> + }
>>>>> break;
>>>>> }
>>>>> }
>>>>
>>>> ... expr_error() longjmp()s out. The expression evaluator commonly
>>>> exploits that.
>>>
>>> And that's correct. As far far I understood it's fixing clang, not qemu.
>>>
>>>> If expr_error() returned, the code would be just as wrong after your
>>>> patch as before.
>>>
>>> Hmm, how? It checks for val2 == 0 first.
>>
>> It would evaluate A % 0 into A, which is wrong.
>
> Oh, you're talking about the result that would be returned by expr_prod().
> I thought you were saying that val2 == 0 was still possible.
>
>>
>>>> Perhaps the checker can be shut up by making expr_error() QEMU_NORETURN.
>>>
>>> That's indeed a better solution.
>>
>> Stefan, could you try that for us?
Adding QEMU_NORETURN to function expr_error also
fixes the warning from ccc-analyzer.
I'll send a patch series which adds this and some more
QEMU_NORETURN attributes.
What about using above patch in addition? IMHO it
improves readability, and it fixes the coding style.
Regards,
Stefan W.
next prev parent reply other threads:[~2012-08-18 20:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 13:34 [Qemu-devel] [PATCH] monitor: Fix warning from clang Stefan Weil
2012-08-17 13:58 ` Luiz Capitulino
2012-08-17 14:10 ` Markus Armbruster
2012-08-17 14:21 ` Luiz Capitulino
2012-08-17 14:41 ` Markus Armbruster
2012-08-17 15:02 ` Luiz Capitulino
2012-08-18 11:49 ` Stefan Weil [this message]
2012-08-20 7:17 ` Markus Armbruster
2012-08-24 10:31 ` Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=502F8164.2060701@weilnetz.de \
--to=sw@weilnetz.de \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).