From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id E4122A04FA; Thu, 6 Feb 2020 03:23:40 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 25B9B1C20D; Thu, 6 Feb 2020 03:23:40 +0100 (CET) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 698B21C1FA for ; Thu, 6 Feb 2020 03:23:39 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id F112021DC4; Wed, 5 Feb 2020 21:23:38 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 05 Feb 2020 21:23:38 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=PCxtVssOTFKTmYpt/XIBPNTGUS4rovvv/2XHJ1T6kOI=; b=Eqt1Lnll3rbs tvD333WPLDyNI8cGPXtv7KN0omrTZxprtnpaLPcFrkYYUpIV18netuE2NdCpATHo PvTesPZf9jUknlkp7P5mITyztvZGpYvhyhgLrTJJpU6pC1NTHj+af6fSgU0GuNVU EEHWNpgJYRadA+dS/oMfdkWQi3Bhues= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=PCxtVssOTFKTmYpt/XIBPNTGUS4rovvv/2XHJ1T6k OI=; b=hHbum1qsuY7FHtS5QD2MWwo2q6O+ZTZBPqKz9Jyek2hL7o+fgbKYS9gbF 09tNtr/DDCa2gLTgLBrWkFreAfZ7fJS4cA9TI1CHSrDf7FY5JB3465AoTim3RXOS N9q8wQ/FQWSG9Hb8UtpqfO+5rVdgMx+ch6NfFskx9qELJgO5pd2czH8iLdHRcicl wBoR3qhBhQiAxY1uawVeQRc0aOOYko0WT3tMt/602rhDCjl1kxIAS2F6BoBJ3oAj k7iKewJqzbESn89zXQKi3BgFifTaEXcGqJickf+kmasSCXqOPIbXmFyYyfVhCyrD Ln4t+NSOX3KkXFMYQdxdfpCvt1W/g== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrhedvgdegiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghr rghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 53A0B3280063; Wed, 5 Feb 2020 21:23:38 -0500 (EST) From: Thomas Monjalon To: Bruce Richardson Cc: dev@dpdk.org Date: Thu, 06 Feb 2020 03:23:37 +0100 Message-ID: <3125378.usfYGdeWWP@xps> In-Reply-To: <20200124153755.13939-1-bruce.richardson@intel.com> References: <20200124153755.13939-1-bruce.richardson@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH 0/2] remove compiler warnings with icc using meson X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 24/01/2020 16:37, Bruce Richardson: > While icc can compile DPDK successfully using a meson/ninja build, there > are a lot of warnings issued in the process, which means that any use of > werror flag will break the build, and the output just looks messy and > possibly worrying to the user. > > To improve this situation, we can fix the warnings about unsupported > compiler flags, and just maintain a list of icc warnings to ignore. > > Bruce Richardson (2): > net/octeontx2: check compiler flag before use > build: remove warnings for builds with icc Applied, thanks