From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Arek Kusztal <arkadiuszx.kusztal@intel.com>, zhoumin@loongson.cn
Subject: |FAILURE| pw126265-126266 [PATCH 2/2] crypto/qat: add sm3 hmac
Date: Thu, 20 Apr 2023 03:40:39 +0800 [thread overview]
Message-ID: <202304191940.33JJedHc2243056@localhost.localdomain> (raw)
In-Reply-To: <20230419195109.1659341-2-arkadiuszx.kusztal@intel.com>
Test-Label: loongarch-compilation
Test-Status: FAILURE
http://dpdk.org/patch/126266
_ninja build failure_
Submitter: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Date: Wed, 19 Apr 2023 19:51:08 +0000
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 189c02f5ec891ed02927062e124e8ca03adf74e7
126265-126266 --> ninja build failed
Test environment and result as below:
+---------------------+----------------+
| Environment | compilation |
+---------------------+----------------+
| Loongnix-Server 8.3 | FAIL |
+---------------------+----------------+
Loongnix-Server 8.3
Kernel: 4.19.190+
Compiler: gcc 8.3
Ninja build logs:
-------------------------------BEGIN LOGS----------------------------
FAILED: drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_sym_session.c.o
cc -Idrivers/libtmp_rte_common_qat.a.p -Idrivers -I../drivers -Idrivers/common/qat -I../drivers/common/qat -I../drivers/common/qat/qat_adf -I../drivers/crypto/qat -I../drivers/compress/qat -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/loongarch/include -I../lib/eal/loongarch/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/pci -I../lib/pci -Ilib/cryptodev -I../lib/cryptodev -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/rcu -I../lib/rcu -Ilib/net -I../lib/net -Ilib/compressdev -I../lib/compressdev -Ilib/security -I../lib/security -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -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-packed-not-aligned -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -march=loongarch64 -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DBUILD_QAT_SYM -DBUILD_QAT_ASYM -DRTE_LOG_DEFAULT_LOGTYPE=pmd.common.qat -MD -MQ drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_sym_session.c.o -MF drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_sym_session.c.o.d -o drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_sym_session.c.o -c ../drivers/crypto/qat/qat_sym_session.c
./drivers/crypto/qat/qat_sym_session.c: In function ‘qat_sym_session_configure_auth’:
./drivers/crypto/qat/qat_sym_session.c:698:7: error: ‘RTE_CRYPTO_AUTH_SM3_HMAC’ undeclared (first use in this function); did you mean ‘RTE_CRYPTO_AUTH_SHA1_HMAC’?
case RTE_CRYPTO_AUTH_SM3_HMAC:
^~~~~~~~~~~~~~~~~~~~~~~~
RTE_CRYPTO_AUTH_SHA1_HMAC
./drivers/crypto/qat/qat_sym_session.c:698:7: note: each undeclared identifier is reported only once for each function it appears in
./drivers/crypto/qat/qat_sym_session.c:700:22: warning: this statement may fall through [-Wimplicit-fallthrough=]
session->auth_mode = ICP_QAT_HW_AUTH_MODE2;
~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~
./drivers/crypto/qat/qat_sym_session.c:701:2: note: here
case RTE_CRYPTO_AUTH_SM3:
^~~~
[606/2869] Compiling C object drivers/libtmp_rte_common_qat.a.p/common_qat_qat_device.c.o
[607/2869] Compiling C object drivers/libtmp_rte_common_cnxk.a.p/common_cnxk_roc_npc_mcam.c.o
[608/2869] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_dev_qat_asym_pmd_gen1.c.o
[609/2869] Compiling C object drivers/libtmp_rte_common_cnxk.a.p/common_cnxk_cnxk_telemetry_nix.c.o
[610/2869] Compiling C object drivers/libtmp_rte_common_qat.a.p/compress_qat_qat_comp_pmd.c.o
[611/2869] Compiling C object drivers/libtmp_rte_common_cnxk.a.p/common_cnxk_cnxk_security.c.o
[612/2869] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_crypto.c.o
[613/2869] Compiling C object drivers/libtmp_rte_mempool_cnxk.a.p/mempool_cnxk_cnxk_mempool_telemetry.c.o
[614/2869] Compiling C object drivers/libtmp_rte_mempool_cnxk.a.p/mempool_cnxk_cnxk_mempool.c.o
[615/2869] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_dev_qat_crypto_pmd_gen2.c.o
[616/2869] Compiling C object drivers/libtmp_rte_mempool_cnxk.a.p/mempool_cnxk_cn9k_mempool_ops.c.o
[617/2869] Compiling C object drivers/libtmp_rte_common_qat.a.p/common_qat_qat_qp.c.o
[618/2869] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_sym.c.o
[619/2869] Compiling C object drivers/libtmp_rte_common_qat.a.p/compress_qat_qat_comp.c.o
[620/2869] Compiling C object drivers/libtmp_rte_common_cnxk.a.p/common_cnxk_roc_nix_tm.c.o
[621/2869] Compiling C object drivers/libtmp_rte_raw_skeleton.a.p/raw_skeleton_skeleton_rawdev_test.c.o
[622/2869] Compiling C object drivers/libtmp_rte_mempool_cnxk.a.p/mempool_cnxk_cnxk_mempool_ops.c.o
[623/2869] Compiling C object drivers/libtmp_rte_mempool_cnxk.a.p/mempool_cnxk_cn10k_mempool_ops.c.o
[624/2869] Compiling C object drivers/libtmp_rte_mempool_dpaa.a.p/mempool_dpaa_dpaa_mempool.c.o
[625/2869] Compiling C object drivers/libtmp_rte_mempool_dpaa2.a.p/mempool_dpaa2_dpaa2_hw_mempool.c.o
[626/2869] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_dev_qat_crypto_pmd_gen4.c.o
[627/2869] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_hwrm.c.o
[628/2869] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_asym.c.o
[629/2869] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_dev_qat_crypto_pmd_gen3.c.o
[630/2869] Generating rte_common_idpf.sym_chk with a custom command (wrapped by meson to capture output)
[631/2869] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_dev_qat_sym_pmd_gen1.c.o
[632/2869] Compiling C object drivers/libtmp_rte_mempool_bucket.a.p/mempool_bucket_rte_mempool_bucket.c.o
[633/2869] Generating rte_bus_fslmc.sym_chk with a custom command (wrapped by meson to capture output)
[634/2869] Generating rte_bus_dpaa.sym_chk with a custom command (wrapped by meson to capture output)
[635/2869] Generating ethdev.sym_chk with a custom command (wrapped by meson to capture output)
[636/2869] Generating eal.sym_chk with a custom command (wrapped by meson to capture output)
[637/2869] Compiling C object lib/librte_pipeline.a.p/pipeline_rte_swx_pipeline.c.o
[638/2869] Compiling C object lib/librte_vhost.a.p/vhost_virtio_net.c.o
ninja: build stopped: subcommand failed.
-------------------------------END LOGS------------------------------
next parent reply other threads:[~2023-04-19 19:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230419195109.1659341-2-arkadiuszx.kusztal@intel.com>
2023-04-19 19:40 ` qemudev [this message]
2023-04-19 19:52 ` |SUCCESS| pw126266 " checkpatch
2023-04-19 20:19 ` |FAILURE| " 0-day Robot
2023-04-19 20:39 |FAILURE| pw126265-126266 [PATCH] [2/2] " dpdklab
2023-04-19 20:42 dpdklab
2023-04-19 20:47 dpdklab
2023-04-19 21:02 dpdklab
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=202304191940.33JJedHc2243056@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=arkadiuszx.kusztal@intel.com \
--cc=test-report@dpdk.org \
--cc=zhoumin@loongson.cn \
/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).