From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: dev <dev@dpdk.org>, Qiming Yang <qiming.yang@intel.com>,
Qi Zhang <qi.z.zhang@intel.com>
Cc: ci@dpdk.org, Aaron Conole <aconole@redhat.com>,
dpdklab <dpdklab@iol.unh.edu>
Subject: [dpdk-dev] RHEL7 failures
Date: Tue, 5 Oct 2021 15:09:05 -0400 [thread overview]
Message-ID: <CAOE1vsOQTj+Gb9P8dShdZwSTs7xp5dHzvxD-oT8qck3j6gLK0A@mail.gmail.com> (raw)
Hello Qiming and Qi,
The CI is picking up failures when building on RHEL7, where warnings are
being treated as errors. This looks like something has been merged into
the mainline, as it's failing across all patches.
Here is the specific failure:
./drivers/net/ice/base/ice_parser_rt.c: In function '_hv_bit_sel':
../drivers/net/ice/base/ice_parser_rt.c:201:2: error: dereferencing
type-punned pointer will break strict-aliasing rules
[-Werror=strict-aliasing]
d64 = *(u64 *)&b[0];
^
../drivers/net/ice/base/ice_parser_rt.c: In function '_reg_bit_sel':
../drivers/net/ice/base/ice_parser_rt.c:458:2: error: dereferencing
type-punned pointer will break strict-aliasing rules
[-Werror=strict-aliasing]
d32 = *(u32 *)&v[0];
^
cc1: all warnings being treated as errors
You can download a full set of logs from here (for a failing run):
https://lab.dpdk.org/results/dashboard/patchsets/19162/
Cheers,
Lincoln
--
*Lincoln Lavoie*
Principal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu>
next reply other threads:[~2021-10-05 19:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 19:09 Lincoln Lavoie [this message]
2021-10-05 21:46 ` Ferruh Yigit
2021-10-06 12:39 ` Lincoln Lavoie
2021-10-07 3:40 ` Zhang, Qi Z
2021-10-11 14:39 ` Thinh Tran
2021-10-11 14:42 ` Lincoln Lavoie
2021-10-11 16:39 ` Thinh Tran
2021-10-11 17:17 ` [dpdk-dev] [dpdk-ci] " Brandon Lo
2021-10-11 22:45 ` Thinh Tran
2021-10-12 0:57 ` Ferruh Yigit
2021-10-12 12:39 ` Lincoln Lavoie
2021-10-12 13:32 ` Ferruh Yigit
2021-10-12 13:57 ` Thomas Monjalon
2021-10-12 13:49 ` Thinh Tran
2021-10-12 13:50 ` Juraj Linkeš
2021-10-12 14:00 ` Thomas Monjalon
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=CAOE1vsOQTj+Gb9P8dShdZwSTs7xp5dHzvxD-oT8qck3j6gLK0A@mail.gmail.com \
--to=lylavoie@iol.unh.edu \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
/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).