From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 3/3] igmp: Remove apparently unneeded suppression
Date: Wed, 14 Jan 2026 12:11:43 +1100 [thread overview]
Message-ID: <aWbtTxZLMdzuFFFL@zatzit> (raw)
In-Reply-To: <20260114003503.412fc9d1@elisabeth>
[-- Attachment #1: Type: text/plain, Size: 1454 bytes --]
On Wed, Jan 14, 2026 at 12:35:03AM +0100, Stefano Brivio wrote:
> On Tue, 13 Jan 2026 14:54:15 +1100
> David Gibson <david@gibson.dropbear.id.au> wrote:
>
> > cppcheck-2.19.1 complains that the unusedFunction suppression in igmp.c
> > doesn't match. That seems like a cppcheck bug, because the function
> > clearly *is* unused. The function exists because otherwise the compiler
> > fails because "ISO C forbids an empty translation unit".
> >
> > mld.c contains an identical unused definition for the same reason, but
> > without the suppression. It doesn't seem to have caused unusedFunction
> > warnings, so maybe cppcheck counts the non-empty translation unit
> > requirement as a "use" of the function?
>
> No idea why, but with this patch and cppcheck 2.16.0 I'm getting:
>
> igmp.c:16:0: style: The function 'unused' is never used. [unusedFunction]
> __attribute__((__unused__)) static void unused(void) { }
> ^
>
> ...I guess we needed one and exactly one suppression between mld.c and
> igmp.c, even though it's two different translation units.
Huh. Weird.
> Anyway, whatever, it's too old to make sense. Upgraded to 2.19.0, no
> error there, I guess it should be good enough for everybody.
Works for me.
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-01-14 1:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 3:54 [PATCH 0/3] cppcheck-2.19.1 fixes David Gibson
2026-01-13 3:54 ` [PATCH 1/3] treewide: Fix more pointers which can be const David Gibson
2026-01-13 3:54 ` [PATCH 2/3] epoll_ctl: Move u64 variant first for safer initialisation David Gibson
2026-01-13 3:54 ` [PATCH 3/3] igmp: Remove apparently unneeded suppression David Gibson
2026-01-13 23:35 ` Stefano Brivio
2026-01-14 1:11 ` David Gibson [this message]
2026-01-14 0:08 ` [PATCH 0/3] cppcheck-2.19.1 fixes Stefano Brivio
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=aWbtTxZLMdzuFFFL@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).