From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 739] Building DPDK with gcc 10.2.1 Generates Multiple Warning Messages
Date: Wed, 16 Jun 2021 17:17:38 +0000 [thread overview]
Message-ID: <bug-739-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=739
Bug ID: 739
Summary: Building DPDK with gcc 10.2.1 Generates Multiple
Warning Messages
Product: DPDK
Version: unspecified
Hardware: POWER
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: drc@linux.vnet.ibm.com
Target Milestone: ---
Created attachment 162
--> https://bugs.dpdk.org/attachment.cgi?id=162&action=edit
Full Build Output Including Warnings
Building DPDK 21.08-rc0 with gcc 10.2.1 on RHEL 8.3 generates multiple
warnings, though the final executables appear to work correctly. Examples of
such warnings include:
[115/2415] Compiling C object
'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_trace_utils.c.o'.
../lib/eal/common/eal_common_trace_utils.c: In function
‘trace_epoch_time_save’:
../lib/eal/common/eal_common_trace_utils.c:284:22: note: the layout of
aggregates containing vectors with 8-byte alignment has changed in GCC 5
284 | trace->uptime_ticks = avg;
| ~~~~~~~~~~~~~~~~~~~~^~~~~
[225/2415] Compiling C object 'lib/76b5a35@@rte_acl@sta/acl_acl_gen.c.o'.
../lib/acl/acl_gen.c: In function ‘acl_count_trie_types.constprop’:
../lib/acl/acl_gen.c:220:1: note: the layout of aggregates containing vectors
with 4-byte alignment has changed in GCC 5
220 | acl_count_trie_types(struct acl_node_counters *counts,
| ^~~~~~~~~~~~~~~~~~~~
...
[320/2415] Compiling C object 'lib/76b5a35@@rte_hash@sta/hash_rte_thash.c.o'.
In file included from ../lib/mempool/rte_mempool.h:51,
from ../lib/mbuf/rte_mbuf.h:38,
from ../lib/net/rte_ip.h:31,
from ../lib/hash/rte_thash.h:29,
from ../lib/hash/rte_thash.c:5:
In function ‘rte_memcpy_func’,
inlined from ‘rte_thash_init_ctx’ at ../lib/hash/rte_thash.c:232:3:
../lib/eal/ppc/include/rte_memcpy.h:50:2: warning: writing 16 bytes into a
region of size 0 [-Wstringop-overflow=]
50 | vec_vsx_st(vec_vsx_ld(0, src), 0, dst);
| ^~~~~~~~~~
...
[323/2415] Compiling C object 'lib/76b5a35@@rte_lpm@sta/lpm_rte_lpm.c.o'.
../lib/lpm/rte_lpm.c: In function ‘rte_lpm_create’:
../lib/lpm/rte_lpm.c:240:19: note: the layout of aggregates containing vectors
with 8-byte alignment has changed in GCC 5
240 | i_lpm->max_rules = config->max_rules;
| ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~
[328/2415] Compiling C object
'drivers/a715181@@tmp_rte_net_bnxt@sta/net_bnxt_tf_ulp_bnxt_ulp_flow.c.o'.
../drivers/net/bnxt/tf_ulp/bnxt_ulp_flow.c: In function
‘bnxt_ulp_init_mapper_params’:
../drivers/net/bnxt/tf_ulp/bnxt_ulp_flow.c:78:1: note: the layout of aggregates
containing vectors with 8-byte alignment has changed in GCC 5
78 | bnxt_ulp_init_mapper_params(struct bnxt_ulp_mapper_create_parms
*mapper_cparms,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
...
[1153/2415] Compiling C object
'drivers/a715181@@tmp_rte_net_ena@sta/net_ena_ena_ethdev.c.o'.
In file included from ../lib/net/rte_ether.h:21,
from ../drivers/net/ena/ena_ethdev.c:7:
../drivers/net/ena/ena_ethdev.c: In function ‘ena_rss_key_fill’:
../lib/eal/ppc/include/rte_memcpy.h:53:2: warning: array subscript 3 is outside
array bounds of ‘uint8_t[40]’ {aka ‘unsigned char[40]’} [-Warray-bounds]
53 | vec_vsx_st(vec_vsx_ld(48, src), 48, dst);
| ^~~~~~~~~~
../drivers/net/ena/ena_ethdev.c:277:17: note: while referencing ‘default_key’
277 | static uint8_t default_key[ENA_HASH_KEY_SIZE];
| ^~~~~~~~~~~
In file included from ../lib/net/rte_ether.h:21,
from ../drivers/net/ena/ena_ethdev.c:7:
../lib/eal/ppc/include/rte_memcpy.h:53:2: warning: array subscript [3, 7] is
outside array bounds of ‘uint8_t[40]’ {aka ‘unsigned char[40]’}
[-Warray-bounds]
53 | vec_vsx_st(vec_vsx_ld(48, src), 48, dst);
| ^~~~~~~~~~
../drivers/net/ena/ena_ethdev.c:277:17: note: while referencing ‘default_key’
277 | static uint8_t default_key[ENA_HASH_KEY_SIZE];
| ^~~~~~~~~~~
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-06-16 17: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-739-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).