From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id A6F37A0544;
	Tue,  7 Jun 2022 12:52:39 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 54392406B4;
	Tue,  7 Jun 2022 12:52:39 +0200 (CEST)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com
 [64.147.123.21])
 by mails.dpdk.org (Postfix) with ESMTP id 71C6D4021D;
 Tue,  7 Jun 2022 12:52:38 +0200 (CEST)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45])
 by mailout.west.internal (Postfix) with ESMTP id E97D132009A5;
 Tue,  7 Jun 2022 06:52:36 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163])
 by compute5.internal (MEProxy); Tue, 07 Jun 2022 06:52:37 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
 cc:cc:content-transfer-encoding:content-type:date:date:from:from
 :in-reply-to:in-reply-to:message-id:mime-version:references
 :reply-to:sender:subject:subject:to:to; s=fm2; t=1654599156; x=
 1654685556; bh=1wJsTijNO2voVRn5Ft5sPqJL+o+OHw+ZVvBUGi8pYVc=; b=X
 WUFawwR6sPpN3SFdbl53h28/wlJdMc8qz4Y5jpAJdkUFQ/62+nmPUE0/EMJx+OAY
 sKAcgP5su8/I8cI1q/igPpBtBEnxLjUKAHjQN+MaqV8TAX8htrRF7WLBO6Oe93Kh
 BXGT+EktQvOacL96yyurGOiZSx2eNTrWVlV2OYZgPCBVTNM2jCWqds4YxC7vztOU
 KisKWdXHL0T/RBTRw8Skla0qOZ1mED7xQwX0JG732jkRr1kH8W4wFjnYUtcVBJoI
 afpbHdUhEUHjS/wyEdBUCA6VyIhjvXeWMtjA5eDCPdaUYyzl8kkhT9JcZx3YbBnP
 APaTih9U8FBnwPJrNYocw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:cc:content-transfer-encoding
 :content-type:date:date:feedback-id:feedback-id:from:from
 :in-reply-to:in-reply-to:message-id:mime-version:references
 :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy
 :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1654599156; x=
 1654685556; bh=1wJsTijNO2voVRn5Ft5sPqJL+o+OHw+ZVvBUGi8pYVc=; b=v
 h3tcrQ7RJcsn0FVnBdXRzTyj1XYHpiPCEa4p7qzUcREy7d1vGqvce+ClZrtKUt0s
 OmrY4LEqG7VhCVbs1bJ76b+tQRnHFFKHEhtLfO3LaCW8IuGHPFzonYYtDqnzbfho
 i/oyjtuPc1325GDHeSnGhjpC0M35nwX8opLuIA5D2Xb8TiixmEhMZR6R/3PdPIlC
 UjHj3Ts6yGoXFq3xD1zp2pEFVysW67L+7mn+g0KqAS96UPGNT72zlznTq3kaTMo1
 F7aYTgUYlIidFC9tg6Ct+urzwwn1FJx8Q/5xrY+lEdC6XzfCo5WuBJIdZ4+3+6Ed
 eg+N0UBHZF8UG/ssyd00w==
X-ME-Sender: <xms:9C2fYlArTWrbwAbyVmwov3J6EiVaH7up-dUfiJTpUMsV3oY1CWnzUg>
 <xme:9C2fYjhtey2llYPubVZDa0tfsmluGpzRFGjI0X9XrWddPZR3w7MhPCKJvdd_FYU0y
 4hWhUwmxSBpO4QOIQ>
X-ME-Received: <xmr:9C2fYgkprnhDZDGyPTq2krZDMW6XFfkr3_WInHuZ1LZKVcms4C5LS0qq4qnUSqfdW-QWAkTmyvKFzryZ5jUeTJ9YJw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedruddthedgfedvucetufdoteggodetrfdotf
 fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen
 uceurghilhhouhhtmecufedttdenucenucfjughrpefhvfevufffkfgjfhgggfgtsehtuf
 ertddttddvnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghs
 sehmohhnjhgrlhhonhdrnhgvtheqnecuggftrfgrthhtvghrnheptdejieeifeehtdffgf
 dvleetueeffeehueejgfeuteeftddtieekgfekudehtdfgnecuvehluhhsthgvrhfuihii
 vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonh
 drnhgvth
X-ME-Proxy: <xmx:9C2fYvz6NMJE6zvLfG00eOQaGQHRLMzo_cZdTDJmzjSbTMpliRUsIA>
 <xmx:9C2fYqQJoW6JNSgz1UqVIpiR-m661SPN3c93iuBRW4yyCiO93qPXmA>
 <xmx:9C2fYiYPUWXcA5EEJHUzXdHeKaKMQ5xyLtpYUUgm9jIhybaPdiO6Qg>
 <xmx:9C2fYofzARg_AK_jPza9WV28wE9yfjD5mOkzvN6gCB6lIgCky4Fk5Q>
Feedback-ID: i47234305:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue,
 7 Jun 2022 06:52:35 -0400 (EDT)
From: Thomas Monjalon <thomas@monjalon.net>
To: Wenxuan Wu <wenxuanx.wu@intel.com>
Cc: bruce.richardson@intel.com, dev@dpdk.org, stable@dpdk.org,
 david.marchand@redhat.com
Subject: Re: [PATCH] build: fix meson build when gcc >= 10.0
Date: Tue, 07 Jun 2022 12:52:32 +0200
Message-ID: <26640576.6Emhk5qWAg@thomas>
In-Reply-To: <20220607025652.1114683-1-wenxuanx.wu@intel.com>
References: <20220607025652.1114683-1-wenxuanx.wu@intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org

07/06/2022 04:56, wenxuanx.wu@intel.com:
> 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.
[...]
>  # FIXME: Bugzilla 396
> -    warning_flags += '-Wno-zero-length-bounds'
> +    warning_flags += [
> +      '-Wno-zero-length-bounds',
> +      '-Wno-stringop-overflow',
> +      '-Wno-array-bounds',
> +      '-Wno-format-overflow',

The compilers are reported warnings to help us having a better code.
We should try to resolve the warnings, not hiding them.