From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Yongseok Koh <yskoh@mellanox.com>
Cc: jianbo.liu@arm.com, dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal/arm64: fix instrinsic for ARM64 NEON with GCC < 4.9
Date: Wed, 31 Jan 2018 11:12:41 +0530 [thread overview]
Message-ID: <20180131054240.GA11264@jerin> (raw)
In-Reply-To: <20180131000708.32562-1-yskoh@mellanox.com>
-----Original Message-----
> Date: Tue, 30 Jan 2018 16:07:08 -0800
> From: Yongseok Koh <yskoh@mellanox.com>
> To: jerin.jacob@caviumnetworks.com, jianbo.liu@arm.com
> CC: dev@dpdk.org, Yongseok Koh <yskoh@mellanox.com>, stable@dpdk.org
> Subject: [PATCH] eal/arm64: fix instrinsic for ARM64 NEON with GCC < 4.9
> X-Mailer: git-send-email 2.11.0
>
> vceqzq_u32() is being used by mlx5 PMD but added since gcc 4.9.
>
> Fixes: 570acdb1da8a ("net/mlx5: add vectorized Rx/Tx burst for ARM")
> Cc: stable@dpdk.org
>
> Signed-off-by: Yongseok Koh <yskoh@mellanox.com>
Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> ---
> lib/librte_eal/common/include/arch/arm/rte_vect.h | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/lib/librte_eal/common/include/arch/arm/rte_vect.h b/lib/librte_eal/common/include/arch/arm/rte_vect.h
> index 5cc34190f..2a18a6854 100644
> --- a/lib/librte_eal/common/include/arch/arm/rte_vect.h
> +++ b/lib/librte_eal/common/include/arch/arm/rte_vect.h
> @@ -78,6 +78,12 @@ vcopyq_laneq_u32(uint32x4_t a, const int lane_a,
> typedef uint64_t poly64_t;
> typedef uint64x2_t poly64x2_t;
> typedef uint8_t poly128_t __attribute__((vector_size(16), aligned(16)));
> +
> +static inline uint32x4_t
> +vceqzq_u32(uint32x4_t a)
> +{
> + return (a == 0);
> +}
> #endif
>
> /* NEON intrinsic vreinterpretq_u64_p128() is supported since GCC version 7 */
> --
> 2.11.0
>
next prev parent reply other threads:[~2018-01-31 5:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 0:07 Yongseok Koh
2018-01-31 5:42 ` Jerin Jacob [this message]
2018-01-31 11:21 ` 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=20180131054240.GA11264@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=jianbo.liu@arm.com \
--cc=stable@dpdk.org \
--cc=yskoh@mellanox.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).