From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1509] Build failure on Ubuntu 24.04 with Link Time Optimization (LTO)
Date: Sun, 04 Aug 2024 20:38:51 +0000 [thread overview]
Message-ID: <bug-1509-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1509
Bug ID: 1509
Summary: Build failure on Ubuntu 24.04 with Link Time
Optimization (LTO)
Product: DPDK
Version: 24.07
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: alialnu@nvidia.com
Target Milestone: ---
$ meson --werror -Db_lto=true -Dc_args='-O3'
-Ddisable_drivers=net/ena,net/tap,*/octeontx,*/cnxk build && ninja -C build
[..]
[2453/2453] Linking target app/dpdk-test
In function ‘memcpy’,
inlined from ‘test_argparse_copy’ at ../app/test/test_argparse.c:94:3,
inlined from ‘test_argparse_init_obj’ at ../app/test/test_argparse.c:106:2,
inlined from ‘test_argparse_invalid_basic_param’ at
../app/test/test_argparse.c:116:8:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:29:10: warning:
‘__builtin___memcpy_chk’ writing 48 bytes into a region of size 0 overflows the
destination [-Wstringop-overflow=]
[..]
OS: Ubuntu 24.04
Meson: 1.3.2
Compiler: gcc 13.2.0
(Note: some drivers are disabled because they report other errors)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3239 bytes --]
next reply other threads:[~2024-08-04 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-04 20:38 bugzilla [this message]
2026-01-19 18:33 ` [DPDK/core Bug 1509] Build failure on Ubuntu 24.04 with Link Time Optimization (LTO) 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-1509-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.