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: Mon, 19 Jan 2026 18:33:54 +0000 [thread overview]
Message-ID: <bug-1509-3-kp2fpZdEHT@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1509-3@http.bugs.dpdk.org/>
http://bugs.dpdk.org/show_bug.cgi?id=1509
Stephen Hemminger (stephen@networkplumber.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
CC| |stephen@networkplumber.org
--- Comment #2 from Stephen Hemminger (stephen@networkplumber.org) ---
commit 3fc246e883c412f3c285bcabdb402b7d66e78526
Author: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue Sep 9 06:49:52 2025 -0700
test/argparse: change initialization to workaround LTO
When compiled with Link Time Optimization, the existing code
generated an error, because the compiler was unable to intuit
that there was space in the flexible array.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2026-01-19 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-04 20:38 [DPDK/core Bug 1509] Build failure on Ubuntu 24.04 with Link Time Optimization (LTO) bugzilla
2026-01-19 18:33 ` bugzilla [this message]
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-kp2fpZdEHT@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