From: Panu Matilainen <pmatilai@redhat.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] rte_memcpy.h: additional cflags required with OVS
Date: Tue, 10 Mar 2015 09:52:07 +0200 [thread overview]
Message-ID: <54FEA2A7.90403@redhat.com> (raw)
In-Reply-To: <533710CFB86FA344BFBF2D6802E60286CFDC65@SHSMSX101.ccr.corp.intel.com>
On 03/10/2015 05:04 AM, Qiu, Michael wrote:
> On 3/10/2015 12:44 AM, Kavanagh, Mark B wrote:
>> Hi,
>>
>> Compilation of Open vSwitch fails when linked against current HEAD of DPDK (f2552cd5).
>>
>> The source of this issue appears to be commit ID 9144d6b: "eal/x86: optimize memcpy for SSE and AVX", and can be resolved by passing an additional argument to OVS when building same (CFLAGS="-march=native").
>> It seems that without this flag, OVS doesn't pick up one or more SSE #defines in DPDK, and doesn't include a relevant intrinsic header (emmintrin.h), leading to an 'implicit declaration' error for instrinsic '_mm_storeu_si128'.
>
> What's your gcc version? this should be an issue with old version gcc,
> and I'm working on this to solve this issue now. If you want to solve
> this you should upgrade gcc or include them manually, and remove header
> x86intrin.h .
At least gcc 4.8.2 (which is what RHEL-7 has) exhibits this, however gcc
4.9 and 5 "just work". The workaround I used was adding -msse4.1 to the
OVS CFLAGS manually.
- Panu -
next prev parent reply other threads:[~2015-03-10 7:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 16:44 Kavanagh, Mark B
2015-03-09 17:51 ` Mcnamara, John
2015-03-10 0:57 ` Mcnamara, John
2015-03-10 3:00 ` Qiu, Michael
2015-03-10 9:16 ` Kavanagh, Mark B
2015-03-10 3:04 ` Qiu, Michael
2015-03-10 7:52 ` Panu Matilainen [this message]
2015-03-10 8:27 ` Mcnamara, John
2015-03-10 10:03 ` Kavanagh, Mark B
2015-03-11 4:37 ` Wang, Zhihong
2015-03-11 8:06 ` Mcnamara, John
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=54FEA2A7.90403@redhat.com \
--to=pmatilai@redhat.com \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).