All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 2061] [Debug][aarch64] test_stack_perf fails to build with GCC 13 due to memcpy overread/overflow warning
Date: Mon, 19 Oct 2026 13:36:39 +0000	[thread overview]
Message-ID: <bug-2061-3@https.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=2061

            Bug ID: 2061
           Summary: [Debug][aarch64] test_stack_perf fails to build with
                    GCC 13 due to memcpy overread/overflow warning
           Product: DPDK
           Version: 26.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: alialnu@nvidia.com
  Target Milestone: ---

$ meson --werror --buildtype=debug build && ninja -C build

[..]
[3428/3451] Compiling C object app/dpdk-test.p/test_test_tailq.c.o
[3429/3451] Compiling C object
app/dpdk-test.p/test_test_security_inline_macsec.c.o
[3430/3451] Compiling C object app/dpdk-test.p/test_test_stack_perf.c.o
FAILED: app/dpdk-test.p/test_test_stack_perf.c.o 
[..]
In file included from ../../root/dpdk/lib/eal/arm/include/rte_memcpy.h:9,
                 from ../../root/dpdk/lib/stack/rte_stack_pile.h:8,
                 from ../../root/dpdk/lib/stack/rte_stack.h:152,
                 from ../../root/dpdk/app/test/test_stack_perf.c:12:
In function '__rte_stack_pile_push',
    inlined from 'rte_stack_push' at
../../root/dpdk/lib/stack/rte_stack.h:179:10,
    inlined from 'test_single_push_pop' at
../../root/dpdk/app/test/test_stack_perf.c:261:3:
../../root/dpdk/lib/eal/arm/include/rte_memcpy_64.h:365:33: error: 'memcpy'
reading 256 bytes from a region of size 8 [-Werror=stringop-overread]
  365 | #define rte_memcpy(d, s, n)     memcpy((d), (s), (n))
      |                                 ^~~~~~~~~~~~~~~~~~~~~
../../root/dpdk/lib/stack/rte_stack_pile.h:160:17: note: in expansion of macro
'rte_memcpy'
  160 |                 rte_memcpy(((struct rte_stack_pile_bulk_elem
*)tmp)->objs,
      |                 ^~~~~~~~~~
../../root/dpdk/app/test/test_stack_perf.c: In function 'test_single_push_pop':
../../root/dpdk/app/test/test_stack_perf.c:255:15: note: source object 'obj' of
size 8
  255 |         void *obj = NULL;
      |               ^~~
In function '__rte_stack_pile_bulk_pop_elems',
    inlined from '__rte_stack_pile_pop' at
../../root/dpdk/lib/stack/rte_stack_pile.h:274:15,
    inlined from 'rte_stack_pop' at
../../root/dpdk/lib/stack/rte_stack.h:205:10,
    inlined from 'test_single_push_pop' at
../../root/dpdk/app/test/test_stack_perf.c:262:3:
../../root/dpdk/lib/eal/arm/include/rte_memcpy_64.h:365:33: error: 'memcpy'
writing 256 bytes into a region of size 8 overflows the destination
[-Werror=stringop-overflow=]
  365 | #define rte_memcpy(d, s, n)     memcpy((d), (s), (n))
      |                                 ^~~~~~~~~~~~~~~~~~~~~
../../root/dpdk/lib/stack/rte_stack_pile.h:75:25: note: in expansion of macro
'rte_memcpy'
   75 |                         rte_memcpy(&obj_table[i *
RTE_STACK_PILE_BULK_SIZE],
      |                         ^~~~~~~~~~
../../root/dpdk/app/test/test_stack_perf.c: In function 'test_single_push_pop':
../../root/dpdk/app/test/test_stack_perf.c:255:15: note: destination object
'obj' of size 8
  255 |         void *obj = NULL;
      |               ^~~
cc1: all warnings being treated as errors
[..]
ninja: build stopped: subcommand failed.

git-bisect points to ee0822a0ef41 ("stack: introduce pile")

Meson: 1.3.2
OS: Ubuntu 24.04.4 LTS
Compiler: gcc (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2026-10-19 13:36 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=bug-2061-3@https.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.