From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 452] cuckoo hash gcc10 warning
Date: Fri, 17 Apr 2020 19:04:06 +0000 [thread overview]
Message-ID: <bug-452-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=452
Bug ID: 452
Summary: cuckoo hash gcc10 warning
Product: DPDK
Version: 20.05
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: kevuzaj@gmail.com
Target Milestone: ---
[1/83] Compiling C object
'lib/76b5a35@@rte_hash@sta/librte_hash_rte_cuckoo_hash.c.o'
../lib/librte_hash/rte_cuckoo_hash.c: In function
‘__rte_hash_add_key_with_hash’:
../lib/librte_hash/rte_cuckoo_hash.c:1104:29: warning: ‘ext_bkt_id’ may be used
uninitialized in this function [-Wmaybe-uninitialized]
1104 | (h->buckets_ext[ext_bkt_id - 1]).sig_current[0] = short_sig;
| ~~~~~~~~~~~^~~
Relevant code:
if (rte_ring_sc_dequeue_elem(h->free_ext_bkts, &ext_bkt_id,
sizeof(uint32_t)) != 0) {
ret = -ENOSPC;
goto failure;
}
/* Use the first location of the new bucket */
(h->buckets_ext[ext_bkt_id - 1]).sig_current[0] = short_sig;
--
I'm not seeing the path that where rte_ring_sc_dequeue_elem() return !=0 and
ext_bkt_id has not been initialized but gcc10 seems to think there is one.
Initializing ext_bkt_id = 1 earlier in the function would fix this.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-04-17 19:04 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-452-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 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 NNTP newsgroup(s).