From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 822] failsafe build fails for gcc12
Date: Mon, 04 Oct 2021 17:36:07 +0000 [thread overview]
Message-ID: <bug-822-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=822
Bug ID: 822
Summary: failsafe build fails for gcc12
Product: DPDK
Version: 20.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: ferruh.yigit@intel.com
Target Milestone: ---
gcc version:
gcc 12.0.0 "gcc (GCC) 12.0.0 20211003 (experimental)"
build error:
failsafe_failsafe_ops.c.o -c ../drivers/net/failsafe/failsafe_ops.c
In file included from ../drivers/net/failsafe/failsafe_ops.c:19:
../drivers/net/failsafe/failsafe_ops.c: In function ‘fs_link_update’:
../drivers/net/failsafe/failsafe_private.h:307:9: error: the comparison will
always evaluate as ‘true’ for the pointer operand in ‘((struct fs_priv
*)dev->data->dev_private)->subs + (sizetype)((long unsigned int)((struct
fs_priv * )dev->data->dev_private)->subs_tx * 904)’ must not be NULL
[-Werror=address]
307 | (PRIV(dev)->subs_tx >= PRIV(dev)->subs_tail ?
NULL \
| ^
../drivers/net/failsafe/failsafe_ops.c:850:13: note: in expansion of macro
‘TX_SUBDEV’
850 | if (TX_SUBDEV(dev)) {
| ^~~~~~~~~
cc1: all warnings being treated as errors
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-10-04 17:36 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-822-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).