From: Bruce Richardson <bruce.richardson@intel.com>
To: "Wiles, Roger Keith" <keith.wiles@windriver.com>
Cc: "<dev@dpdk.org>" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Building current 1.8.1-rc1 with clang
Date: Tue, 30 Sep 2014 10:34:01 +0100 [thread overview]
Message-ID: <20140930093400.GA18200@BRICHA3-MOBL> (raw)
In-Reply-To: <A07EB24F-3F3B-4783-BE9B-5E5AA0FD08D9@windriver.com>
On Mon, Sep 29, 2014 at 09:50:34PM +0000, Wiles, Roger Keith wrote:
> I just pulled the current repo and stated a build with ‘make install T=x86_64-native-linuxapp-clang’ which produced the following error. I do not think I am allowed to modify this file, correct? If that is the case then someone will have to update the original source. If you want me to submit a patch I can, but I do not think I fully understand what needs to be done.
>
> From what I can tell the line:
> dma_addr0 = _mm_xor_si128(dma_addr0, dma_addr0);
> needs to be:
> dma_addr0 = _mm_setzero_si128();
>
> == Build lib/librte_pmd_ixgbe
> CC ixgbe_common.o
> CC ixgbe_82598.o
> CC ixgbe_82599.o
> CC ixgbe_x540.o
> CC ixgbe_phy.o
> CC ixgbe_api.o
> CC ixgbe_vf.o
> CC ixgbe_dcb.o
> CC ixgbe_dcb_82599.o
> CC ixgbe_dcb_82598.o
> CC ixgbe_mbx.o
> CC ixgbe_rxtx.o
> CC ixgbe_ethdev.o
> CC ixgbe_fdir.o
> CC ixgbe_pf.o
> CC ixgbe_rxtx_vec.o
> /home/keithw/projects/dpdk-code/org-dpdk/lib/librte_pmd_ixgbe/ixgbe_rxtx_vec.c:67:30: error: variable 'dma_addr0' is uninitialized
> when used here [-Werror,-Wuninitialized]
> dma_addr0 = _mm_xor_si128(dma_addr0, dma_addr0);
> ^~~~~~~~~
> /home/keithw/projects/dpdk-code/org-dpdk/lib/librte_pmd_ixgbe/ixgbe_rxtx_vec.c:57:2: note: variable 'dma_addr0' is declared here
> __m128i dma_addr0, dma_addr1;
> ^
> 1 error generated.
> make[5]: *** [ixgbe_rxtx_vec.o] Error 1
> make[4]: *** [librte_pmd_ixgbe] Error 2
> make[3]: *** [lib] Error 2
> make[2]: *** [all] Error 2
> make[1]: *** [x86_64-native-linuxapp-clang_install] Error 2
> make: *** [install] Error 2
>
> Thanks
> ++Keith
>
> Keith Wiles, Principal Technologist with CTO office, Wind River mobile 972-213-5533
>
I think a simple one-line change like below should fix it. The xor can also
be written as a setzero call.
diff --git a/lib/librte_pmd_ixgbe/ixgbe_rxtx_vec.c
b/lib/librte_pmd_ixgbe/ixgbe_rxtx_vec.c
index 457f267..2236250 100644
--- a/lib/librte_pmd_ixgbe/ixgbe_rxtx_vec.c
+++ b/lib/librte_pmd_ixgbe/ixgbe_rxtx_vec.c
@@ -64,7 +64,7 @@ ixgbe_rxq_rearm(struct igb_rx_queue *rxq)
RTE_IXGBE_RXQ_REARM_THRESH) < 0) {
if (rxq->rxrearm_nb + RTE_IXGBE_RXQ_REARM_THRESH >=
rxq->nb_rx_desc) {
- dma_addr0 = _mm_xor_si128(dma_addr0, dma_addr0);
+ dma_addr0 = _mm_setzero_si128();
for (i = 0; i < RTE_IXGBE_DESCS_PER_LOOP; i++) {
rxep[i].mbuf = &rxq->fake_mbuf;
_mm_store_si128((__m128i *)&rxdp[i].read,
/Bruce
next prev parent reply other threads:[~2014-09-30 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 21:50 Wiles, Roger Keith
2014-09-30 9:34 ` Bruce Richardson [this message]
2014-09-30 9:40 ` [dpdk-dev] [PATCH] ixgbe: Fix clang compilation issue Bruce Richardson
2014-09-30 13:46 ` Wiles, Roger Keith
2014-09-30 17:14 ` 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=20140930093400.GA18200@BRICHA3-MOBL \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@windriver.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).