From: Ali Alnubani <alialnu@nvidia.com>
To: David Marchand <david.marchand@redhat.com>,
Andre Muezerie <andremue@linux.microsoft.com>
Cc: David Christensen <drc@linux.ibm.com>,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] drivers/net: fix cast-qual and strict-aliasing errors for ppc64le
Date: Thu, 30 Jan 2025 08:07:02 +0000 [thread overview]
Message-ID: <PH7PR12MB9173C2720FC0000164F84C95DAE92@PH7PR12MB9173.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8zzgnRciyizsAwatLNQEiGCYDEr2QEbYFOja4nGYM=8sw@mail.gmail.com>
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Thursday, January 30, 2025 10:02 AM
> To: Andre Muezerie <andremue@linux.microsoft.com>; Ali Alnubani
> <alialnu@nvidia.com>
> Cc: David Christensen <drc@linux.ibm.com>; Dariusz Sosnowski
> <dsosnowski@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>; Bing
> Zhao <bingz@nvidia.com>; Ori Kam <orika@nvidia.com>; Suanming Mou
> <suanmingm@nvidia.com>; Matan Azrad <matan@nvidia.com>; dev@dpdk.org
> Subject: Re: [PATCH] drivers/net: fix cast-qual and strict-aliasing errors for
> ppc64le
>
> On Wed, Jan 29, 2025 at 6:36 PM Andre Muezerie
> <andremue@linux.microsoft.com> wrote:
> >
> > During a recent cleanup a few lines were missed which are causing
> > errors on ppc64le, like the ones below:
> >
> > drivers/net/mlx5/mlx5_rxtx_vec_altivec.h:77:17: error: cast discards
> > ‘volatile’ qualifier from pointer target type [-Werror=cast-qual]
> >
> > lib/eal/include/rte_common.h:557:34: warning: dereferencing type-punned
> > pointer will break strict-aliasing rules [-Wstrict-aliasing]
> >
> > Signed-off-by: Andre Muezerie <andremue@linux.microsoft.com>
>
> Thank you André, this fixes the build error reported by OBS (I tested
> with my dpdk project in OBS).
> Ali, I'll wait for your test report.
Can confirm it resolves the build failure in my environment.
Tested-by: Ali Alnubani <alialnu@nvidia.com>
Thanks,
Ali
>
>
> --
> David Marchand
next prev parent reply other threads:[~2025-01-30 8:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 17:35 Andre Muezerie
2025-01-30 8:02 ` David Marchand
2025-01-30 8:07 ` Ali Alnubani [this message]
2025-01-30 8:15 ` David Marchand
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=PH7PR12MB9173C2720FC0000164F84C95DAE92@PH7PR12MB9173.namprd12.prod.outlook.com \
--to=alialnu@nvidia.com \
--cc=andremue@linux.microsoft.com \
--cc=bingz@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=drc@linux.ibm.com \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@nvidia.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).