From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1498] warning in hns3 driver with clang and asan
Date: Fri, 19 Jul 2024 17:42:55 +0000 [thread overview]
Message-ID: <bug-1498-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1581 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1498
Bug ID: 1498
Summary: warning in hns3 driver with clang and asan
Product: DPDK
Version: 24.03
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
If build is configured with:
meson setup -Db_sanitize=address -Db_lundef=false build
[1225/2990] Compiling C object drivers..._net_hns3.a.p/net_hns3_hns3_ethdev.c.o
In function ‘hns3_fec_get_internal’,
inlined from ‘hns3_query_dev_fec_info’ at
../drivers/net/hns3/hns3_ethdev.c:6268:8,
inlined from ‘hns3_get_configuration’ at
../drivers/net/hns3/hns3_ethdev.c:2883:8,
inlined from ‘hns3_init_pf’ at ../drivers/net/hns3/hns3_ethdev.c:4630:8,
inlined from ‘hns3_dev_init’ at ../drivers/net/hns3/hns3_ethdev.c:6567:8:
../drivers/net/hns3/hns3_ethdev.c:6061:20: warning: ‘auto_state’ may be used
uninitialized [-Wmaybe-uninitialized]
6061 | if (auto_state == 0x1) {
| ^
../drivers/net/hns3/hns3_ethdev.c: In function ‘hns3_dev_init’:
../drivers/net/hns3/hns3_ethdev.c:6047:17: note: ‘auto_state’ was declared here
6047 | uint8_t auto_state;
| ^~~~~~~~~~
[2990/2990] Linking target app/dpdk-test
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3451 bytes --]
next reply other threads:[~2024-07-19 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 17:42 bugzilla [this message]
2024-07-30 8:01 ` [DPDK/ethdev Bug 1498] warning in hns3 driver with clang and asan bugzilla
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-1498-3@http.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.