From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1062] GCC 12 build errors with --buildtype=debug
Date: Thu, 04 Aug 2022 09:17:26 +0000 [thread overview]
Message-ID: <bug-1062-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1062
Bug ID: 1062
Summary: GCC 12 build errors with --buildtype=debug
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: jerinjacobk@gmail.com
Target Milestone: ---
Reproducer:
meson --werror --buildtype=debug build
ninja -C build
gcc version:
gcc version 12.1.1 20220730 (GCC) (Archlinux)
Log:
../lib/eventdev/rte_event_eth_rx_adapter.c: In function
‘rxa_intr_ring_dequeue’:
../lib/eventdev/rte_event_eth_rx_adapter.c:1213:34: note: destination object
‘qd’ of size 8
1213 | union queue_data qd = rx_adapter->qd;
| ^~
In function ‘__rte_ring_dequeue_elems_128’,
inlined from ‘__rte_ring_dequeue_elems’ at
../lib/ring/rte_ring_elem_pvt.h:262:3,
inlined from ‘__rte_ring_do_hts_dequeue_elem’ at
../lib/ring/rte_ring_hts_elem_pvt.h:237:3,
inlined from ‘rte_ring_mc_hts_dequeue_bulk_elem’ at
../lib/ring/rte_ring_hts.h:83:9,
inlined from ‘rte_ring_dequeue_bulk_elem’ at
../lib/ring/rte_ring_elem.h:391:10,
inlined from ‘rte_ring_dequeue_elem’ at ../lib/ring/rte_ring_elem.h:476:9,
inlined from ‘rte_ring_dequeue’ at ../lib/ring/rte_ring.h:480:9,
inlined from ‘rxa_intr_ring_dequeue’ at
../lib/eventdev/rte_event_eth_rx_adapter.c:1220:10:
../lib/ring/rte_ring_elem_pvt.h:234:25: error: ‘memcpy’ writing 32 bytes into a
region of size 8 overflows the destination [-Werror=stringop-overflow=]
234 | memcpy((void *)(obj + i), (void *)(ring + idx),
32);
|
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/eventdev/rte_event_eth_rx_adapter.c: In function
‘rxa_intr_ring_dequeue’:
../lib/eventdev/rte_event_eth_rx_adapter.c:1213:34: note: destination object
‘qd’ of size 8
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2022-08-04 9:17 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-1062-3@http.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).