DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Ferruh Yigit" <ferruh.yigit@amd.com>,
	"Stephen Hemminger" <stephen@networkplumber.org>,
	"Robin Jarry" <rjarry@redhat.com>
Cc: <dev@dpdk.org>, "Robin Jarry" <rjarry@redhat.com>,
	"Wathsala Vithanage" <wathsala.vithanage@arm.com>,
	"Min Zhou" <zhoumin@loongson.cn>,
	"David Christensen" <drc@linux.ibm.com>,
	"Stanislaw Kardach" <stanislaw.kardach@gmail.com>,
	<bruce.richardson@intel.com>, <konstantin.v.ananyev@yandex.ru>,
	"Vipin Varghese" <vipin.varghese@amd.com>,
	"Thomas Monjalon" <thomas.monjalon@6wind.com>,
	"Jerin Jacob" <jerinj@marvell.com>
Subject: RE: [dpdk-dev] [PATCH 1/2] mk: fix build for clang 4
Date: Fri, 11 Oct 2024 19:36:08 +0200	[thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9F7C6@smartserver.smartshare.dk> (raw)
In-Reply-To: <20170417143559.11701-1-ferruh.yigit@intel.com>

> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ferruh Yigit
> Sent: Monday, 17 April 2017 16.36
> 
> 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>
> ---
>  mk/toolchain/clang/rte.vars.mk | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/mk/toolchain/clang/rte.vars.mk
> b/mk/toolchain/clang/rte.vars.mk
> index 7749b99..af34c10 100644
> --- a/mk/toolchain/clang/rte.vars.mk
> +++ b/mk/toolchain/clang/rte.vars.mk
> @@ -79,5 +79,10 @@ include
> $(RTE_SDK)/mk/toolchain/$(RTE_TOOLCHAIN)/rte.toolchain-compat.mk
>  # workaround clang bug with warning "missing field initializer" for "=
> {0}"
>  WERROR_FLAGS += -Wno-missing-field-initializers
> 
> +# disable packed member unalign warnings
> +ifeq ($(shell test $(CLANG_MAJOR_VERSION) -ge 4 && echo 1), 1)
> +WERROR_FLAGS += -Wno-address-of-packed-member
> +endif
> +
>  export CC AS AR LD OBJCOPY OBJDUMP STRIP READELF
>  export TOOLCHAIN_CFLAGS TOOLCHAIN_LDFLAGS TOOLCHAIN_ASFLAGS
> --
> 2.9.3
> 

Revisiting an old patch...

Maybe the code causing the warnings should have been fixed instead of disabling the compiler warning?

We would probably handle this differently today... I wonder how many warnings it spews out with the warning enabled?

-Morten


  parent reply	other threads:[~2024-10-11 17:36 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 ` [dpdk-dev] [PATCH 1/2] mk: " Thomas Monjalon
2024-10-11 17:36 ` Morten Brørup [this message]
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=98CBD80474FA8B44BF855DF32C47DC35E9F7C6@smartserver.smartshare.dk \
    --to=mb@smartsharesystems.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=drc@linux.ibm.com \
    --cc=ferruh.yigit@amd.com \
    --cc=jerinj@marvell.com \
    --cc=konstantin.v.ananyev@yandex.ru \
    --cc=rjarry@redhat.com \
    --cc=stanislaw.kardach@gmail.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas.monjalon@6wind.com \
    --cc=vipin.varghese@amd.com \
    --cc=wathsala.vithanage@arm.com \
    --cc=zhoumin@loongson.cn \
    /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).