From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 991] [19.11] net/ena build failure with gcc 12
Date: Sun, 03 Apr 2022 11:54:21 +0000 [thread overview]
Message-ID: <bug-991-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=991
Bug ID: 991
Summary: [19.11] net/ena build failure with gcc 12
Product: DPDK
Version: 19.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: alialnu@nvidia.com
Target Milestone: ---
"""
$ meson --werror -Dc_args='-DRTE_ENABLE_ASSERT' --buildtype=debug build &&
ninja-build -C build
[..]
FAILED: drivers/libtmp_rte_pmd_ena.a.p/net_ena_ena_ethdev.c.o
gcc -Idrivers/libtmp_rte_pmd_ena.a.p -Idrivers -I../../root/dpdk/drivers
-Idrivers/net/ena -I../../root/dpdk/drivers/net/ena
-I../../root/dpdk/drivers/net/ena/base
-I../../root/dpdk/drivers/net/ena/base/ena_defs -Ilib/librte_ethdev
-I../../root/dpdk/lib/librte_ethdev -I. -I../../root/dpdk -Iconfig
-I../../root/dpdk/config -Ilib/librte_eal/common/include
-I../../root/dpdk/lib/librte_eal/common/include
-I../../root/dpdk/lib/librte_eal/linux/eal/include -Ilib/librte_eal/common
-I../../root/dpdk/lib/librte_eal/common
-Ilib/librte_eal/common/include/arch/x86
-I../../root/dpdk/lib/librte_eal/common/include/arch/x86 -Ilib/librte_eal
-I../../root/dpdk/lib/librte_eal -Ilib/librte_kvargs
-I../../root/dpdk/lib/librte_kvargs -Ilib/librte_net
-I../../root/dpdk/lib/librte_net -Ilib/librte_mbuf
-I../../root/dpdk/lib/librte_mbuf -Ilib/librte_mempool
-I../../root/dpdk/lib/librte_mempool -Ilib/librte_ring
-I../../root/dpdk/lib/librte_ring -Ilib/librte_meter
-I../../root/dpdk/lib/librte_meter -Idrivers/bus/pci
-I../../root/dpdk/drivers/bus/pci -I../../root/dpdk/drivers/bus/pci/linux
-Ilib/librte_pci -I../../root/dpdk/lib/librte_pci -Idrivers/bus/vdev
-I../../root/dpdk/drivers/bus/vdev -Ilib/librte_timer
-I../../root/dpdk/lib/librte_timer -fdiagnostics-color=always
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -g -include
rte_config.h -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral
-Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs
-Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes
-Wundef -Wwrite-strings -Wno-address-of-packed-member -Wno-packed-not-aligned
-Wno-missing-field-initializers -Wno-zero-length-bounds -D_GNU_SOURCE
-DRTE_ENABLE_ASSERT -DRTE_LIBRTE_MLX4_DEBUG -DRTE_LIBRTE_MLX5_DEBUG -fPIC
-march=native -Wno-format-truncation -DALLOW_EXPERIMENTAL_API -MD -MQ
drivers/libtmp_rte_pmd_ena.a.p/net_ena_ena_ethdev.c.o -MF
drivers/libtmp_rte_pmd_ena.a.p/net_ena_ena_ethdev.c.o.d -o
drivers/libtmp_rte_pmd_ena.a.p/net_ena_ena_ethdev.c.o -c
../../root/dpdk/drivers/net/ena/ena_ethdev.c
../../root/dpdk/drivers/net/ena/ena_ethdev.c: In function 'ena_rss_reta_query':
../../root/dpdk/drivers/net/ena/ena_ethdev.c:605:66: error: the comparison will
always evaluate as 'false' for the pointer operand in 'reta_conf + 136' must
not be NULL [-Werror=address]
605 | (reta_size > RTE_RETA_GROUP_SIZE && ((reta_conf + 1) ==
NULL)))
| ^~
cc1: all warnings being treated as errors
[..]
"""
OS: Fedora Linux 37 (Rawhide)
gcc: 12.0.1 20220308 (Red Hat 12.0.1-0)
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2022-04-03 11:54 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-991-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).