From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: jasvinder.singh@intel.com
Subject: [dpdk-test-report] |FAILURE| pw21718 [PATCH v3 2/2] app/test: add unit test for CRC computation
Date: 12 Mar 2017 15:13:14 -0700 [thread overview]
Message-ID: <e81775$11dle80@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5784 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/21718
_Compilation issues_
Submitter: Jasvinder Singh <jasvinder.singh@intel.com>
Date: Sun, 12 Mar 2017 21:33:32 +0000
DPDK git baseline: Repo:dpdk, Branch:master, CommitID:9d5ca5323910591f2cafbac5070fcb5b6d02d022
Patch21717-21718 --> compile error
Build Summary: 18 Builds Done, 17 Successful, 1 Failures
Test environment and configuration as below:
OS: RHEL7.2_64
Kernel Version:3.10.0-514.10.2.el7.x86_64
CPU info:Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version:gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)
Clang Version:3.4.2
i686-native-linuxapp-gcc
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc-shared
OS: FreeBSD10.3_64
Kernel Version:10.3-RELEASE
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz (2194.97-MHz K8-class CPU)
GCC Version:gcc (FreeBSD Ports Collection) 4.8.5
Clang Version:3.4.1
x86_64-native-bsdapp-clang
x86_64-native-bsdapp-gcc
OS: FC24_64
Kernel Version:4.9.13-100.fc24.x86_64
CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version:gcc (GCC) 6.2.1 20160916 (Red Hat 6.2.1-2)
Clang Version:3.8.0
x86_64-native-linuxapp-gcc-debug
i686-native-linuxapp-gcc
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-clang
OS: UB1604_64
Kernel Version:4.4.0-64-generic
CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version:gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
Clang Version:3.8.0
i686-native-linuxapp-gcc
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-clang
OS: CentOS7_64
Kernel Version:3.10.0-514.10.2.el7.x86_64
CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version:gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)
Clang Version:3.4.2
i686-native-linuxapp-gcc
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-gcc
Failed Build #1:
OS: FreeBSD10.3_64
Target: x86_64-native-bsdapp-clang
In file included from /home/patchWorkOrg/compilation/lib/librte_net/rte_net_crc.c:34:
In file included from /home/patchWorkOrg/compilation/lib/librte_net/rte_net_crc.h:96:
/home/patchWorkOrg/compilation/lib/librte_net/rte_net_crc_sse.h:74:17: error: implicit declaration of function '_mm_clmulepi64_si128' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
__m128i tmp0 = _mm_clmulepi64_si128(fold, precomp, 0x01);
^
/home/patchWorkOrg/compilation/lib/librte_net/rte_net_crc_sse.h:74:17: note: did you mean '_mm_cvtsi64_si128'?
/usr/include/clang/3.4.1/emmintrin.h:1041:1: note: '_mm_cvtsi64_si128' declared here
_mm_cvtsi64_si128(long long __a)
^
In file included from /home/patchWorkOrg/compilation/lib/librte_net/rte_net_crc.c:34:
In file included from /home/patchWorkOrg/compilation/lib/librte_net/rte_net_crc.h:96:
/home/patchWorkOrg/compilation/lib/librte_net/rte_net_crc_sse.h:74:10: error: initializing '__m128i' with an expression of incompatible type 'int'
__m128i tmp0 = _mm_clmulepi64_si128(fold, precomp, 0x01);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/patchWorkOrg/compilation/lib/librte_net/rte_net_crc_sse.h:75:10: error: initializing '__m128i' with an expression of incompatible type 'int'
__m128i tmp1 = _mm_clmulepi64_si128(fold, precomp, 0x10);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/patchWorkOrg/compilation/lib/librte_net/rte_net_crc_sse.h:70:36: error: unused parameter 'data_block' [-Werror,-Wunused-parameter]
crcr32_folding_round(const __m128i data_block,
^
/home/patchWorkOrg/compilation/lib/librte_net/rte_net_crc_sse.h:96:7: error: assigning to '__m128i' from incompatible type 'int'
tmp0 = _mm_clmulepi64_si128(data128, precomp, 0x00);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/patchWorkOrg/compilation/lib/librte_net/rte_net_crc_sse.h:102:7: error: assigning to '__m128i' from incompatible type 'int'
tmp1 = _mm_clmulepi64_si128(tmp2, precomp, 0x10);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/patchWorkOrg/compilation/lib/librte_net/rte_net_crc_sse.h:131:7: error: assigning to '__m128i' from incompatible type 'int'
tmp1 = _mm_clmulepi64_si128(tmp0, precomp, 0x00);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/patchWorkOrg/compilation/lib/librte_net/rte_net_crc_sse.h:135:7: error: assigning to '__m128i' from incompatible type 'int'
tmp2 = _mm_clmulepi64_si128(tmp1, precomp, 0x10);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/patchWorkOrg/compilation/lib/librte_net/rte_net_crc_sse.h:267:8: error: assigning to '__m128i' from incompatible type 'int'
temp = _mm_clmulepi64_si128(a, k, 0x01);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/patchWorkOrg/compilation/lib/librte_net/rte_net_crc_sse.h:268:8: error: assigning to '__m128i' from incompatible type 'int'
fold = _mm_clmulepi64_si128(a, k, 0x10);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10 errors generated.
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'rte_net_crc.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'librte_net' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:81: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:129: recipe for target 'all' failed
/home/patchWorkOrg/compilation/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:104: recipe for target 'install' failed
DPDK STV team
reply other threads:[~2017-03-12 22:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='e81775$11dle80@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=jasvinder.singh@intel.com \
--cc=test-report@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).