patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Bruce Richardson <bruce.richardson@intel.com>, stable@dpdk.org
Cc: xuemingx.zhang@intel.com
Subject: Re: [dpdk-stable] [PATCH 17.11] mk: disable warnings for packed mem config data structure
Date: Tue, 24 Sep 2019 19:17:18 +0100	[thread overview]
Message-ID: <28bdfe106d4aba2f6b3c9d070dfbc727c4484471.camel@debian.org> (raw)
In-Reply-To: <20190902144239.11292-1-bruce.richardson@intel.com>

On Mon, 2019-09-02 at 15:42 +0100, Bruce Richardson wrote:
> The rte_mem_config data structure is marked as packed, but we access
> members of that structure via pointers in the code. This leads to
> warnings
> with later gcc compilers e.g. gcc9, so disable those warnings to
> allow
> clean builds.
> 
> For older GCC versions, which may not have the flag, there is no need
> to
> filter it out as adding unrecognised warning disable flags to GCC is
> always
> safe [Ref: 
> https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html
> ]
> 
> Signed-off-by: Bruce Richardson <
> bruce.richardson@intel.com
> >
> ---
>  mk/toolchain/gcc/rte.vars.mk | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/mk/toolchain/gcc/rte.vars.mk
> b/mk/toolchain/gcc/rte.vars.mk
> index e7008c052..ec082db99 100644
> --- a/mk/toolchain/gcc/rte.vars.mk
> +++ b/mk/toolchain/gcc/rte.vars.mk
> @@ -81,6 +81,8 @@ ifeq ($(RTE_DEVEL_BUILD),y)
>  WERROR_FLAGS += -Werror
>  endif
>  
> +WERROR_FLAGS += -Wno-address-of-packed-member
> +
>  # There are many issues reported for strict alignment architectures
>  # which are not necessarily fatal. Report as warnings.
>  ifeq ($(CONFIG_RTE_ARCH_STRICT_ALIGN),y)

Acked-by: Luca Boccassi <luca.boccassi@microsoft.com>

Thanks Bruce, applied and pushed.

-- 
Kind regards,
Luca Boccassi

      reply	other threads:[~2019-09-24 18:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-02 14:42 Bruce Richardson
2019-09-24 18:17 ` Luca Boccassi [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=28bdfe106d4aba2f6b3c9d070dfbc727c4484471.camel@debian.org \
    --to=bluca@debian.org \
    --cc=bruce.richardson@intel.com \
    --cc=stable@dpdk.org \
    --cc=xuemingx.zhang@intel.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).