From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Lincoln Lavoie <lylavoie@iol.unh.edu>, 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>,
"Singh, Aman Deep" <aman.deep.singh@intel.com>,
"David Marchand" <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] RHEL7 failures
Date: Tue, 5 Oct 2021 22:46:00 +0100 [thread overview]
Message-ID: <7c1ead6b-6e3a-ad0b-ea80-25dd266db87e@intel.com> (raw)
In-Reply-To: <CAOE1vsOQTj+Gb9P8dShdZwSTs7xp5dHzvxD-oT8qck3j6gLK0A@mail.gmail.com>
On 10/5/2021 8:09 PM, Lincoln Lavoie wrote:
> 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/
>
Issue was reported by David, Aman sent the fix [1] and it is already merged by David [2],
it should be fixed now, can you please double check?
[1]
https://patches.dpdk.org/project/dpdk/patch/20211005115754.34117-1-aman.deep.singh@intel.com/
[2]
https://git.dpdk.org/dpdk/commit/?id=16b809d144dc2df7f31695b5abc64a809021b154
next prev parent reply other threads:[~2021-10-05 21:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 19:09 Lincoln Lavoie
2021-10-05 21:46 ` Ferruh Yigit [this message]
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=7c1ead6b-6e3a-ad0b-ea80-25dd266db87e@intel.com \
--to=ferruh.yigit@intel.com \
--cc=aconole@redhat.com \
--cc=aman.deep.singh@intel.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--cc=lylavoie@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).