DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, Jie Liu <liujie5@linkdatatechnology.com>
Subject: Re: [PATCH] net/sxe2: fix 32-bit SSE build
Date: Thu, 28 May 2026 12:58:11 +0200	[thread overview]
Message-ID: <-b1vJiPdTrqtGy9X39oH8Q@monjalon.net> (raw)
In-Reply-To: <CAJFAV8xY0uM=RbcR64ZMc-eOTVkzZc0PFTCBCaQkNNE7uuvZeg@mail.gmail.com>

28/05/2026 11:47, David Marchand:
> On Thu, 28 May 2026 at 10:47, Thomas Monjalon <thomas@monjalon.net> wrote:
> >
> > Seen in OBS on i586 Debian:
> >
> > from ../drivers/net/sxe2/sxe2_txrx_vec_sse.c:5:
> >         In function ‘_mm_loadu_si128’,
> >                 inlined from ‘rte_memcpy’
> >                 inlined from ‘sxe2_rx_pkts_refactor’
> >                         at ../drivers/net/sxe2/sxe2_txrx_vec_common.h:233:2:
> >         /usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:703:10: error:
> >         array subscript 8 is outside array bounds of ‘struct rte_mbuf *[32]’
> >
> > The important options to reproduce are "-m32 -O2 -march=corei7".
> >
> > In 32-bit build the pointer array done_pkts[32] is smaller:
> >         32 * 4 = 128 bytes
> > so an SSE access  would be outside the bound.
> >
> > The libc memcpy does not trigger such warning
> > and is a good choice to copy an array of pointers.
> >
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> 
> I reproduced and checked Debian 13 32 bits build with OBS.
> Tested-by: David Marchand <david.marchand@redhat.com>

Thanks for testing.

I forgot this:

Fixes: 885647d31504 ("net/sxe2: fix 32-bit SSE build")




  reply	other threads:[~2026-05-28 10:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-28  8:47 [PATCH] net/sxe2: fix 32-bit SSE build Thomas Monjalon
2026-05-28  9:47 ` David Marchand
2026-05-28 10:58   ` Thomas Monjalon [this message]
2026-05-28 11:00     ` Thomas Monjalon
2026-05-29 10:24   ` Thomas Monjalon

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=-b1vJiPdTrqtGy9X39oH8Q@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=liujie5@linkdatatechnology.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