From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1790] warnings in CNXK when built with LTO
Date: Tue, 23 Sep 2025 04:23:36 +0000 [thread overview]
Message-ID: <bug-1790-3@https.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 4048 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1790
Bug ID: 1790
Summary: warnings in CNXK when built with LTO
Product: DPDK
Version: 25.07
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
If DPDK is built with link time optimization the compiler can see across file
scope and detect more errors like this.
$ meson setup build -Db_lto=true && ninja --quiet -C build
In function ‘parse_flag’,
inlined from ‘kvargs_process_common’ at ../lib/kvargs/rte_kvargs.c:187:9,
inlined from ‘rte_kvargs_process’ at ../lib/kvargs/rte_kvargs.c:203:9,
inlined from ‘cnxk_ethdev_parse_devargs’ at
../drivers/net/cnxk/cnxk_ethdev_devargs.c:371:2:
../drivers/net/cnxk/cnxk_ethdev_devargs.c:166: warning: writing 2 bytes into a
region of size 1 [-Wstringop-overflow=]
166 | *(uint16_t *)extra_args = atoi(value);
../drivers/net/cnxk/cnxk_ethdev_devargs.c: In function
‘cnxk_ethdev_parse_devargs’:
../drivers/net/cnxk/cnxk_ethdev_devargs.c:306:17: note: destination object
‘force_tail_drop’ of size 1
306 | uint8_t force_tail_drop = 0;
| ^
In function ‘parse_flag’,
inlined from ‘kvargs_process_common’ at ../lib/kvargs/rte_kvargs.c:187:9,
inlined from ‘rte_kvargs_process’ at ../lib/kvargs/rte_kvargs.c:203:9,
inlined from ‘cnxk_ethdev_parse_devargs’ at
../drivers/net/cnxk/cnxk_ethdev_devargs.c:372:2:
../drivers/net/cnxk/cnxk_ethdev_devargs.c:166: warning: writing 2 bytes into a
region of size 1 [-Wstringop-overflow=]
166 | *(uint16_t *)extra_args = atoi(value);
../drivers/net/cnxk/cnxk_ethdev_devargs.c: In function
‘cnxk_ethdev_parse_devargs’:
../drivers/net/cnxk/cnxk_ethdev_devargs.c:312:17: note: destination object
‘dis_xqe_drop’ of size 1
312 | uint8_t dis_xqe_drop = 0;
| ^
../drivers/common/cnxk/roc_platform.c: In function ‘irq_config’:
../drivers/common/cnxk/roc_platform.c:55:14: warning: argument to
variable-length array is too large [-Wvla-larger-than=]
55 | char irq_set_buf[MSIX_IRQ_SET_BUF_LEN];
| ^
../drivers/common/cnxk/roc_platform.c:55:14: note: limit is 9223372036854775807
bytes, but argument is 18446744073709551548
../drivers/common/cnxk/roc_platform.c: In function ‘irq_init’:
../drivers/common/cnxk/roc_platform.c:91:14: warning: argument to
variable-length array is too large [-Wvla-larger-than=]
91 | char irq_set_buf[MSIX_IRQ_SET_BUF_LEN];
| ^
../drivers/common/cnxk/roc_platform.c:91:14: note: limit is 9223372036854775807
bytes, but argument is 18446744073709551548
In function ‘roc_ow_reass_inb_sa_init’,
inlined from ‘nix_inl_reass_inb_sa_tbl_setup’ at
../drivers/common/cnxk/roc_nix_inl.c:610:2,
inlined from ‘nix_inl_inb_init’ at
../drivers/common/cnxk/roc_nix_inl.c:1417:8,
inlined from ‘roc_nix_inl_inb_init’ at
../drivers/common/cnxk/roc_nix_inl.c:1439:9:
../drivers/common/cnxk/roc_ie_ow.c:35:9: warning: ‘memset’ writing 808 bytes
into a region of size 1 overflows the destination [-Wstringop-overflow=]
35 | memset(sa, 0, sizeof(struct roc_ow_ipsec_inb_sa));
| ^
In function ‘nix_inl_reass_inb_sa_tbl_setup’,
inlined from ‘nix_inl_inb_init’ at
../drivers/common/cnxk/roc_nix_inl.c:1417:8,
inlined from ‘roc_nix_inl_inb_init’ at
../drivers/common/cnxk/roc_nix_inl.c:1439:9:
../drivers/common/cnxk/roc_nix_inl.c:603:40: note: destination object of size 1
allocated by ‘rte_zmalloc’
603 | nix->inb_sa_base[profile_id] = plt_zmalloc(inb_sa_sz * max_sa,
ROC_NIX_INL_SA_BASE_ALIGN);
|
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 5923 bytes --]
reply other threads:[~2025-09-23 4:23 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-1790-3@https.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).