From: sys_stv@intel.com
To: test-report@dpdk.org, gmuthukrishn@marvell.com
Subject: compilation|FAILURE| pw(144992) sid(33243) job(PER_PATCH_BUILD13380)[v4, 6/6] app/crypto-perf: support EDDSA
Date: 03 Oct 2024 11:46:52 -0700 [thread overview]
Message-ID: <66cbb4$2bb2et@fmviesa004-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 12354 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/144992
_Compilation issues_
Submitter: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: 2024-10-03 17:56:22
Reply_mail: <20241003175625.135-6-gmuthukrishn@marvell.com>
DPDK git baseline: Repo:dpdk, CommitID: 2b843cac232eb3f2fa79e4254e21766817e2019f
Meson Build Summary: 23 Builds Done, 22 Successful, 1 Failures, 0 Blocked
+------------------+------------+--------------+------------+------------+-----------+----------+------------+
| os | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug | document | gcc-16byte |
+------------------+------------+--------------+------------+------------+-----------+----------+------------+
| OpenAnolis8.9-64 | pass | | | | | | |
| FreeBSD14-64 | pass | pass | | pass | pass | | |
| RHEL94-64 | pass | pass | | pass | pass | | |
| SUSE15-64 | pass | pass | | | | | |
| AzureLinux3.0-64 | fail | | | | | | |
| UB2404-32 | pass | | | | | | |
| RHEL81-64 | pass | | | | | | |
| UB2404-64 | pass | pass | | | | pass | pass |
| RHEL94-64Rt | pass | | | | | | |
| UB2204-64 | pass | | | | | | |
| FC40-64 | pass | pass | | | | | |
| UB2404-64Rt | pass | | | | | | |
+------------------+------------+--------------+------------+------------+-----------+----------+------------+
Comments:
Because of DPDK bug (https://bugs.dpdk.org/show_bug.cgi?id=928),
All the dpdk-next-* branch add `Ddisable_drivers=event/cnxk` option when build with ICC complier.
Test environment and configuration as below:
OS: OpenAnolis8.9-64
Kernel Version: 5.10.134-16.2.an8.x86_64
GCC Version: gcc (GCC) 8.5.0 20210514 (Anolis 8.5.0-22.0.1)
Clang Version: 15.0.7 (Anolis 15.0.7-1.0.3.module+an8.8.0+11135+e398acfc)
x86_64-native-linuxapp-gcc
OS: FreeBSD14-64
Kernel Version: 14.1-RELEASE
GCC Version: gcc (FreeBSD Ports Collection) 13.2.0
Clang Version: 18.1.5 (https://github.com/llvm/llvm-project.git llvmorg-18.1.5-0-g617a15a9eac9)
x86_64-native-bsdapp-gcc
x86_64-native-bsdapp-clang
x86_64-native-bsdapp-gcc+shared
x86_64-native-bsdapp-gcc+debug
OS: RHEL94-64
Kernel Version: 5.14.0-427.13.1.el9_4.x86_64
GCC Version: gcc (GCC) 11.4.1 20231218 (Red Hat 11.4.1-3)
Clang Version: 17.0.6 (Red Hat, Inc. 17.0.6-5.el9)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc+shared
x86_64-native-linuxapp-gcc+debug
OS: SUSE15-64
Kernel Version: 6.4.0-150600.21-default
GCC Version: gcc (SUSE Linux) 7.5.0
Clang Version: 17.0.6
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc
OS: AzureLinux3.0-64
Kernel Version: 6.6.47.1-1.azl3
GCC Version: gcc (GCC) 13.2.0
Clang Version: 18.1.2
x86_64-native-linuxapp-gcc
OS: UB2404-32
Kernel Version: 6.8.0-41-generic
GCC Version: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
Clang Version: NA
i686-native-linuxapp-gcc
OS: RHEL81-64
Kernel Version: 4.18.0-553.el8_10.x86_64
GCC Version: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-21)
Clang Version: 17.0.6 (Red Hat 17.0.6-1.module+el8.10.0+20808+e12784c0)
x86_64-native-linuxapp-gcc
OS: UB2404-64
Kernel Version: 6.8.0-41-generic
GCC Version: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
Clang Version: NA
x86_64-native-linuxapp-gcc+16byte
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-doc
OS: RHEL94-64Rt
Kernel Version: 5.14.0-427.13.1.el9_4.x86_64+rt
GCC Version: gcc (GCC) 11.4.1 20231218 (Red Hat 11.4.1-3)
Clang Version: 17.0.6 (Red Hat, Inc. 17.0.6-5.el9)
x86_64-native-linuxapp-gcc
OS: UB2204-64
Kernel Version: 5.15.0-94-generic
GCC Version: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang Version: 14.0.0-1ubuntu1.1
x86_64-native-linuxapp-gcc
OS: FC40-64
Kernel Version: 6.8.5-301.fc40.x86_64
GCC Version: gcc (GCC) 14.0.1 20240411 (Red Hat 14.0.1-0)
Clang Version: 18.1.1 (Fedora 18.1.1-1.fc40)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
OS: UB2404-64Rt
Kernel Version: 6.8.0-rt8
GCC Version: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
Clang Version: NA
x86_64-native-linuxapp-gcc
*Build Failed #1:
OS: AzureLinux3.0-64
Target: x86_64-native-linuxapp-gcc
FAILED: drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd_ops.c.o
gcc -Idrivers/libtmp_rte_crypto_openssl.a.p -Idrivers -I../drivers -Idrivers/crypto/openssl -I../drivers/crypto/openssl -Ilib/cryptodev -I../lib/cryptodev -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/x86/include -I../lib/eal/x86/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/log -I../lib/log -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/rcu -I../lib/rcu -Idrivers/bus/vdev -I../drivers/bus/vdev -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -O3 -include rte_config.h -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-address-of-packed-member -Wno-packed-not-aligned -Wno-missing-field-initializers -Wno-zero-length-bounds -D_GNU_SOURCE -fPIC -march=native -mrtm -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DRTE_LOG_DEFAULT_LOGTYPE=pmd.crypto.openssl -MD -MQ drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd_ops.c.o -MF drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd_ops.c.o.d -o drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd_ops.c.o -c ../drivers/crypto/openssl/rte_openssl_pmd_ops.c
In file included from ../lib/eal/x86/include/rte_vect.h:14,
from ../lib/eal/x86/include/rte_memcpy.h:17,
from ../lib/mempool/rte_mempool.h:50,
from ../lib/mbuf/rte_mbuf.h:38,
from ../lib/cryptodev/rte_crypto.h:19,
from ../lib/cryptodev/cryptodev_pmd.h:28,
from ../drivers/crypto/openssl/rte_openssl_pmd_ops.c:9:
../drivers/crypto/openssl/rte_openssl_pmd_ops.c: In function ‘openssl_set_asym_session_parameters’:
../lib/log/rte_log.h:364:9: error: static assertion failed: "This log format string contains a \\n"
364 | static_assert(!__builtin_strchr(fmt, '\n'), \
| ^~~~~~~~~~~~~
../lib/log/rte_log.h:445:9: note: in expansion of macro ‘RTE_LOG_CHECK_NO_NEWLINE’
445 | RTE_LOG_CHECK_NO_NEWLINE(RTE_FMT_HEAD(prefix __VA_ARGS__ ,)); \
| ^~~~~~~~~~~~~~~~~~~~~~~~
../drivers/crypto/openssl/openssl_pmd_private.h:28:9: note: in expansion of macro ‘RTE_LOG_LINE_PREFIX’
28 | RTE_LOG_LINE_PREFIX(level, OPENSSL_DRIVER, "%s() line %u: ", \
| ^~~~~~~~~~~~~~~~~~~
../drivers/crypto/openssl/rte_openssl_pmd_ops.c:1521:25: note: in expansion of macro ‘OPENSSL_LOG’
1521 | OPENSSL_LOG(ERR, "failed to allocate params\n");
| ^~~~~~~~~~~
../lib/log/rte_log.h:364:9: error: static assertion failed: "This log format string contains a \\n"
364 | static_assert(!__builtin_strchr(fmt, '\n'), \
| ^~~~~~~~~~~~~
../lib/log/rte_log.h:445:9: note: in expansion of macro ‘RTE_LOG_CHECK_NO_NEWLINE’
445 | RTE_LOG_CHECK_NO_NEWLINE(RTE_FMT_HEAD(prefix __VA_ARGS__ ,)); \
| ^~~~~~~~~~~~~~~~~~~~~~~~
../drivers/crypto/openssl/openssl_pmd_private.h:28:9: note: in expansion of macro ‘RTE_LOG_LINE_PREFIX’
28 | RTE_LOG_LINE_PREFIX(level, OPENSSL_DRIVER, "%s() line %u: ", \
| ^~~~~~~~~~~~~~~~~~~
../drivers/crypto/openssl/rte_openssl_pmd_ops.c:1528:25: note: in expansion of macro ‘OPENSSL_LOG’
1528 | OPENSSL_LOG(ERR, "failed to push params\n");
| ^~~~~~~~~~~
../lib/log/rte_log.h:364:9: error: static assertion failed: "This log format string contains a \\n"
364 | static_assert(!__builtin_strchr(fmt, '\n'), \
| ^~~~~~~~~~~~~
../lib/log/rte_log.h:445:9: note: in expansion of macro ‘RTE_LOG_CHECK_NO_NEWLINE’
445 | RTE_LOG_CHECK_NO_NEWLINE(RTE_FMT_HEAD(prefix __VA_ARGS__ ,)); \
| ^~~~~~~~~~~~~~~~~~~~~~~~
../drivers/crypto/openssl/openssl_pmd_private.h:28:9: note: in expansion of macro ‘RTE_LOG_LINE_PREFIX’
28 | RTE_LOG_LINE_PREFIX(level, OPENSSL_DRIVER, "%s() line %u: ", \
| ^~~~~~~~~~~~~~~~~~~
../drivers/crypto/openssl/rte_openssl_pmd_ops.c:1535:25: note: in expansion of macro ‘OPENSSL_LOG’
1535 | OPENSSL_LOG(ERR, "failed to push params\n");
| ^~~~~~~~~~~
../lib/log/rte_log.h:364:9: error: static assertion failed: "This log format string contains a \\n"
364 | static_assert(!__builtin_strchr(fmt, '\n'), \
| ^~~~~~~~~~~~~
../lib/log/rte_log.h:445:9: note: in expansion of macro ‘RTE_LOG_CHECK_NO_NEWLINE’
445 | RTE_LOG_CHECK_NO_NEWLINE(RTE_FMT_HEAD(prefix __VA_ARGS__ ,)); \
| ^~~~~~~~~~~~~~~~~~~~~~~~
../drivers/crypto/openssl/openssl_pmd_private.h:28:9: note: in expansion of macro ‘RTE_LOG_LINE_PREFIX’
28 | RTE_LOG_LINE_PREFIX(level, OPENSSL_DRIVER, "%s() line %u: ", \
| ^~~~~~~~~~~~~~~~~~~
../drivers/crypto/openssl/rte_openssl_pmd_ops.c:1542:25: note: in expansion of macro ‘OPENSSL_LOG’
1542 | OPENSSL_LOG(ERR, "failed to push params\n");
| ^~~~~~~~~~~
../lib/log/rte_log.h:364:9: error: static assertion failed: "This log format string contains a \\n"
364 | static_assert(!__builtin_strchr(fmt, '\n'), \
| ^~~~~~~~~~~~~
../lib/log/rte_log.h:445:9: note: in expansion of macro ‘RTE_LOG_CHECK_NO_NEWLINE’
445 | RTE_LOG_CHECK_NO_NEWLINE(RTE_FMT_HEAD(prefix __VA_ARGS__ ,)); \
| ^~~~~~~~~~~~~~~~~~~~~~~~
../drivers/crypto/openssl/openssl_pmd_private.h:28:9: note: in expansion of macro ‘RTE_LOG_LINE_PREFIX’
28 | RTE_LOG_LINE_PREFIX(level, OPENSSL_DRIVER, "%s() line %u: ", \
| ^~~~~~~~~~~~~~~~~~~
../drivers/crypto/openssl/rte_openssl_pmd_ops.c:1548:25: note: in expansion of macro ‘OPENSSL_LOG’
1548 | OPENSSL_LOG(ERR, "failed to push params\n");
| ^~~~~~~~~~~
[2259/3037] Linking target drivers/librte_crypto_dpaa2_sec.so.25.0
[2260/3037] Compiling C object drivers/libtmp_rte_crypto_scheduler.a.p/crypto_scheduler_scheduler_failover.c.o
[2261/3037] Compiling C object drivers/libtmp_rte_crypto_scheduler.a.p/crypto_scheduler_rte_cryptodev_scheduler.c.o
[2262/3037] Compiling C object drivers/libtmp_rte_crypto_scheduler.a.p/crypto_scheduler_scheduler_pkt_size_distr.c.o
[2263/3037] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/crypto_cnxk_cn9k_cryptodev_ops.c.o
[2264/3037] Compiling C object drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd.c.o
[2265/3037] Compiling C object drivers/libtmp_rte_crypto_scheduler.a.p/crypto_scheduler_scheduler_multicore.c.o
[2266/3037] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/crypto_cnxk_cn10k_cryptodev_ops.c.o
[2267/3037] Compiling C object drivers/libtmp_rte_crypto_octeontx.a.p/crypto_octeontx_otx_cryptodev_ops.c.o
ninja: build stopped
DPDK STV team
reply other threads:[~2024-10-03 18:47 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='66cbb4$2bb2et@fmviesa004-auth.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=gmuthukrishn@marvell.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).