From: Thomas Monjalon <thomas@monjalon.net>
To: pbhagavatula@marvell.com
Cc: dev@dpdk.org, gavin.hu@arm.com, jerinj@marvell.com
Subject: Re: [dpdk-dev] [PATCH v2] mempool/octeontx2: fix arm64 clang build failure
Date: Fri, 05 Jul 2019 11:02:31 +0200 [thread overview]
Message-ID: <1966653.7aN1hUl6W2@xps> (raw)
In-Reply-To: <20190705042650.3457-1-pbhagavatula@marvell.com>
05/07/2019 06:26, pbhagavatula@marvell.com:
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> The ARMv8.1 CASP instruction works with even register pairs and since
> there no register constraint in older versions of GCC/Clang, use
> explicit register allocation to satisfy CASP requirements.
> Remove function level optimization specification as Clang doesnt have
> support for it and explicit register allocation removes the need for it.
>
> Fixes build issue with arm64-armv8a-linux-clang.
>
> Fixes: ee338015e7a9 ("mempool/octeontx2: add optimized dequeue operation for arm64")
>
> Reported-by: Gavin Hu <gavin.hu@arm.com>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied, thanks
prev parent reply other threads:[~2019-07-05 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 4:26 pbhagavatula
2019-07-05 9:02 ` Thomas Monjalon [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=1966653.7aN1hUl6W2@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=gavin.hu@arm.com \
--cc=jerinj@marvell.com \
--cc=pbhagavatula@marvell.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).