From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: 26.11-rc4 build tests.
Date: Fri, 20 Nov 2026 11:05:06 -0800 [thread overview]
Message-ID: <20261120110506.1394765d@phoenix.local> (raw)
Things that still fallout from my "build with all possibilities" script.
All the compiler versions, documentation and options are fine
ASAN: error in base/ixgbe
In function ‘ixgbe_aci_debug_array’,
inlined from ‘ixgbe_aci_debug’ at ../drivers/net/intel/ixgbe/base/ixgbe_e610.c:123:3,
inlined from ‘ixgbe_aci_debug’ at ../drivers/net/intel/ixgbe/base/ixgbe_e610.c:92:6:
../drivers/net/intel/ixgbe/base/ixgbe_e610.c:59:41: error: ‘strncat’ output may be truncated copying between 43 and 118 bytes from a string of length 127 [-Werror=stringop-truncation]
59 | strncat(debug_string, debug_portion, remaining_space);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
LTO: errors in soring see fix in patchwork
Unreachable code checks still found in lots of places.
reply other threads:[~2026-11-20 19:05 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=20261120110506.1394765d@phoenix.local \
--to=stephen@networkplumber.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