From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 2136] bus/dpaa: unreachable code warnings
Date: Tue, 17 Nov 2026 17:09:19 +0000 [thread overview]
Message-ID: <bug-2136-3@https.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=2136
Bug ID: 2136
Summary: bus/dpaa: unreachable code warnings
Product: DPDK
Version: 26.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: minor
Priority: Low
Component: other
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
Building with clang and -Wunreachable-code results in:
../drivers/bus/dpaa/base/qbman/qman.c:471:8: warning: code will never be
executed [-Wunreachable-code]
471 | (0 ? 0x10 : 0); /* Ignore SP */
| ^~~~
../drivers/bus/dpaa/base/qbman/qman.c:471:4: note: silence by adding
parentheses to mark code as explicitly dead
471 | (0 ? 0x10 : 0); /* Ignore SP */
| ^
| /* DISABLES CODE */ ( )
../drivers/bus/dpaa/base/qbman/qman.c:470:8: warning: code will never be
executed [-Wunreachable-code]
470 | (0 ? 0x40 : 0) | /* Ignore RP */
| ^~~~
../drivers/bus/dpaa/base/qbman/qman.c:470:4: note: silence by adding
parentheses to mark code as explicitly dead
470 | (0 ? 0x40 : 0) | /* Ignore RP */
| ^
| /* DISABLES CODE */ ( )
2 warnings generated.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2026-11-17 17:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-2136-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 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.