From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] mk: fix scope of disabling AVX512F support Date: Wed, 19 Dec 2018 20:58:26 +0100 Message-ID: <1772993.ZpFq8iN2Ki@xps> References: <20181219192904.61934-1-ferruh.yigit@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, stable@dpdk.org, Tom Barbette , Yongseok Koh , Konstantin Ananyev , Bruce Richardson To: Ferruh Yigit Return-path: In-Reply-To: <20181219192904.61934-1-ferruh.yigit@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 19/12/2018 20:29, 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. [...] > # disable AVX512F support of gcc as a workaround for Bug 97 > ifeq ($(CONFIG_RTE_TOOLCHAIN_GCC),y) > +ifneq ($(filter 2.30%,$(LD_VERSION)),) > MACHINE_CFLAGS += -mno-avx512f I think we should print a warning here. There is a function $(warning) or $(info) for such case.