DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: dev@dpdk.org, thomas@monjalon.net, bruce.richardson@intel.com
Cc: ravi1.kumar@amd.com, g.singh@nxp.com, hemant.agrawal@nxp.com,
	akhil.goyal@nxp.com, johndale@cisco.com, hyonkim@cisco.com,
	jingjing.wu@intel.com, wenzhuo.lu@intel.com, rmody@marvell.com,
	shshaikh@marvell.com, matan@mellanox.com, shahafs@mellanox.com,
	declan.doherty@intel.com, cristian.dumitrescu@intel.com,
	Kevin Traynor <ktraynor@redhat.com>
Subject: [dpdk-dev] [PATCH] build: gcc 10 disable stringop-overflow warnings
Date: Tue,  7 Apr 2020 17:27:55 +0100	[thread overview]
Message-ID: <20200407162755.6802-1-ktraynor@redhat.com> (raw)
In-Reply-To: <20200325141137.7088-1-ktraynor@redhat.com>

stringop-overflow warns when it sees a possible overflow
in a string operation.

In the rte_memcpy functions different implementations are
used depending on the size. stringop-overflow is raised for
the paths in the function where it sees the static size of the
src could be overflowed.

However, in reality a correct size argument and in some cases
dynamic allocation would ensure that this does not happen.

Disable this warning at the top level as it is being raised on
several components.

For example, in the case below for key, the correct path will be
chosen in rte_memcpy_generic at runtime based on the size argument
but as some paths in the function could lead to a cast to 32 bytes
a warning is raised.

In function ‘_mm256_storeu_si256’,
inlined from ‘rte_memcpy_generic’
at ../lib/librte_eal/common/include/arch/x86/rte_memcpy.h:315:2,
inlined from ‘iavf_configure_rss_key’
at ../lib/librte_eal/common/include/arch/x86/rte_memcpy.h:869:10:

/usr/lib/gcc/x86_64-redhat-linux/10/include/avxintrin.h:928:8:
warning: writing 32 bytes into a region of size 1 [-Wstringop-overflow=]
  928 |   *__P = __A;
      |   ~~~~~^~~~~
In file included
from ../drivers/net/iavf/../../common/iavf/iavf_prototype.h:10,
from ../drivers/net/iavf/iavf.h:9,
from ../drivers/net/iavf/iavf_vchnl.c:22:

../drivers/net/iavf/iavf_vchnl.c:
In function ‘iavf_configure_rss_key’:

../drivers/net/iavf/../../common/iavf/virtchnl.h:508:5:
note: at offset 0 to object ‘key’ with size 1 declared here
  508 |  u8 key[1];         /* RSS hash key, packed bytes */
      |     ^~~

Bugzilla ID: 394
Bugzilla ID: 421

Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
---
 config/meson.build           | 3 ++-
 mk/toolchain/gcc/rte.vars.mk | 3 +++
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/config/meson.build b/config/meson.build
index 58421342b..476a667a9 100644
--- a/config/meson.build
+++ b/config/meson.build
@@ -200,5 +200,6 @@ warning_flags = [
 	'-Wno-address-of-packed-member',
 	'-Wno-packed-not-aligned',
-	'-Wno-missing-field-initializers'
+	'-Wno-missing-field-initializers',
+	'-Wno-stringop-overflow'
 ]
 if not dpdk_conf.get('RTE_ARCH_64')
diff --git a/mk/toolchain/gcc/rte.vars.mk b/mk/toolchain/gcc/rte.vars.mk
index f19305e49..fe4b8c705 100644
--- a/mk/toolchain/gcc/rte.vars.mk
+++ b/mk/toolchain/gcc/rte.vars.mk
@@ -101,4 +101,7 @@ endif
 WERROR_FLAGS += -Wno-address-of-packed-member
 
+# disable stringop-overflow warnings
+WERROR_FLAGS += -Wno-stringop-overflow
+
 export CC AS AR LD OBJCOPY OBJDUMP STRIP READELF
 export TOOLCHAIN_CFLAGS TOOLCHAIN_LDFLAGS TOOLCHAIN_ASFLAGS
-- 
2.21.1


  parent reply	other threads:[~2020-04-07 16:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 14:11 [dpdk-dev] [RFC 0/2] gcc 10 disable stringop-overflow warning Kevin Traynor
2020-03-25 14:11 ` [dpdk-dev] [RFC 1/2] meson: gcc 10 disable stringop-overflow warnings Kevin Traynor
2020-03-25 14:11 ` [dpdk-dev] [RFC 2/2] mk: " Kevin Traynor
2020-03-25 14:18 ` [dpdk-dev] [RFC 0/2] gcc 10 disable stringop-overflow warning Thomas Monjalon
2020-03-31 14:08   ` Kevin Traynor
2020-03-31 14:53     ` Stephen Hemminger
2020-04-01 11:33       ` Kevin Traynor
2020-04-07 16:27 ` Kevin Traynor [this message]
2020-04-10 10:51   ` [dpdk-dev] [PATCH] build: gcc 10 disable stringop-overflow warnings Kevin Traynor
2020-04-10 13:23     ` Bruce Richardson
2020-04-16 18:43       ` Kevin Traynor
2020-04-16 18:45   ` [dpdk-dev] [PATCH v2] x86/eal: gcc 10 ignore " Kevin Traynor
2020-04-17  9:33     ` Bruce Richardson
2020-04-17 10:13       ` Thomas Monjalon
2020-04-17 14:50         ` Kevin Traynor
2020-04-17 12:40       ` Kevin Traynor
2020-04-17 15:43     ` [dpdk-dev] [PATCH v3] " Kevin Traynor
2020-05-06  9:20       ` David Marchand

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=20200407162755.6802-1-ktraynor@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=akhil.goyal@nxp.com \
    --cc=bruce.richardson@intel.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=g.singh@nxp.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=hyonkim@cisco.com \
    --cc=jingjing.wu@intel.com \
    --cc=johndale@cisco.com \
    --cc=matan@mellanox.com \
    --cc=ravi1.kumar@amd.com \
    --cc=rmody@marvell.com \
    --cc=shahafs@mellanox.com \
    --cc=shshaikh@marvell.com \
    --cc=thomas@monjalon.net \
    --cc=wenzhuo.lu@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).