DPDK patches and discussions
 help / color / mirror / Atom feed
From: wenxuanx.wu@intel.com
To: bruce.richardson@intel.com, dev@dpdk.org
Cc: Wenxuan Wu <wenxuanx.wu@intel.com>, stable@dpdk.org
Subject: [PATCH] build: fix meson build when gcc >= 10.0
Date: Tue,  7 Jun 2022 02:56:52 +0000	[thread overview]
Message-ID: <20220607025652.1114683-1-wenxuanx.wu@intel.com> (raw)

From: Wenxuan Wu <wenxuanx.wu@intel.com>

GCC version greater than 10.0, with compile option -O2, several warnings info would appear,
this fix omitted these warnings.

Fixes: cfacbcb5a23b ("build: disable gcc 10 zero-length-bounds warning")
Cc: stable@dpdk.org

Signed-off-by: Wenxuan Wu <wenxuanx.wu@intel.com>
---
 config/meson.build | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/config/meson.build b/config/meson.build
index 7134e80e8d..97f0ea6cca 100644
--- a/config/meson.build
+++ b/config/meson.build
@@ -273,7 +273,12 @@ warning_flags = [
 ]
 if cc.get_id() == 'gcc' and cc.version().version_compare('>=10.0')
 # FIXME: Bugzilla 396
-    warning_flags += '-Wno-zero-length-bounds'
+    warning_flags += [
+      '-Wno-zero-length-bounds',
+      '-Wno-stringop-overflow',
+      '-Wno-array-bounds',
+      '-Wno-format-overflow',
+      ]
 endif
 if not dpdk_conf.get('RTE_ARCH_64')
 # for 32-bit, don't warn about casting a 32-bit pointer to 64-bit int - it's fine!!
-- 
2.25.1


             reply	other threads:[~2022-06-07  3:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07  2:56 wenxuanx.wu [this message]
2022-06-07 10:52 ` Thomas Monjalon
2022-06-07 15:09   ` Stephen Hemminger
2022-06-07 15:13     ` David Marchand
2022-06-07 15:25       ` Stephen Hemminger
2022-06-08  3:27   ` Wu, WenxuanX

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=20220607025652.1114683-1-wenxuanx.wu@intel.com \
    --to=wenxuanx.wu@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    /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).