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 6DCC6A0A02;
	Fri, 21 May 2021 09:57:02 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id D6E8B40143;
	Fri, 21 May 2021 09:57:01 +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 61F4E40041
 for <dev@dpdk.org>; Fri, 21 May 2021 09:57:00 +0200 (CEST)
ARC-Seal: i=1; a=rsa-sha256; t=1621583815; cv=none; d=zohomail.eu; s=zohoarc; 
 b=FFExnCLaWLB3t5KNzJJIVGRpjXXr70iagSEZUt1R3j40/drfRK+bshQ5liI6r+jKwERTCj7pGUS0o6owU7u0Yk2rBUQ+M1TtLrPuVTMoaZq1lKsJn7BbFxOF3Ux1a6CQy4YDFI/M+U8ihxNH3xvFpnzp2Y1cuGocmfLJ9Tp6Zf4=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.eu;
 s=zohoarc; t=1621583815;
 h=Content-Type:Cc:Date:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:To;
 bh=vbZ2wW0BwetBXmqp4RY1ycvZ1w1lqtoFn3mne5TJHfA=; 
 b=C6/V7QkbWQ5hgXbVux4llllOJ0ZHZrM/shnHqivUHHzNOQso2IgDQpl6Of4l4jMbC3KBA3pcB0rdGQRaXONe7HfvWJHcbBzzhjO0oAoPRBJqaQHr+trhO8soN0GLEgUA3j9UxvVHnHzv9qiUyKfZvWr1PBPsdwxFs/OaZkXL/uM=
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 C02F33EJML85 (47.254.128.112 [47.254.128.112]) by mx.zoho.eu
 with SMTPS id 1621583813178424.9484159465492;
 Fri, 21 May 2021 09:56:53 +0200 (CEST)
Date: Fri, 21 May 2021 08:56:50 +0100
From: Liang Ma <liangma@liangbit.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, bruce.richardson@intel.com
Message-ID: <YKdnwqBBwzMt2I1w@C02F33EJML85>
References: <20210520212203.GA26@DESKTOP-POQV63C.localdomain>
 <28959083.qiruW6CpZX@thomas>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <28959083.qiruW6CpZX@thomas>
X-ZohoMailClient: External
Subject: Re: [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>

On Fri, May 21, 2021 at 09:04:06AM +0200, Thomas Monjalon wrote:
> 20/05/2021 23:22, Liang Ma:
> > 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 ?
> 
> The same binary can be run on multiple CPUs,
> so it makes no sense to check the compilation CPUID in generic compilation.
> For native build, why not.
> 
> Anyway, your problem is at compilation, not runtime, right?
Yes, the problem is at compilation. 
Given X86_64, gcc-6.30, Debug build always failed due
to librte_acl AVX512 code. I hope there is a graceful switch allow
developer disable avx512 in certain circumstance.