From: <jerinj@marvell.com>
To: "Amit Prakash Shukla" <amitprakashs@marvell.com>,
"Jerin Jacob" <jerinj@marvell.com>,
"Sunil Kumar Kori" <skori@marvell.com>,
"Ankur Dwivedi" <adwivedi@marvell.com>,
"Morten Brørup" <mb@smartsharesystems.com>,
"Ferruh Yigit" <ferruh.yigit@amd.com>
Cc: <dev@dpdk.org>, <thomas@monjalon.net>,
<bruce.richardson@intel.com>, <david.marchand@redhat.com>,
<stable@dpdk.org>
Subject: [dpdk-dev] [PATCH v1 3/3] app/test: fix issues with clang 21.1.4
Date: Tue, 28 Oct 2025 22:53:23 +0530 [thread overview]
Message-ID: <20251028172324.3149379-3-jerinj@marvell.com> (raw)
In-Reply-To: <20251028172324.3149379-1-jerinj@marvell.com>
From: Jerin Jacob <jerinj@marvell.com>
Fix the following errors seen with clang 21.1.4
app/test/test_event_dma_adapter.c:532:32: error: variable 'event' is
uninitialized when passed as a const pointer argument here
[-Werror,-Wuninitialized-const-pointer]
app/test/test_trace.c:201:29: error: variable 'tmp' is uninitialized
when passed as a const pointer argument here
[-Werror,-Wuninitialized-const-pointer]
Fixes: 4925e15a1614 ("trace: add trace point emit for blob")
Fixes: a276e7c8fbb3 ("test/event: add DMA adapter auto-test")
Cc: stable@dpdk.org
Signed-off-by: Jerin Jacob <jerinj@marvell.com>
---
app/test/test_event_dma_adapter.c | 2 ++
app/test/test_trace.c | 2 +-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/app/test/test_event_dma_adapter.c b/app/test/test_event_dma_adapter.c
index 7f72a4e81d..4df5991285 100644
--- a/app/test/test_event_dma_adapter.c
+++ b/app/test/test_event_dma_adapter.c
@@ -144,6 +144,7 @@ test_dma_adapter_params(void)
TEST_ASSERT_SUCCESS(err, "Failed to get adapter capabilities\n");
if (cap & RTE_EVENT_DMA_ADAPTER_CAP_INTERNAL_PORT_VCHAN_EV_BIND) {
+ event.queue_id = 0;
err = rte_event_dma_adapter_vchan_add(TEST_ADAPTER_ID, TEST_DMA_DEV_ID,
TEST_DMA_VCHAN_ID, &event);
} else
@@ -528,6 +529,7 @@ test_dma_adapter_vchan_add_del(void)
TEST_ASSERT_SUCCESS(ret, "Failed to get adapter capabilities\n");
if (cap & RTE_EVENT_DMA_ADAPTER_CAP_INTERNAL_PORT_VCHAN_EV_BIND) {
+ event.queue_id = 0;
ret = rte_event_dma_adapter_vchan_add(TEST_ADAPTER_ID, TEST_DMA_DEV_ID,
TEST_DMA_VCHAN_ID, &event);
} else
diff --git a/app/test/test_trace.c b/app/test/test_trace.c
index 8ea1443044..52b5ba5cbb 100644
--- a/app/test/test_trace.c
+++ b/app/test/test_trace.c
@@ -179,7 +179,7 @@ static int
test_generic_trace_points(void)
{
uint8_t arr[RTE_TRACE_BLOB_LEN_MAX];
- int tmp;
+ int tmp = 0;
int i;
for (i = 0; i < RTE_TRACE_BLOB_LEN_MAX; i++)
--
2.51.2
next prev parent reply other threads:[~2025-10-28 17:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 17:23 [dpdk-dev] [PATCH v1 1/3] app/test-eventdev: " jerinj
2025-10-28 17:23 ` [dpdk-dev] [PATCH v1 2/3] net/iavf: " jerinj
2025-10-29 10:01 ` Medvedkin, Vladimir
2025-10-29 13:13 ` David Marchand
2025-10-28 17:23 ` jerinj [this message]
2025-10-29 5:02 ` [dpdk-dev] [PATCH v1 3/3] app/test: " Amit Prakash Shukla
2025-10-29 13:19 ` David Marchand
2025-10-29 6:25 ` [dpdk-dev] [PATCH v1 1/3] app/test-eventdev: " Pavan Nikhilesh Bhagavatula
2025-10-29 13:11 ` David Marchand
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=20251028172324.3149379-3-jerinj@marvell.com \
--to=jerinj@marvell.com \
--cc=adwivedi@marvell.com \
--cc=amitprakashs@marvell.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=mb@smartsharesystems.com \
--cc=skori@marvell.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).