From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1195] Building DPDK with gcc 12 Generates stringop-overflow warnings on RHEL 8.7
Date: Tue, 21 Mar 2023 22:37:10 +0000 [thread overview]
Message-ID: <bug-1195-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1835 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1195
Bug ID: 1195
Summary: Building DPDK with gcc 12 Generates stringop-overflow
warnings on RHEL 8.7
Product: DPDK
Version: 23.03
Hardware: POWER
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: drc@linux.vnet.ibm.com
Target Milestone: ---
Building DPDK 23.03-rc3 on ppc64le systems with RHEL 8.7 and gcc-toolset-12
(gcc v12.2.1) generates stringop-overflow overflow warnings:
[1641/2397] Compiling C object
drivers/libtmp_rte_net_tap.a.p/net_tap_rte_eth_tap.c.o
In function ‘parse_user_mac’,
inlined from ‘set_mac_type’ at ../drivers/net/tap/rte_eth_tap.c:2314:6:
../drivers/net/tap/rte_eth_tap.c:2286:47: warning: writing 1 byte into a region
of size 0 [-Wstringop-overflow=]
2286 | user_mac->addr_bytes[index++] = strtoul(mac_byte, NULL,
16);
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from ../lib/ethdev/rte_eth_ctrl.h:10,
from ../lib/ethdev/rte_ethdev.h:1421,
from ../lib/ethdev/ethdev_driver.h:24,
from ../drivers/net/tap/rte_eth_tap.c:10:
../lib/net/rte_ether.h: In function ‘set_mac_type’:
../lib/net/rte_ether.h:61:17: note: at offset 6 into destination object
‘addr_bytes’ of size 6
61 | uint8_t addr_bytes[RTE_ETHER_ADDR_LEN]; /**< Addr bytes in tx
order */
| ^~~~~~~~~~
Warning is not observed when building on an x86_64 system with RHEL 8.7 and
gcc-toolset-12.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3722 bytes --]
reply other threads:[~2023-03-21 22:37 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-1195-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).