From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 2135] eal: unreachable code warning
Date: Tue, 17 Nov 2026 17:07:54 +0000 [thread overview]
Message-ID: <bug-2135-3@https.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=2135
Bug ID: 2135
Summary: eal: unreachable code warning
Product: DPDK
Version: 26.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: minor
Priority: Low
Component: core
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
Building with clang and -Wunreachable-code finds this:
[18/3982] Compiling C object lib/librte_eal.a.p/eal_common_rte_version.c.o
../lib/eal/common/rte_version.c:40:3: warning: code will never be executed
[-Wunreachable-code]
40 | snprintf(version, sizeof(version), "%s %d.%02d.%d",
| ^~~~~~~~
../lib/eal/common/rte_version.c:39:32: note: silence by adding parentheses to
mark code as explicitly dead
39 | if (strlen(RTE_VER_SUFFIX) == 0)
| ^
| /* DISABLES CODE */ ( )
1 warning generated.
It can be fixed by adding parens, using sizeof, or useing RTE_VERSION which is
already built by meson.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2026-11-17 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 17:07 bugzilla [this message]
2026-11-17 17:21 ` [DPDK/core Bug 2135] eal: unreachable code warning Bruce Richardson
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=bug-2135-3@https.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.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