From: "Zhang, XuemingX" <xuemingx.zhang@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
Raslan Darawsheh <rasland@mellanox.com>
Cc: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>,
Karra Satwik <kaara.satwik@chelsio.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/cxgbe: fix build with clang 3.4.2
Date: Thu, 19 Mar 2020 07:31:20 +0000 [thread overview]
Message-ID: <1bfe1b0ed41347808c3eae51eb261f31@intel.com> (raw)
In-Reply-To: <511c9de6-1543-47b5-3be4-9525130bbe59@intel.com>
Many thanks Ferruh.
In dpdk-next-net and dpdk-next-net-intel, the patch verified.
>-----Original Message-----
>From: Yigit, Ferruh
>Sent: Wednesday, March 18, 2020 9:10 PM
>To: Raslan Darawsheh <rasland@mellanox.com>; Zhang, XuemingX
><xuemingx.zhang@intel.com>
>Cc: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>; Karra Satwik
><kaara.satwik@chelsio.com>; dev@dpdk.org
>Subject: Re: [PATCH] net/cxgbe: fix build with clang 3.4.2
>
>On 3/18/2020 12:52 PM, Ferruh Yigit wrote:
>> Build error:
>> .../drivers/net/cxgbe/cxgbe_flow.c:315:2:
>> error: implicit truncation from 'int' to bitfield changes
>value
>> from -1 to 7 [-Werror,-Wbitfield-constant-conversion]
>> CXGBE_FILL_FS(adap->pf, ~0, pf);
>> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> .../drivers/net/cxgbe/cxgbe_flow.c:25:2:
>> note: expanded from macro 'CXGBE_FILL_FS'
>> __CXGBE_FILL_FS(v, m, fs, elem, e)
>> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> .../drivers/net/cxgbe/cxgbe_flow.c:15:18: note:
>> expanded from macro '__CXGBE_FILL_FS'
>> (fs)->mask.elem = (__m); \
>> ^ ~~~~~
>> Commit in fixes line changes 'PF_BITWIDTH' to '3', which makes
>'fs->pf'
>> bitfield size '3', changing '~0' to '0x7' to prevent truncation in
>> assignment.
>>
>> Fixes: dcd456abe46f ("net/cxgbe: support flow API for matching all
>> packets on PF")
>>
>> Reported-by: Raslan Darawsheh <rasland@mellanox.com>
>> Reported-by: Xueming Zhang <xuemingx.zhang@intel.com>
>> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
>
>Hi Raslan, Xueming,
>
>Can you please confirm the above patch on top of next-net fixes the
>build issue?
>
>Thanks,
>ferruh
next prev parent reply other threads:[~2020-03-19 7:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 12:52 Ferruh Yigit
2020-03-18 13:09 ` Ferruh Yigit
2020-03-19 7:31 ` Zhang, XuemingX [this message]
2020-03-18 13:48 ` Rahul Lakkireddy
2020-03-18 14:46 ` Raslan Darawsheh
2020-03-18 14:48 ` 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=1bfe1b0ed41347808c3eae51eb261f31@intel.com \
--to=xuemingx.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=kaara.satwik@chelsio.com \
--cc=rahul.lakkireddy@chelsio.com \
--cc=rasland@mellanox.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).