From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 3FF3AA0096 for ; Wed, 10 Apr 2019 18:45:41 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 312651B123; Wed, 10 Apr 2019 18:45:41 +0200 (CEST) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 421AA1B150 for ; Wed, 10 Apr 2019 18:45:40 +0200 (CEST) Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id ABFEF30F8DA1; Wed, 10 Apr 2019 16:45:39 +0000 (UTC) Received: from rh.redhat.com (ovpn-117-94.ams2.redhat.com [10.36.117.94]) by smtp.corp.redhat.com (Postfix) with ESMTP id A9B645D962; Wed, 10 Apr 2019 16:45:38 +0000 (UTC) From: Kevin Traynor To: Jerin Jacob Cc: Ferruh Yigit , dpdk stable Date: Wed, 10 Apr 2019 17:43:53 +0100 Message-Id: <20190410164411.10546-45-ktraynor@redhat.com> In-Reply-To: <20190410164411.10546-1-ktraynor@redhat.com> References: <20190410164411.10546-1-ktraynor@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.49]); Wed, 10 Apr 2019 16:45:39 +0000 (UTC) Subject: [dpdk-stable] patch 'mk: fix AVX512 disabled warning on non x86' has been queued to LTS release 18.11.2 X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 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 Sender: "stable" Hi, FYI, your patch has been queued to LTS release 18.11.2 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 04/16/19. So please shout if anyone has objections. Also note that after the patch there's a diff of the upstream commit vs the patch applied to the branch. This will indicate if there was any rebasing needed to apply to the stable branch. If there were code changes for rebasing (ie: not only metadata diffs), please double check that the rebase was correctly done. Thanks. Kevin Traynor --- >From d6d558dd0f8babb7fa31d56e821b15b1fafce9bf Mon Sep 17 00:00:00 2001 From: Jerin Jacob Date: Sun, 24 Feb 2019 18:27:10 +0000 Subject: [PATCH] mk: fix AVX512 disabled warning on non x86 [ upstream commit 0c3b8a2c7d7d8ea713d252127059d1bd08eb0f5e ] AVX512 is a x86 specific feature, So, enable AVX512 warning only on x86. Fixes: a32ca9a4ebc1 ("mk: fix scope of disabling AVX512F support") Signed-off-by: Jerin Jacob Reviewed-by: Ferruh Yigit --- mk/toolchain/gcc/rte.toolchain-compat.mk | 2 ++ 1 file changed, 2 insertions(+) diff --git a/mk/toolchain/gcc/rte.toolchain-compat.mk b/mk/toolchain/gcc/rte.toolchain-compat.mk index dbddc986e..df71e4a8b 100644 --- a/mk/toolchain/gcc/rte.toolchain-compat.mk +++ b/mk/toolchain/gcc/rte.toolchain-compat.mk @@ -23,4 +23,5 @@ HOST_GCC_VERSION = $(HOST_GCC_MAJOR)$(HOST_GCC_MINOR) LD_VERSION = $(shell $(LD) -v) # disable AVX512F support for GCC & binutils 2.30 as a workaround for Bug 97 +ifeq ($(CONFIG_RTE_ARCH_X86), y) ifneq ($(filter 2.30%,$(LD_VERSION)),) FORCE_DISABLE_AVX512 := y @@ -30,4 +31,5 @@ $(warning AVX512 support disabled because of ld 2.30. See Bug 97) endif endif +endif # if GCC is older than 4.x -- 2.20.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2019-04-10 14:06:11.337744096 +0100 +++ 0045-mk-fix-AVX512-disabled-warning-on-non-x86.patch 2019-04-10 14:06:07.984291496 +0100 @@ -1,13 +1,14 @@ -From 0c3b8a2c7d7d8ea713d252127059d1bd08eb0f5e Mon Sep 17 00:00:00 2001 +From d6d558dd0f8babb7fa31d56e821b15b1fafce9bf Mon Sep 17 00:00:00 2001 From: Jerin Jacob Date: Sun, 24 Feb 2019 18:27:10 +0000 Subject: [PATCH] mk: fix AVX512 disabled warning on non x86 +[ upstream commit 0c3b8a2c7d7d8ea713d252127059d1bd08eb0f5e ] + AVX512 is a x86 specific feature, So, enable AVX512 warning only on x86. Fixes: a32ca9a4ebc1 ("mk: fix scope of disabling AVX512F support") -Cc: stable@dpdk.org Signed-off-by: Jerin Jacob Reviewed-by: Ferruh Yigit