From: "Kavanagh, Mark B" <mark.b.kavanagh@intel.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>,
"Qiu, Michael" <michael.qiu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Panu Matilainen <pmatilai@redhat.com>
Subject: Re: [dpdk-dev] rte_memcpy.h: additional cflags required with OVS
Date: Tue, 10 Mar 2015 10:03:50 +0000 [thread overview]
Message-ID: <DC5AD7FA266D86499789B1BCAEC715F846D4F022@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2ECCAB0@IRSMSX103.ger.corp.intel.com>
>-----Original Message-----
>From: Mcnamara, John
>Sent: Tuesday, March 10, 2015 8:27 AM
>To: Qiu, Michael; Kavanagh, Mark B; dev@dpdk.org; Panu Matilainen
>Subject: RE: [dpdk-dev] rte_memcpy.h: additional cflags required with OVS
>
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Qiu, Michael
>> Sent: Tuesday, March 10, 2015 3:05 AM
>> To: Kavanagh, Mark B; dev@dpdk.org
>> Subject: Re: [dpdk-dev] rte_memcpy.h: additional cflags required with OVS
>>
>
>> 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.
>
>
>Hi Michael,
>
>I see the issue with gcc 4.7.2 but not with 4.9.2.
I'm using gcc v4.8.3.
Just to clarify my initial post, there are two issues related to gcc intrinsic headers emmintrin.h, and tmmintrin.h:
- in former, a difference in parameter types for _mm_storeu_si128 is the issue. This is the primary issue observed.
- in tmmintrin.h, when __OPTIMIZE__ is not defined, function _mm_alignr_epi8 is also not defined, leading to an 'implicit definition of function' error.
I've only noticed this intermittently (even though I compile OVS with -O2 CFLAGS)
>
>John
next prev parent reply other threads:[~2015-03-10 10:03 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
2015-03-10 8:27 ` Mcnamara, John
2015-03-10 10:03 ` Kavanagh, Mark B [this message]
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=DC5AD7FA266D86499789B1BCAEC715F846D4F022@irsmsx105.ger.corp.intel.com \
--to=mark.b.kavanagh@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=michael.qiu@intel.com \
--cc=pmatilai@redhat.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).