From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: "Beraldo Leal" <bleal@redhat.com>,
"David Hildenbrand" <david@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Marcelo Tosatti" <mtosatti@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
kvm@vger.kernel.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
qemu-s390x@nongnu.org, "Daniel P. Berrangé" <berrange@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Ilya Leoshkevich" <iii@linux.ibm.com>
Subject: Re: [PATCH v2 2/4] target/i386: fix build warning (gcc-12 -fsanitize=thread)
Date: Fri, 16 Aug 2024 10:54:31 -0700 [thread overview]
Message-ID: <dbce200b-a6ac-46ed-aec3-4a87f1434797@linaro.org> (raw)
In-Reply-To: <54bb02a6-1b12-460a-97f6-3f478ef766c6@linaro.org>
On 8/16/24 03:59, Philippe Mathieu-Daudé wrote:
> On 15/8/24 00:41, Pierrick Bouvier wrote:
>> Found on debian stable.
>>
>> ../target/i386/kvm/kvm.c: In function ‘kvm_handle_rdmsr’:
>> ../target/i386/kvm/kvm.c:5345:1: error: control reaches end of non-void function [-Werror=return-type]
>> 5345 | }
>> | ^
>> ../target/i386/kvm/kvm.c: In function ‘kvm_handle_wrmsr’:
>> ../target/i386/kvm/kvm.c:5364:1: error: control reaches end of non-void function [-Werror=return-type]
>> 5364 | }
>>
>> Signed-off-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
>> ---
>> target/i386/kvm/kvm.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>
> But what about the other cases?
>
> $ git grep 'assert(false)'
> block/qcow2.c:5302: assert(false);
> hw/hyperv/hyperv_testdev.c:91: assert(false);
> hw/hyperv/hyperv_testdev.c:190: assert(false);
> hw/hyperv/hyperv_testdev.c:240: assert(false);
> hw/hyperv/vmbus.c:1877: assert(false);
> hw/hyperv/vmbus.c:1892: assert(false);
> hw/hyperv/vmbus.c:1934: assert(false);
> hw/hyperv/vmbus.c:1949: assert(false);
> hw/hyperv/vmbus.c:1999: assert(false);
> hw/hyperv/vmbus.c:2023: assert(false);
> hw/net/e1000e_core.c:564: assert(false);
> hw/net/igb_core.c:400: assert(false);
> hw/net/net_rx_pkt.c:378: assert(false);
> hw/nvme/ctrl.c:1819: assert(false);
> hw/nvme/ctrl.c:1873: assert(false);
> hw/nvme/ctrl.c:4657: assert(false);
> hw/nvme/ctrl.c:7208: assert(false);
> hw/pci/pci-stub.c:49: g_assert(false);
> hw/pci/pci-stub.c:55: g_assert(false);
> hw/ppc/spapr_events.c:648: g_assert(false);
> include/hw/s390x/cpu-topology.h:60: assert(false);
> include/qemu/osdep.h:240: * assert(false) as unused. We rely on this
> within the code base to delete
> migration/dirtyrate.c:231: assert(false); /* unreachable */
> target/i386/kvm/kvm.c:5773: assert(false);
> target/i386/kvm/kvm.c:5792: assert(false);
>
They don't seem to be a problem, but I'll do a series to clean this
completely from the code base, so assert(false) is eradicated.
next prev parent reply other threads:[~2024-08-16 17:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 22:41 [PATCH v2 0/4] build qemu with gcc and tsan Pierrick Bouvier
2024-08-14 22:41 ` [PATCH v2 1/4] meson: hide tsan related warnings Pierrick Bouvier
2024-08-15 9:50 ` Thomas Huth
2024-08-15 17:57 ` Pierrick Bouvier
2024-08-15 10:12 ` Peter Maydell
2024-08-15 11:05 ` Daniel P. Berrangé
2024-08-15 17:43 ` Pierrick Bouvier
2024-08-15 17:54 ` Peter Maydell
2024-08-15 17:58 ` Pierrick Bouvier
2024-08-16 5:44 ` Thomas Huth
2024-08-16 8:44 ` Daniel P. Berrangé
2024-08-14 22:41 ` [PATCH v2 2/4] target/i386: fix build warning (gcc-12 -fsanitize=thread) Pierrick Bouvier
2024-08-14 22:47 ` Richard Henderson
2024-08-15 17:54 ` Pierrick Bouvier
2024-08-15 9:49 ` Thomas Huth
2024-08-16 10:59 ` Philippe Mathieu-Daudé
2024-08-16 17:54 ` Pierrick Bouvier [this message]
2024-08-14 22:41 ` [PATCH v2 3/4] target/s390x: " Pierrick Bouvier
2024-08-14 22:57 ` Ilya Leoshkevich
2024-08-14 22:41 ` [PATCH v2 4/4] docs/devel: update tsan build documentation Pierrick Bouvier
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=dbce200b-a6ac-46ed-aec3-4a87f1434797@linaro.org \
--to=pierrick.bouvier@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=david@redhat.com \
--cc=iii@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=marcandre.lureau@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
/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).