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] [RFC 0/2] gcc 10 disable stringop-overflow warning
Date: Wed, 25 Mar 2020 14:11:35 +0000 [thread overview]
Message-ID: <20200325141137.7088-1-ktraynor@redhat.com> (raw)
This is a blunt way to remove this warning.
Some alternatives are:
- disable the warning for individual components
- components rework to statically allocate memory for parts of structs impacted
Maybe there's some other solutions?
Impacted components:
../drivers/crypto/caam_jr/caam_jr_pvt.h
../drivers/crypto/ccp/ccp_crypto.h
../drivers/crypto/dpaa_sec/dpaa_sec.h
../drivers/crypto/virtio/virtio_cryptodev.h
../drivers/net/enic/base/vnic_dev.c
../drivers/net/iavf/../../common/iavf/virtchnl.h
../drivers/net/ice/base/ice_adminq_cmd.h
../drivers/net/mlx4/mlx4_rxtx.c
../drivers/net/qede/base/ecore_mcp.c
../lib/librte_cryptodev/rte_cryptodev.h
../lib/librte_pipeline/rte_table_action.c
Full details in the Bugzilla:
https://bugs.dpdk.org/show_bug.cgi?id=421
Kevin Traynor (2):
meson: gcc 10 disable stringop-overflow warnings
mk: gcc 10 disable stringop-overflow warnings
config/meson.build | 3 ++-
mk/toolchain/gcc/rte.vars.mk | 3 +++
2 files changed, 5 insertions(+), 1 deletion(-)
--
2.21.1
next reply other threads:[~2020-03-25 14:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 14:11 Kevin Traynor [this message]
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 ` [dpdk-dev] [PATCH] build: gcc 10 disable stringop-overflow warnings Kevin Traynor
2020-04-10 10:51 ` 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=20200325141137.7088-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).