From: Harris, James R <james.r.harris at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Compiling error on different types of Intel CPU
Date: Mon, 11 Mar 2019 15:23:15 +0000 [thread overview]
Message-ID: <192F9EFB-2EE2-4CF8-A440-ECC421F3D703@intel.com> (raw)
In-Reply-To: CAHK_hpJ+mb7wC=qc_j-CWQGQqr8J_B3RDDUvEk2kaHmN9TNf8Q@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1538 bytes --]
On 3/11/19, 5:49 AM, "SPDK on behalf of Ernest Zed" <spdk-bounces(a)lists.01.org on behalf of kreuzerkrieg(a)gmail.com> wrote:
Hi,
In continuation to this issue from May 2018, I dont see anything changed in
make file, SPDK is being built with the same `-march=native` which hit us
hard two days ago when we upgraded our build machine to the latest Xeon
which supports AVX512. Our test machines does not have this extension so
binaries built on newer machine wont run on older ones. Meanwhile I gonna
change the `-march=native` to something like `-march=core-avx-i`. But is it
possible to change the `configure` script to pass additional compilation
flags to the `make`?
Hi Ernest,
I don't think it's possible today. There's a way to pass CFLAGS to configure, but if I'm reading the Makefile correctly, any arch definition you put there would get overridden by the march=native. The DPDK and ISA-L submodules would also need plumbing to pass through the arch setting. I think we'll want to create a separate variable specific for arch, rather than try to 'fix' the CFLAGS handling in the configure script.
This is a pretty reasonable request though - could you file an issue in the SPDK GitHub tracker for this? Please also add in the issue if this is something you'd be interested in working on.
Thanks,
-Jim
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk
next reply other threads:[~2019-03-11 15:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 15:23 Harris, James R [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-11 16:12 [SPDK] Compiling error on different types of Intel CPU E.W.Z.
2019-03-11 12:48 Ernest Zed
2018-05-22 14:00 Kulasek, TomaszX
2018-05-22 7:09 Bob Chen
2018-05-22 4:08 Harris, James R
2018-05-22 3:23 Bob Chen
2018-05-21 15:25 Harris, James R
2018-05-21 15:18 Verkamp, Daniel
2018-05-21 13:31 Marushak, Nathan
2018-05-21 12:21 Luse, Paul E
2018-05-21 8:11 Bob Chen
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=192F9EFB-2EE2-4CF8-A440-ECC421F3D703@intel.com \
--to=spdk@lists.01.org \
/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