From: Markus Armbruster <armbru@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] test-qapi-visit causes clang -fsanitize=undefined warning
Date: Mon, 10 Mar 2014 10:45:15 +0100 [thread overview]
Message-ID: <87eh2ae6ac.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <CAFEAcA-kVfnh4UwKsiK4tDRksZ2N-PXHd8a83fTjnwBNH5L+Ag@mail.gmail.com> (Peter Maydell's message of "Sat, 8 Mar 2014 14:03:25 +0000")
Peter Maydell <peter.maydell@linaro.org> writes:
> On 8 March 2014 12:39, Peter Maydell <peter.maydell@linaro.org> wrote:
>> I've noticed that the tests/test-qapi-visit.c code provokes the following
>> complaint from clang's -fsanitize=undefined undefined-behaviour
>> checker when you run 'make check':
>>
>> tests/test-qapi-visit.c:462:33: runtime error: member access within
>> null pointer of type 'UserDefA' (aka 'struct UserDefA')
>
> There's also this clang compile warning which is probably not
> related but is also in code dealing with unions:
>
> CC tests/test-qmp-output-visitor.o
> /home/petmay01/linaro/qemu-for-merges/tests/test-qmp-output-visitor.c:452:17:
> warning: implicit conversion from enumeration type
> 'enum UserDefUnionKind' to different enumeration type
> 'UserDefFlatUnionKind' (aka 'enum UserDefFlatUnionKind')
> [-Wenum-conversion]
> tmp->kind = USER_DEF_UNION_KIND_A;
> ~ ^~~~~~~~~~~~~~~~~~~~~
> 1 warning generated.
Thanks, I'll look into both.
next prev parent reply other threads:[~2014-03-10 9:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-08 12:39 [Qemu-devel] test-qapi-visit causes clang -fsanitize=undefined warning Peter Maydell
2014-03-08 14:03 ` Peter Maydell
2014-03-10 9:45 ` Markus Armbruster [this message]
2014-03-10 12:21 ` Markus Armbruster
2014-03-10 12:27 ` Peter Maydell
2014-03-10 13:36 ` Markus Armbruster
2014-03-10 13:41 ` Peter Maydell
2014-03-10 18:21 ` Markus Armbruster
2014-03-11 12:29 ` Kevin Wolf
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=87eh2ae6ac.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.