From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 857] gcc12 build error, lib/mbuf
Date: Thu, 28 Oct 2021 12:41:39 +0000 [thread overview]
Message-ID: <bug-857-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=857
Bug ID: 857
Summary: gcc12 build error, lib/mbuf
Product: DPDK
Version: 20.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: ferruh.yigit@intel.com
Target Milestone: ---
With gcc 12.0.0 "gcc (GCC) 12.0.0 20211024 (experimental)"
../lib/mbuf/rte_mbuf_dyn.c: In function ‘rte_mbuf_dynflag_lookup’:
../lib/mbuf/rte_mbuf_dyn.c:397:17: warning: ‘memcpy’ reading 68 bytes from a
region of size 64 [-Wstringop-overread]
397 | memcpy(params, &mbuf_dynflag->params, sizeof(*params));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from ../lib/mbuf/rte_mbuf_dyn.c:18:
../lib/mbuf/rte_mbuf_dyn.h:98:14: note: source object ‘name’ of size 64
98 | char name[RTE_MBUF_DYN_NAMESIZE]; /**< Name of the dynamic
flag. */
| ^~~~
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-10-28 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 12:41 bugzilla [this message]
2022-06-15 8:23 ` [Bug 857] gcc12 build error, lib/mbuf bugzilla
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-857-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 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.