From: Liang Ma <liangma@liangbit.com>
To: dev@dpdk.org
Cc: bruce.richardson@intel.com, thomas@monjalon.net
Subject: [dpdk-dev] Question Of binutils-avx512-check
Date: Thu, 20 May 2021 22:22:03 +0100 [thread overview]
Message-ID: <20210520212203.GA26@DESKTOP-POQV63C.localdomain> (raw)
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
next reply other threads:[~2021-05-20 21:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 21:22 Liang Ma [this message]
2021-05-21 7:04 ` Thomas Monjalon
2021-05-21 7:56 ` Liang Ma
2021-05-21 8:19 ` Bruce Richardson
2021-05-21 8:55 ` Liang Ma
2021-05-21 9:07 ` Bruce Richardson
2021-05-21 9:56 ` Liang Ma
2021-05-21 9:52 ` Ananyev, Konstantin
2021-05-21 10:01 ` Liang Ma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210520212203.GA26@DESKTOP-POQV63C.localdomain \
--to=liangma@liangbit.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).