|
From: | Thomas Huth |
Subject: | Re: [PATCH 2/5] scripts/checkpatch.pl: Do not allow assert(0) |
Date: | Wed, 22 Feb 2023 04:53:19 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.13.0 |
On 22/02/2023 00.25, Philippe Mathieu-Daudé wrote:
Since commit 262a69f428 ("osdep.h: Prohibit disabling assert() in supported builds") we can not build QEMU with NDEBUG (or G_DISABLE_ASSERT) defined, thus 'assert(0)' always aborts QEMU. However some static analyzers / compilers doesn't notice NDEBUG can't be defined and emit warnings if code is used after an 'assert(0)' call. See for example commit c0a6665c3c ("target/i386: Remove compilation errors when -Werror=maybe-uninitialized").
commit c0a6665c3c only uses g_assert_not_reached(), so that looks like a bad example for your asset(0) case?
Thomas
[Prev in Thread] | Current Thread | [Next in Thread] |