From: Conor Walsh <conor.walsh@intel.com>
To: jiawenwu@trustnetic.com, jianwang@trustnetic.com
Cc: dev@dpdk.org, linglix.chen@intel.com,
Conor Walsh <conor.walsh@intel.com>
Subject: [dpdk-dev] [PATCH v1] net/txgbe: offset needs to be initialised to fix gcc compile error
Date: Wed, 11 Nov 2020 13:05:42 +0000 [thread overview]
Message-ID: <20201111130542.1949894-1-conor.walsh@intel.com> (raw)
When DPDK is compiled with gcc 7.5 with the optimization level set to 1
gcc sees the offset variable in txgbe_ethdev.c as possibly being
uninitialised. To correct this error offset has been initialised to 0 in
txgbe_ethdev.c
Signed-off-by: Conor Walsh <conor.walsh@intel.com>
---
drivers/net/txgbe/txgbe_ethdev.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/txgbe/txgbe_ethdev.c b/drivers/net/txgbe/txgbe_ethdev.c
index 9f533603a1..7fd56c2698 100644
--- a/drivers/net/txgbe/txgbe_ethdev.c
+++ b/drivers/net/txgbe/txgbe_ethdev.c
@@ -2247,7 +2247,7 @@ txgbe_dev_xstats_get_(struct rte_eth_dev *dev, uint64_t *values,
/* Extended stats from txgbe_hw_stats */
for (i = 0; i < limit; i++) {
- uint32_t offset;
+ uint32_t offset = 0;
if (txgbe_get_offset_by_id(i, &offset)) {
PMD_INIT_LOG(WARNING, "id value %d isn't valid", i);
@@ -2270,7 +2270,7 @@ txgbe_dev_xstats_get_by_id(struct rte_eth_dev *dev, const uint64_t *ids,
return txgbe_dev_xstats_get_(dev, values, limit);
for (i = 0; i < limit; i++) {
- uint32_t offset;
+ uint32_t offset = 0;
if (txgbe_get_offset_by_id(ids[i], &offset)) {
PMD_INIT_LOG(WARNING, "id value %d isn't valid", i);
--
2.25.1
next reply other threads:[~2020-11-11 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 13:05 Conor Walsh [this message]
2020-11-11 13:14 ` Ferruh Yigit
2020-11-11 15:39 ` [dpdk-dev] [PATCH v2] net/txgbe: return changed " Conor Walsh
2020-11-12 15:05 ` Ferruh Yigit
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=20201111130542.1949894-1-conor.walsh@intel.com \
--to=conor.walsh@intel.com \
--cc=dev@dpdk.org \
--cc=jianwang@trustnetic.com \
--cc=jiawenwu@trustnetic.com \
--cc=linglix.chen@intel.com \
/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).