From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] ACL: fix build for native-icc target on haswell fails
Date: Fri, 20 Nov 2015 17:15:51 +0100 [thread overview]
Message-ID: <4197524.MhqdmjAr8F@xps13> (raw)
In-Reply-To: <564F436A.9010202@intel.com>
2015-11-20 15:59, Declan Doherty:
> On 20/11/15 15:38, Konstantin Ananyev wrote:
> > On HSW box with icc 16.0.0 build for x86_64-native-linuxapp-icc fails with:
> > icc: command line warning #10120: overriding '-march=native' with '-msse4.1'
> > ...
> > dpdk.org/x86_64-native-linuxapp-icc/include/rte_memcpy.h(96): error: identifier "__m256i" is undefined
> >
> > The reason is that icc treats "-march=native ... -msse4.1"
> > in a different way, then gcc and clang.
> > For icc it means override all flags enabled with
> > '-march=native' with '-msse4.1'.
> > Even when '-march=native' is a superset for '-msse4.1'.
> > To overcome the problem add a check is SSE4.1 compilation flag already enabled.
> > If yes, then no need to add '-msse4.1'
> > Similar change for avx2 compilation option.
> >
> > Fixes: 074f54ad03ee ("acl: fix build and runtime for default target")
> >
> > Reported-by: Declan Doherty <declan.doherty@intel.com>
> > Reported-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
> > Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
>
> Acked-by: Declan Doherty <declan.doherty@intel.com>
Applied, thanks
prev parent reply other threads:[~2015-11-20 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 15:38 Konstantin Ananyev
2015-11-20 15:59 ` Declan Doherty
2015-11-20 16:15 ` Thomas Monjalon [this message]
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=4197524.MhqdmjAr8F@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
/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).