From: David Marchand <david.marchand@redhat.com>
To: Joyce Kong <joyce.kong@arm.com>
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>,
Ilya Maximets <i.maximets@ovn.org>,
"Ruifeng Wang (Arm Technology China)" <ruifeng.wang@arm.com>,
Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
dev <dev@dpdk.org>, nd <nd@arm.com>,
subhim@nvidia.com
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v1] net/virtio: fix compiling issue for vectorized NEON path
Date: Tue, 26 Jan 2021 10:25:25 +0100 [thread overview]
Message-ID: <CAJFAV8x9NxqHkJmHA5ku=dSY_Ft-epks0uF8zCzpQf07B7dVvQ@mail.gmail.com> (raw)
In-Reply-To: <20210126091736.55586-1-joyce.kong@arm.com>
On Tue, Jan 26, 2021 at 10:20 AM Joyce Kong <joyce.kong@arm.com> wrote:
>
> In file included from ../drivers/net/virtio/virtio_rxtx_packed.c:22:0:
> ../drivers/net/virtio/virtio_rxtx_packed_neon.h: In function
> ‘virtqueue_enqueue_batch_packed_vec’:
> ../drivers/net/virtio/virtio_rxtx_packed_neon.h:74:2: warning:
> implicit declaration of function ‘vreinterpretq_p128_u32’
> [-Wimplicit-function-declaration]
> poly128_t cmp1 = vreinterpretq_p128_u32(~vceqq_u32(ref_seg, def_ref_seg));
> ^
>
> The message shows ‘vreinterpretq_p128_u32’ instrisic is not supported
intrinsic*
> because an old version gcc (gcc 4.8.5) was used. So fix the issue with
> implementing the logic with other intrinsics.
>
> Bugzilla ID: 621
> Fixes: 530887469350 ("net/virtio: add vectorized packed ring NEON Tx")
> Fixes: 5971ce5e2a59 ("net/virtio: add vectorized packed ring NEON Rx")
> Cc: stable@dpdk.org
No reason to copy stable@dpdk.org.
Cc: reporter.
--
David Marchand
next prev parent reply other threads:[~2021-01-26 9:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 9:17 [dpdk-dev] " Joyce Kong
2021-01-26 9:25 ` David Marchand [this message]
2021-01-26 9:57 ` [dpdk-dev] [PATCH v2] " Joyce Kong
2021-01-27 5:18 ` Ruifeng Wang
2021-01-27 8:44 ` Maxime Coquelin
2021-01-27 10:37 ` Subhi Masri
2021-01-27 11:52 ` Maxime Coquelin
2021-01-27 10:43 ` Maxime Coquelin
2021-01-27 12:01 ` Maxime Coquelin
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='CAJFAV8x9NxqHkJmHA5ku=dSY_Ft-epks0uF8zCzpQf07B7dVvQ@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=i.maximets@ovn.org \
--cc=joyce.kong@arm.com \
--cc=maxime.coquelin@redhat.com \
--cc=nd@arm.com \
--cc=ruifeng.wang@arm.com \
--cc=subhim@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).