From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com
[66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 873F01B1D6;
Mon, 14 Jan 2019 17:29:00 +0100 (CET)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
by mailout.nyi.internal (Postfix) with ESMTP id 1E96A2AC23;
Mon, 14 Jan 2019 11:29:00 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163])
by compute1.internal (MEProxy); Mon, 14 Jan 2019 11:29:00 -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=23A4eqjADZYWvl67/5nE4pyP1ajd9mtR8pHZwnsAA9w=; b=aoYhIN0gm+Q8
pwKRkFQ4CbnOd2w2vevuqaf8k1FbUQUpiaJQzenuNSg/kVJfnBssSfofe5OVee2c
xoUqU6Wh1Vz6iowOQt0M9yyqs5WBXajHx0qStDifW4A1mazegInOm0ICcVRK8niL
YRIRlxRS8LGLdIEs9BkwjL9UzlQEIlg=
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=fm1; bh=23A4eqjADZYWvl67/5nE4pyP1ajd9mtR8pHZwnsAA
9w=; b=samcHz1+iGcqnpUJz8oiGEMDcgLveh77o8hi4ZYG7eDg6h/0Z1npiDiv/
3FwnBJfIVdtNwQp7DVLxbOhSrre/6brIcTj5LUiIHTvd2JrAd+++Su1bQlAJdDhL
fDFZytLnpkHSHq3nfJLbCFOnGBSA4Lq4DjXR6dcACYSlHKJ6yDBgiwPqGntWGg3r
+x1+Ud9v87gQsLx2wVyU3daHATpKVh5scO0zLqv3IMACg4IDtfsSiH9SVfFRVARt
I2M8Pte3mX4Rug8fE8M2BLGpQT0yaf/KsOeDBc/iqSku+inXxkqG30ymI1R4azWb
zvuDYoZHPmBt3ZT5acf0EyDNcNTRw==
X-ME-Sender: <xms:y7g8XGDdtIhGxit_Qsv6n4fdzhbhl4wamMlgdyKBjfyVWI4MSkEkcg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrgedugdeklecutefuodetggdotefrodftvf
curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt
tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvufffkfgjfh
gggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceo
thhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuffhomhgrihhnpeguphgukhdroh
hrghdpghhnuhdrohhrghenucfkphepjeejrddufeegrddvtdefrddukeegnecurfgrrhgr
mhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluh
hsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:y7g8XPAJ0SetAJtUurv4APEd73vjpSvOLB7FSOPWQ5uwQ4zCdG_xYg>
<xmx:y7g8XFEaTapaMaE2RQJmEMpK8tguEp4rSzyjKLquOImrW2VKl2HqsQ>
<xmx:y7g8XO6NoCv-GKhNMfTjryL-4v0-SvaqQ3ZKNyc7qGoMJg-k2yhXfA>
<xmx:zLg8XHE5KhQleCo628UTiRddXQ3U8owFFvPqe_DRnnz5I252Sq53JA>
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
by mail.messagingengine.com (Postfix) with ESMTPA id 0096A100B8;
Mon, 14 Jan 2019 11:28:57 -0500 (EST)
From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>, stable@dpdk.org,
Tom Barbette <barbette@kth.se>, Yongseok Koh <yskoh@mellanox.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Vipin Varghese <vipin.varghese@intel.com>
Date: Mon, 14 Jan 2019 17:28:56 +0100
Message-ID: <2013296.yFTJKXJfz1@xps>
In-Reply-To: <20190114154935.6072-1-ferruh.yigit@intel.com>
References: <20190107164942.88785-1-ferruh.yigit@intel.com>
<20190114154935.6072-1-ferruh.yigit@intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v5] mk: fix scope of disabling
AVX512F support
X-BeenThere: stable@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches for DPDK stable branches <stable.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/stable>,
<mailto:stable-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/stable/>
List-Post: <mailto:stable@dpdk.org>
List-Help: <mailto:stable-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/stable>,
<mailto:stable-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2019 16:29:00 -0000
14/01/2019 16:49, Ferruh Yigit:
> AVX512 was disabled for GCC because of Bugzilla issue 97 [1],
> the GCC defect submitted for the issue [2] highlighted that this is
> a known binutils version 2.30 issue.
>
> Narrowed the scope of no-avx512 to the this specific binutils version.
>
> [1]
> https://bugs.dpdk.org/show_bug.cgi?id=97
>
> [2]
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88096
>
> Fixes: 8d07c82b239f ("mk: disable gcc AVX512F support")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> Cc: Tom Barbette <barbette@kth.se>
> Cc: Thomas Monjalon <thomas@monjalon.net>
> Cc: Yongseok Koh <yskoh@mellanox.com>
> Cc: Konstantin Ananyev <konstantin.ananyev@intel.com>
> Cc: Bruce Richardson <bruce.richardson@intel.com>
>
> v2:
> * Added warning message (print only once for eal)
> * Moved decision details to compat file, kept execution in cpuflags
>
> v3:
> * replace 'ld' with '$(LD)' for cross build
> * added meson support
>
> v4:
> * Document this limitation in release notes
> Cc: Vipin Varghese <vipin.varghese@intel.com>
>
> v5:
> * Grammar fix
> * remove $(lastword.. ) from makefile
> * add 'OR' between possible workarounds
Acked-by: Thomas Monjalon <thomas@monjalon.net>
Applied, thanks