From: Stephen Hemminger <stephen@networkplumber.org>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: <dev@dpdk.org>, "Ali Alnubani" <alialnu@nvidia.com>,
"Bruce Richardson" <bruce.richardson@intel.com>
Subject: Re: [PATCH 1/2] build: disable GCC string op warnings when unoptimized
Date: Tue, 20 Oct 2026 11:01:07 -0700 [thread overview]
Message-ID: <20261020110107.510a3af9@phoenix.local> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35F65ACF@smartserver.smartshare.dk>
On Tue, 20 Oct 2026 17:33:32 +0200
Morten Brørup <mb@smartsharesystems.com> wrote:
> I replied in the wrong thread, here it comes again:
>
> Also '-Warray-bounds'?
No, if it doesn't trip today, then no need to change.
>
> Consider making it a series, and also remove existing overflow/overread pragmas in the code (if viable):
> lib/ring/rte_ring_elem_pvt.h - You did this already!
> lib/eal/ppc/include/rte_memcpy.h
PPC rte_memcpy is doing something different and likely
because of different versions of GCC.
Not sure in general how supported ppc is so left it alone.
>
> With or without suggested changes,
prev parent reply other threads:[~2026-10-20 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 14:55 [PATCH 1/2] build: disable GCC string op warnings when unoptimized Stephen Hemminger
2026-10-20 14:55 ` [PATCH 2/2] ring: remove GCC pragma Stephen Hemminger
2026-10-20 15:33 ` [PATCH 1/2] build: disable GCC string op warnings when unoptimized Morten Brørup
2026-10-20 18:01 ` Stephen Hemminger [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=20261020110107.510a3af9@phoenix.local \
--to=stephen@networkplumber.org \
--cc=alialnu@nvidia.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
/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