DPDK patches and discussions
 help / color / mirror / Atom feed
From: <amartya.das@wipro.com>
To: <akapoor@parallelwireless.com>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [DPDK16.04: Error While compiling]
Date: Tue, 21 Jun 2016 09:42:27 +0000	[thread overview]
Message-ID: <PS1PR03MB18833D22F92CE33E9B2FC15BED2B0@PS1PR03MB1883.apcprd03.prod.outlook.com> (raw)
In-Reply-To: <87d1naq4im.fsf@fatcat.parallelwireless>

Hi,

Its VM fedora21, gcc 4.9.

Thanks,
Amartya

-----Original Message-----
From: Anupam Kapoor [mailto:akapoor@parallelwireless.com]
Sent: Tuesday, June 21, 2016 2:54 PM
To: Amartya Kumar Das (MFG & Tech) <amartya.das@wipro.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [DPDK16.04: Error While compiling]

** This mail has been sent from an external source **

>>>>> [2016-06-21T11:27:50+0530]: "amartya.das" (amartya-das):
,----[ amartya-das ]
| I am facing compilation error for DPDK 16.04 as below:
| In file included from /home/cran/dpdk-16.04/lib/librte_eal/common/eal_common_options.c:52:0:
| /home/cran/dpdk-16.04/x86_64-native-linuxapp-gcc/include/rte_memcpy.h:673:9: error: called from here
| _mm_storeu_si128((__m128i *)((uint8_t *)dst + 6 * 16), _mm_alignr_epi8(xmm7, xmm6, offset));        \
| ^
| /home/cran/dpdk-16.04/x86_64-native-linuxapp-gcc/include/rte_memcpy.h:730:16: note: in expansion of macro 'MOVEUNALIGNED_LEFT47_IMM'
| case 0x0F: MOVEUNALIGNED_LEFT47_IMM(dst, src, n, 0x0F); break;    \
| ^
| /home/cran/dpdk-16.04/x86_64-native-linuxapp-gcc/include/rte_memcpy.h:870:2: note: in expansion of macro 'MOVEUNALIGNED_LEFT47'
| MOVEUNALIGNED_LEFT47(dst, src, n, srcofs); ^ In file included from
| /usr/lib/gcc/x86_64-redhat-linux/4.9.2/include/x86intrin.h:37:0,
| from
| /home/cran/dpdk-16.04/x86_64-native-linuxapp-gcc/include/rte_vect.h:67
| , from
| /home/cran/dpdk-16.04/x86_64-native-linuxapp-gcc/include/rte_memcpy.h:
| 46, from
| /home/cran/dpdk-16.04/lib/librte_eal/common/eal_common_options.c:52:
| /usr/lib/gcc/x86_64-redhat-linux/4.9.2/include/tmmintrin.h:185:1:
| error: inlining failed in call to always_inline '_mm_alignr_epi8':
| target specific option mismatch _mm_alignr_epi8(__m128i __X, __m128i
| __Y, const int __N)
`----
can you please provide information on the os and platform where you are attempting this ? from the paths it seems like gcc 4.9 on redhat (7 maybe ?)

---
thanks
anupam
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

  parent reply	other threads:[~2016-06-21  9:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21  5:57 amartya.das
     [not found] ` <87d1naq4im.fsf@fatcat.parallelwireless>
2016-06-21  9:42   ` amartya.das [this message]
2016-06-21 10:03     ` Anupam Kapoor
2016-06-26 11:53       ` amartya.das

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=PS1PR03MB18833D22F92CE33E9B2FC15BED2B0@PS1PR03MB1883.apcprd03.prod.outlook.com \
    --to=amartya.das@wipro.com \
    --cc=akapoor@parallelwireless.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).