From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/2] mk: fix build for clang 4
Date: Wed, 19 Apr 2017 15:23:44 +0200 [thread overview]
Message-ID: <2941238.rVYzCPaN70@xps> (raw)
In-Reply-To: <20170417143559.11701-1-ferruh.yigit@intel.com>
17/04/2017 16:35, Ferruh Yigit:
> clang 4 gives "taking address of packed member may result in an
> unaligned pointer value" warnings in a few locations [1].
>
> Disabled "-Waddress-of-packed-member" warning for clang >= 4
>
> [1] build errors:
> .../lib/librte_eal/common/eal_common_memzone.c:275:25:
> error: taking address of packed member 'mlock' of class or structure
> 'rte_mem_config' may result in an unaligned pointer value
> [-Werror,-Waddress-of-packed-member]
> rte_rwlock_write_lock(&mcfg->mlock);
> ^~~~~~~~~~~
>
> .../lib/librte_ip_frag/rte_ipv4_reassembly.c:139:31:
> error: taking address of packed member 'src_addr' of class or structure
> 'ipv4_hdr' may result in an unaligned pointer value
> [-Werror,-Waddress-of-packed-member]
> psd = (unaligned_uint64_t *)&ip_hdr->src_addr;
> ^~~~~~~~~~~~~~~~
>
> .../lib/librte_vhost/vhost_user.c:1037:34:
> error: taking address of packed member 'payload' of class or structure
> 'VhostUserMsg' may result in an unaligned pointer value
> [-Werror,-Waddress-of-packed-member]
> vhost_user_set_vring_num(dev, &msg.payload.state);
> ^~~~~~~~~~~~~~~~~
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
Series applied, thanks
next prev parent reply other threads:[~2017-04-19 13:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 14:35 Ferruh Yigit
2017-04-17 14:35 ` [dpdk-dev] [PATCH 2/2] eventdev: " Ferruh Yigit
2017-04-19 13:23 ` Thomas Monjalon [this message]
2024-10-11 17:36 ` [dpdk-dev] [PATCH 1/2] mk: " Morten Brørup
2024-10-11 17:48 ` Stephen Hemminger
2024-10-11 18:20 ` Morten Brørup
2024-10-11 19:07 ` Stephen Hemminger
2024-10-14 7:57 ` Bruce Richardson
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=2941238.rVYzCPaN70@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerin.jacob@caviumnetworks.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).