From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Stephen Hemminger" <stephen@networkplumber.org>
Cc: <dev@dpdk.org>
Subject: RE: [RFC PATCH] pile stack and mempool driver (resend)
Date: Sun, 2 Aug 2026 08:38:57 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35F659B1@smartserver.smartshare.dk> (raw)
In-Reply-To: <20260801075934.2f69d3a7@phoenix.local>
> From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> Sent: Saturday, 1 August 2026 17.00
>
> On Sat, 1 Aug 2026 06:53:58 +0000
> Morten Brørup <mb@smartsharesystems.com> wrote:
>
> > +__rte_diagnostic_push
> > +#pragma GCC diagnostic ignored "-Warray-bounds"
> > +#pragma GCC diagnostic ignored "-Wstringop-overread"
>
> Ugh, no please don't fight the compiler.
>
> > + if (!(s->flags & RTE_STACK_F_PILE)) {
> > + ret = rte_stack_push(s, obj_table, 2 * STACK_SIZE);
> > + if (ret != 0) {
> > + printf("[%s():%u] Excess objects push succeeded\n",
> > + __func__, __LINE__);
> > + goto fail_test;
> > + }
> > }
Yeah. It's also difficult to sneak those pragmas through the CI.
I'll try to rework the test case instead, so the compiler cannot see that we're overflowing the stack.
next prev parent reply other threads:[~2026-08-02 6:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 6:53 [RFC PATCH] pile stack and mempool driver (resend) Morten Brørup
2026-08-01 8:10 ` Morten Brørup
2026-08-01 14:59 ` Stephen Hemminger
2026-08-02 6:38 ` Morten Brørup [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-04 14:33 [PATCH] eal/x86: optimize memcpy of small 64-byte blocks Morten Brørup
2026-08-04 14:33 ` [RFC PATCH] pile stack and mempool driver (resend) Morten Brørup
2026-08-04 14:38 ` Morten Brørup
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=98CBD80474FA8B44BF855DF32C47DC35F659B1@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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