From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1510] net/ena build failure on Ubuntu 24.04 with LTO
Date: Sun, 04 Aug 2024 20:56:42 +0000 [thread overview]
Message-ID: <bug-1510-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 3208 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1510
Bug ID: 1510
Summary: net/ena build failure on Ubuntu 24.04 with LTO
Product: DPDK
Version: 24.07
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: alialnu@nvidia.com
Target Milestone: ---
$ meson --werror -Db_lto=true build && ninja -C build
[..]
[1586/2774] Linking target drivers/librte_net_ena.so.24.2
../lib/eal/x86/include/rte_memcpy.h: In function ‘ena_rss_hash_conf_get’:
../lib/eal/x86/include/rte_memcpy.h:128:9: warning: writing 32 bytes into a
region of size 8 [-Wstringop-overflow=]
128 | _mm256_storeu_si256((__m256i *)(void *)dst, ymm0);
| ^
../drivers/net/ena/ena_rss.c:452:17: note: at offset 32 into destination object
‘hw_rss_key’ of size 40
452 | uint8_t hw_rss_key[ENA_HASH_KEY_SIZE];
| ^
../lib/eal/x86/include/rte_memcpy.h:128:9: warning: writing 32 bytes into a
region of size 0 [-Wstringop-overflow=]
128 | _mm256_storeu_si256((__m256i *)(void *)dst, ymm0);
| ^
../drivers/net/ena/ena_rss.c:452:17: note: at offset 64 into destination object
‘hw_rss_key’ of size 40
452 | uint8_t hw_rss_key[ENA_HASH_KEY_SIZE];
| ^
../lib/eal/x86/include/rte_memcpy.h:128:9: warning: writing 32 bytes into a
region of size 0 [-Wstringop-overflow=]
128 | _mm256_storeu_si256((__m256i *)(void *)dst, ymm0);
| ^
../drivers/net/ena/ena_rss.c:452:17: note: at offset 96 into destination object
‘hw_rss_key’ of size 40
452 | uint8_t hw_rss_key[ENA_HASH_KEY_SIZE];
| ^
../lib/eal/x86/include/rte_memcpy.h:128:9: warning: writing 32 bytes into a
region of size 0 [-Wstringop-overflow=]
128 | _mm256_storeu_si256((__m256i *)(void *)dst, ymm0);
| ^
../drivers/net/ena/ena_rss.c:452:17: note: at offset [131, 17179869245] into
destination object ‘hw_rss_key’ of size 40
452 | uint8_t hw_rss_key[ENA_HASH_KEY_SIZE];
| ^
../drivers/net/ena/ena_rss.c:452:17: note: at offset [129, 193] into
destination object ‘hw_rss_key’ of size 40
../drivers/net/ena/ena_rss.c:452:17: note: at offset [131, 17179869245] into
destination object ‘hw_rss_key’ of size 40
../drivers/net/ena/ena_rss.c:452:17: note: at offset [129, 193] into
destination object ‘hw_rss_key’ of size 40
../drivers/net/ena/ena_rss.c:452:17: note: at offset [1, 40] into destination
object ‘hw_rss_key’ of size 40
../lib/eal/x86/include/rte_memcpy.h:128:9: warning: writing 32 bytes into a
region of size 8 [-Wstringop-overflow=]
128 | _mm256_storeu_si256((__m256i *)(void *)dst, ymm0);
| ^
../drivers/net/ena/ena_rss.c:452:17: note: at offset [32, 40] into destination
object ‘hw_rss_key’ of size 40
[..]
OS: Ubuntu 24.04
Meson: 1.3.2
Compiler: gcc 13.2.0
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 5090 bytes --]
next reply other threads:[~2024-08-04 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-04 20:56 bugzilla [this message]
2024-10-16 20:45 ` bugzilla
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-1510-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).