From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Bruce Richardson <bruce.richardson@intel.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>,
dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: [dpdk-dev] [PATCH 1/2] event/octeontx: fix build with icc
Date: Wed, 5 Apr 2017 16:32:09 +0100 [thread overview]
Message-ID: <20170405153210.26513-1-ferruh.yigit@intel.com> (raw)
build error:
.../drivers/event/octeontx/ssovf_worker.c(212):
error #592: variable "get_work0" is used before its value is set
RTE_SET_USED(get_work0);
^
.../drivers/event/octeontx/ssovf_worker.c(213):
error #592: variable "get_work1" is used before its value is set
RTE_SET_USED(get_work1);
^
For x86 these variables set but not used, move macros below
where values assigned.
Fixes: f61808eaa9ad ("event/octeontx: add start function")
Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
drivers/event/octeontx/ssovf_worker.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/event/octeontx/ssovf_worker.c b/drivers/event/octeontx/ssovf_worker.c
index 6a99df0..ad3fe68 100644
--- a/drivers/event/octeontx/ssovf_worker.c
+++ b/drivers/event/octeontx/ssovf_worker.c
@@ -209,9 +209,6 @@ ssows_flush_events(struct ssows *ws, uint8_t queue_id)
uint64_t enable, get_work0, get_work1;
uint8_t *base = octeontx_ssovf_bar(OCTEONTX_SSO_GROUP, queue_id, 0);
- RTE_SET_USED(get_work0);
- RTE_SET_USED(get_work1);
-
enable = ssovf_read64(base + SSO_VHGRP_QCTL);
if (!enable)
return;
@@ -227,6 +224,9 @@ ssows_flush_events(struct ssows *ws, uint8_t queue_id)
cq_ds_cnt &= 0x1FFF1FFF0000;
ssovf_load_pair(get_work0, get_work1, ws->base + reg_off);
}
+
+ RTE_SET_USED(get_work0);
+ RTE_SET_USED(get_work1);
}
void
--
2.9.3
next reply other threads:[~2017-04-05 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 15:32 Ferruh Yigit [this message]
2017-04-05 15:32 ` [dpdk-dev] [PATCH 2/2] event/sw: " Ferruh Yigit
2017-04-05 16:20 ` Thomas Monjalon
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=20170405153210.26513-1-ferruh.yigit@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=thomas.monjalon@6wind.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).