From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/cryptodev Bug 1395] crypto/qat debug build failure with RTE_ENABLE_ASSERT (ICP_QAT_FW_SYM_COMM_ADDR_SGL undeclared)
Date: Tue, 05 Mar 2024 06:29:19 +0000 [thread overview]
Message-ID: <bug-1395-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 3582 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1395
Bug ID: 1395
Summary: crypto/qat debug build failure with RTE_ENABLE_ASSERT
(ICP_QAT_FW_SYM_COMM_ADDR_SGL undeclared)
Product: DPDK
Version: 23.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: cryptodev
Assignee: dev@dpdk.org
Reporter: alialnu@nvidia.com
Target Milestone: ---
$ meson --werror --buildtype=debug -Dc_args='-DRTE_ENABLE_ASSERT' build &&
ninja -C build
"""
In file included from ../../root/dpdk/lib/eal/x86/include/rte_spinlock.h:15,
from ../../root/dpdk/lib/mempool/rte_mempool.h:43,
from ../../root/dpdk/lib/mbuf/rte_mbuf.h:38,
from ../../root/dpdk/lib/cryptodev/rte_crypto.h:19,
from ../../root/dpdk/lib/cryptodev/rte_cryptodev.h:23,
from
../../root/dpdk/drivers/crypto/qat/dev/qat_crypto_pmd_gen_lce.c:5:
../../root/dpdk/drivers/crypto/qat/dev/qat_crypto_pmd_gen_lce.c: In function
'qat_sym_build_op_aead_gen_lce':
../../root/dpdk/drivers/crypto/qat/dev/qat_crypto_pmd_gen_lce.c:160:56: error:
'ICP_QAT_FW_SYM_COMM_ADDR_SGL' undeclared (first use in this function); did you
mean 'ICP_QAT_FW_SYM_AEAD_ALGO_SET'?
160 | RTE_ASSERT((qat_req->comn_hdr.comn_req_flags &
ICP_QAT_FW_SYM_COMM_ADDR_SGL) == 1);
|
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
../../root/dpdk/lib/eal/include/rte_branch_prediction.h:47:45: note: in
definition of macro 'unlikely'
47 | #define unlikely(x) __builtin_expect(!!(x), 0)
| ^
../../root/dpdk/lib/eal/include/rte_debug.h:47:25: note: in expansion of macro
'RTE_VERIFY'
47 | #define RTE_ASSERT(exp) RTE_VERIFY(exp)
| ^~~~~~~~~~
../../root/dpdk/drivers/crypto/qat/dev/qat_crypto_pmd_gen_lce.c:160:9: note: in
expansion of macro 'RTE_ASSERT'
160 | RTE_ASSERT((qat_req->comn_hdr.comn_req_flags &
ICP_QAT_FW_SYM_COMM_ADDR_SGL) == 1);
| ^~~~~~~~~~
../../root/dpdk/drivers/crypto/qat/dev/qat_crypto_pmd_gen_lce.c:160:56: note:
each undeclared identifier is reported only once for each function it appears
in
160 | RTE_ASSERT((qat_req->comn_hdr.comn_req_flags &
ICP_QAT_FW_SYM_COMM_ADDR_SGL) == 1);
|
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
../../root/dpdk/lib/eal/include/rte_branch_prediction.h:47:45: note: in
definition of macro 'unlikely'
47 | #define unlikely(x) __builtin_expect(!!(x), 0)
| ^
../../root/dpdk/lib/eal/include/rte_debug.h:47:25: note: in expansion of macro
'RTE_VERIFY'
47 | #define RTE_ASSERT(exp) RTE_VERIFY(exp)
| ^~~~~~~~~~
../../root/dpdk/drivers/crypto/qat/dev/qat_crypto_pmd_gen_lce.c:160:9: note: in
expansion of macro 'RTE_ASSERT'
160 | RTE_ASSERT((qat_req->comn_hdr.comn_req_flags &
ICP_QAT_FW_SYM_COMM_ADDR_SGL) == 1);
| ^~~~~~~~~~
[826/2503] Compiling C object
drivers/common/sfc_efx/base/libsfc_base.a.p/ef10_nic.c.o
ninja: build stopped: subcommand failed.
"""
Doesn't reproduce without -Dc_args='-DRTE_ENABLE_ASSERT'.
OS: Debian 12
Meson: 1.0.1
gcc: 12.2.0 (Debian 12.2.0-14)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 5550 bytes --]
reply other threads:[~2024-03-05 6:29 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=bug-1395-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).