From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 40D66A0A02;
	Thu, 20 May 2021 23:22:15 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id ED18E40143;
	Thu, 20 May 2021 23:22:14 +0200 (CEST)
Received: from sender11-of-o51.zoho.eu (sender11-of-o51.zoho.eu
 [31.186.226.237])
 by mails.dpdk.org (Postfix) with ESMTP id 988AD40041
 for <dev@dpdk.org>; Thu, 20 May 2021 23:22:13 +0200 (CEST)
ARC-Seal: i=1; a=rsa-sha256; t=1621545728; cv=none; d=zohomail.eu; s=zohoarc; 
 b=ahhCBZWiQi1Xce6sWyp0x67rH6VsUGODi3hHiCFbs28ieH4w7YLXBgTOGnZVTRMfJ0gl1TUXSRfb/+X92ITNbQkqrx53y49yIw0Jl10FYlXBwmkkwMkWTvkU86nhBXGkKh1I42Ucv3Si4FwzhtQRXjvXYLeYqu6rcElWswYeE7Y=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.eu;
 s=zohoarc; 
 t=1621545728; h=Content-Type:Cc:Date:From:MIME-Version:Message-ID:Subject:To; 
 bh=TBXPBB4OmWuKnvzr2ocb+tolnuxW8GmtvX0zqWTFNdw=; 
 b=iaNpzTO9PF3d2j0LjeHtCPJPh7vqanyyXWhB24qwkrUu9Dp+fUHpPjep0zQVQanKR+EsT/0C9WJOb5iLRBpi/cAPThiry2CGnUedC9L9D9DoPXz9B3NQcmm5MWErkVXNsFTKA8P+sVhpfbIDoRS3HwRWsEHUymJM8zcEeZJLf4I=
ARC-Authentication-Results: i=1; mx.zohomail.eu;
 spf=pass  smtp.mailfrom=liangma@liangbit.com;
 dmarc=pass header.from=<liangma@liangbit.com>
 header.from=<liangma@liangbit.com>
Received: from DESKTOP-POQV63C.localdomain (64.43.43.102 [64.43.43.102]) by
 mx.zoho.eu with SMTPS id 1621545726798195.88208187480882;
 Thu, 20 May 2021 23:22:06 +0200 (CEST)
Date: Thu, 20 May 2021 22:22:03 +0100
From: Liang Ma <liangma@liangbit.com>
To: dev@dpdk.org
Cc: bruce.richardson@intel.com, thomas@monjalon.net
Message-ID: <20210520212203.GA26@DESKTOP-POQV63C.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.9.4 (2018-02-28)
X-ZohoMailClient: External
Subject: [dpdk-dev] Question Of binutils-avx512-check
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

Hi All, 
   I try to build DPDK with debug  build-type but the building process is
   failed becuase of AVX512 code from librte-acl. The release build type
   is fine. Hence, I dig a bit into the avx512 enabling logic of meson.

   I found the main logic is implemented inside binutils-avx512-check.sh.

   It looks the script focus on checking the compatiblity of tools-chain
   instead of CPUID. My problem is current script will produce avx512
   code even I build dpdk on AMD platform. I understand the avx512 code
   may not be used in runtime. I just wonder why we can not check the
   cpuid as well ?

Regards
Liang