From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/examples Bug 2144] ipsec-gw: unreachable code
Date: Tue, 17 Nov 2026 17:21:49 +0000 [thread overview]
Message-ID: <bug-2144-3@https.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=2144
Bug ID: 2144
Summary: ipsec-gw: unreachable code
Product: DPDK
Version: 26.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
Building with clang and -Wunreachable-code finds lots of dead error handling:
[3664/3982] Compiling C object
examples/dpdk-ipsec-secgw.p/ipsec-secgw_parser.c.o
../examples/ipsec-secgw/parser.c:439:3: warning: code will never be executed
[-Wunreachable-code]
439 | goto error_exit;
| ^~~~~~~~~~~~~~~
../examples/ipsec-secgw/parser.c:444:3: warning: code will never be executed
[-Wunreachable-code]
444 | goto error_exit;
| ^~~~~~~~~~~~~~~
../examples/ipsec-secgw/parser.c:467:4: warning: code will never be executed
[-Wunreachable-code]
467 | goto error_exit;
| ^~~~~~~~~~~~~~~
../examples/ipsec-secgw/parser.c:485:5: warning: code will never be executed
[-Wunreachable-code]
485 | goto error_exit;
| ^~~~~~~~~~~~~~~
../examples/ipsec-secgw/parser.c:494:5: warning: code will never be executed
[-Wunreachable-code]
494 | goto error_exit;
| ^~~~~~~~~~~~~~~
../examples/ipsec-secgw/parser.c:506:4: warning: code will never be executed
[-Wunreachable-code]
506 | goto error_exit;
| ^~~~~~~~~~~~~~~
../examples/ipsec-secgw/parser.c:514:4: warning: code will never be executed
[-Wunreachable-code]
514 | goto error_exit;
| ^~~~~~~~~~~~~~~
../examples/ipsec-secgw/parser.c:520:4: warning: code will never be executed
[-Wunreachable-code]
520 | goto error_exit;
| ^~~~~~~~~~~~~~~
8 warnings generated.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2026-11-17 17:21 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-2144-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.