From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============8503738673712124038==" MIME-Version: 1.0 From: Harris, James R Subject: Re: [SPDK] Compiling error on different types of Intel CPU Date: Mon, 11 Mar 2019 15:23:15 +0000 Message-ID: <192F9EFB-2EE2-4CF8-A440-ECC421F3D703@intel.com> In-Reply-To: CAHK_hpJ+mb7wC=qc_j-CWQGQqr8J_B3RDDUvEk2kaHmN9TNf8Q@mail.gmail.com List-ID: To: spdk@lists.01.org --===============8503738673712124038== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable =EF=BB=BFOn 3/11/19, 5:49 AM, "SPDK on behalf of Ernest Zed" wrote: Hi, In continuation to this issue from May 2018, I dont see anything change= d in make file, SPDK is being built with the same `-march=3Dnative` which hi= t 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 gon= na change the `-march=3Dnative` to something like `-march=3Dcore-avx-i`. B= ut 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 configu= re, but if I'm reading the Makefile correctly, any arch definition you put = there would get overridden by the march=3Dnative. The DPDK and ISA-L submo= dules would also need plumbing to pass through the arch setting. I think w= e'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 som= ething you'd be interested in working on. Thanks, -Jim _______________________________________________ SPDK mailing list SPDK(a)lists.01.org https://lists.01.org/mailman/listinfo/spdk = --===============8503738673712124038==--