From: Stephen Hemminger <stephen@networkplumber.org>
To: Piotr Kubaj <pkubaj@FreeBSD.org>
Cc: nicolas.chautru@intel.com, declan.doherty@intel.com,
ciara.power@intel.com, beilei.xing@intel.com,
haiyue.wang@intel.com, jiawenwu@trustnetic.com,
jianwang@trustnetic.com, drc@linux.vnet.ibm.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ppc64le: fix build with Clang
Date: Thu, 29 Jun 2023 09:54:17 -0700 [thread overview]
Message-ID: <20230629095417.48668daf@hermes.local> (raw)
In-Reply-To: <20211014173537.81806-1-pkubaj@FreeBSD.org>
On Thu, 14 Oct 2021 19:35:37 +0200
Piotr Kubaj <pkubaj@FreeBSD.org> wrote:
> Couple of quite common issues:
> 1. In rte_cycles.h, sys/platform/ppc.h and __ppc_get_timebase() are only for glibc.
> 2. In include/rte_atomic.h, the same issue already was encountered on arm64:
> https://mails.dpdk.org/archives/dev/2019-January/123331.html
> 3. In rte_altivec.h, defining vector to __vector is necessary.
> 4. In i40e_rxtx_vec_altivec.c, some type changes from vector unsigned long to
> vector unsigned int is necessary since clang doesn't support vector unsigned
> long very well and deprecated it.
>
> Signed-off-by: Piotr Kubaj <pkubaj@FreeBSD.org>
This patch is several years old and DPDK has changed since then.
I suspect this patch is either out dated or moot now that DPDK has done
a more complete shift to C11 atomics. Could you please either update
or resubmit it if still relavant.
prev parent reply other threads:[~2023-06-29 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 17:35 Piotr Kubaj
2021-10-14 17:57 ` Piotr Kubaj
2021-10-14 18:25 ` Chautru, Nicolas
2023-06-29 16:54 ` Stephen Hemminger [this message]
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=20230629095417.48668daf@hermes.local \
--to=stephen@networkplumber.org \
--cc=beilei.xing@intel.com \
--cc=ciara.power@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=haiyue.wang@intel.com \
--cc=jianwang@trustnetic.com \
--cc=jiawenwu@trustnetic.com \
--cc=nicolas.chautru@intel.com \
--cc=pkubaj@FreeBSD.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).