From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 560F2A054D for ; Tue, 7 Jun 2022 17:13:23 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 4708B4021D; Tue, 7 Jun 2022 17:13:23 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id D3F1A40156 for ; Tue, 7 Jun 2022 17:13:21 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1654614801; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=2VfnWUbUC97cB0vLl1Sc0RUYXqF4rKdpnrXOddl9kAo=; b=VwGJzK2ekwJokMxuzjVta+R3KCkcKkYgtrrUfQuc+hPlASdDVzhp20Ff8rl8Imra1Gx8Lb 2bTSBIktWpPQ1Se16p3Dp8E0FrijCcOLBMkqqxCjB3K0/T7b7qYCWzHGeVZYwi8IVOR258 4YZE5Yo8eiLCd6+tzO7rSG0D6kIM/sU= Received: from mail-lj1-f197.google.com (mail-lj1-f197.google.com [209.85.208.197]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-616-GAbT9XJjPSSXWmGljW0-lQ-1; Tue, 07 Jun 2022 11:13:20 -0400 X-MC-Unique: GAbT9XJjPSSXWmGljW0-lQ-1 Received: by mail-lj1-f197.google.com with SMTP id bn32-20020a05651c17a000b00253e2b131d3so3160564ljb.6 for ; Tue, 07 Jun 2022 08:13:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2VfnWUbUC97cB0vLl1Sc0RUYXqF4rKdpnrXOddl9kAo=; b=NDcSXn+6EHt/cvwJJsBsaXgEnNT/4vW7r2T4d65xNqlUjWUc7V5vIzNFTOjH5JvGW+ vH53fnmLOdLHz+/rtANLRtHd3ZTMCbSZB/lFQDAMpBPv9uHH8Km4bPpu1DV8Yh23gqrx 1gLG90cJJmjWl+82uU1E+NTi5TOV0DJQzhAkfmSmOoUVH9vYml40LpWt1yljsGE8eiS4 b9ckBv24QiEYpA9Yu7uZOFSC3Tv+3Wxb3MG7KggOF09cxjat+kKDF/rOYrSQSeuphT42 b+goMRVuTke7Lb8bJ9bOsgCRfVB4HnGDWZicsO974M4EK8kJQKsVTMyhn3KHHwVpTqcv LxJw== X-Gm-Message-State: AOAM531ZB0dWgdht2PWF1QoJn9I4lBBwFTVdUdYIGxVGSJ+CiRRsmJx8 sgSccyiIUZ5rZQNWgkJ+vO46y/pkpUvNDD4ZptebCVOji8/kps2rbdD+J9XNc1N89jvClec6ocf sBIZ2BglXyzOeuJaTo7nwwIU= X-Received: by 2002:a05:651c:1781:b0:247:daa7:4358 with SMTP id bn1-20020a05651c178100b00247daa74358mr53946083ljb.477.1654614798874; Tue, 07 Jun 2022 08:13:18 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx2PY3B5bzWneEvNvHRhaytQDQCVEhktARhU9bWoMu8zlqk8DlHa75Z1BeMAESyiYCCrixII/RLc9t47p5zHSk= X-Received: by 2002:a05:651c:1781:b0:247:daa7:4358 with SMTP id bn1-20020a05651c178100b00247daa74358mr53946072ljb.477.1654614798676; Tue, 07 Jun 2022 08:13:18 -0700 (PDT) MIME-Version: 1.0 References: <20220607025652.1114683-1-wenxuanx.wu@intel.com> <26640576.6Emhk5qWAg@thomas> <20220607080953.1f35df17@hermes.local> In-Reply-To: <20220607080953.1f35df17@hermes.local> From: David Marchand Date: Tue, 7 Jun 2022 17:13:07 +0200 Message-ID: Subject: Re: [PATCH] build: fix meson build when gcc >= 10.0 To: Stephen Hemminger Cc: Thomas Monjalon , Wenxuan Wu , Bruce Richardson , dev , dpdk stable Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dmarchan@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org On Tue, Jun 7, 2022 at 5:10 PM Stephen Hemminger wrote: > On Tue, 07 Jun 2022 12:52:32 +0200 > Thomas Monjalon wrote: > > 07/06/2022 04:56, wenxuanx.wu@intel.com: > > > From: Wenxuan Wu > > > > > > 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. > > > > > > Agree with Thomas. This not how to address this. > There are fixes already for the zero-length-bounds that are being merged. I just merged them, though, afaics, they fix none of the compilation issues reported with gcc 12. -- David Marchand