DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] clang compilation errors with clang 4.0
Date: Mon, 17 Apr 2017 15:52:42 +0800	[thread overview]
Message-ID: <20170417075242.GO7333@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <20170414155552.GA24264@bricha3-MOBL3.ger.corp.intel.com>

On Fri, Apr 14, 2017 at 04:55:53PM +0100, Bruce Richardson wrote:
> Hi all,
> 
> just a heads-up that there are compilation errors showing up with
> compiling DPDK with clang 4.0 release. Here are some of the errors I am
> seeing. Volunteers to do patches for some of them welcome.
> 
> Regards,
> /Bruce
> 
> /home/bruce/dpdk.org/lib/librte_eal/common/eal_common_tailqs.c:92:24: warning: taking address of packed member 'qlock' of class or structure 'rte_mem_config' may result in an unaligned pointer value [-Waddress-of-packed-member]
>         rte_rwlock_read_lock(&mcfg->qlock);
>                               ^~~~~~~~~~~
> 
> 
> /home/bruce/dpdk.org/lib/librte_eventdev/rte_eventdev.c:371:6: warning: logical not is only applied to the left hand side of this bitwise operator [-Wlogical-not-parentheses]
>         if (!dev_conf->event_dev_cfg & RTE_EVENT_DEV_CFG_PER_DEQUEUE_TIMEOUT) {
>             ^                        ~
> 
> /home/bruce/dpdk.org/lib/librte_ip_frag/rte_ipv4_reassembly.c:139:31: warning: taking address of packed member 'src_addr' of class or structure 'ipv4_hdr' may result in an unaligned pointer value [-Waddress-of-packed-member]
>         psd = (unaligned_uint64_t *)&ip_hdr->src_addr;
>                                      ^~~~~~~~~~~~~~~~
> 
> /home/bruce/dpdk.org/lib/librte_vhost/vhost_user.c:1037:34: warning: taking address of packed member 'payload' of class or structure 'VhostUserMsg' may result in an unaligned pointer value [-Waddress-of-packed-member]
>                 vhost_user_set_vring_num(dev, &msg.payload.state);
>                                                ^~~~~~~~~~~~~~~~~

Besides the 2nd warnign, all others are the same. Though I'm not quite
sure others, for this vhost-user one, I think it's a false-positive
warning.

	--yliu

      reply	other threads:[~2017-04-17  7:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-14 15:55 Bruce Richardson
2017-04-17  7:52 ` Yuanhan Liu [this message]

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=20170417075242.GO7333@yliu-dev.sh.intel.com \
    --to=yuanhan.liu@linux.intel.com \
    --cc=bruce.richardson@intel.com \
    --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).