From: Thomas Monjalon <thomas@monjalon.net>
To: Chengwen Feng <fengchengwen@huawei.com>
Cc: ferruh.yigit@intel.com, ruifeng.wang@arm.com, dev@dpdk.org,
bruce.richardson@intel.com, vladimir.medvedkin@intel.com,
viktorin@rehivetech.com, jerinj@marvell.com
Subject: Re: [dpdk-dev] [PATCH v3] build: fix SVE compile error with gcc8.3
Date: Wed, 23 Jun 2021 10:05:37 +0200 [thread overview]
Message-ID: <6856400.AbmscCdnZU@thomas> (raw)
In-Reply-To: <1621562002-10961-1-git-send-email-fengchengwen@huawei.com>
21/05/2021 03:53, Chengwen Feng:
> If the target machine has SVE feature (e.g. "-march=armv8.2-a+sve'),
> and the compiler are gcc8.3, it will compile error:
> In file included from ../dpdk-next-net/lib/eal/common/
> eal_common_options.c:38:
> ../dpdk-next-net/lib/eal/arm/include/rte_vect.h:13:10: fatal
> error: arm_sve.h: No such file or directory
> #include <arm_sve.h>
> ^~~~~~~~~~~
> compilation terminated.
>
> The root cause is that gcc8.3 supports SVE (the macro
> __ARM_FEATURE_SVE was 1), but it doesn't support SVE ACLE [1].
>
> The solution:
> a) Detect compiler whether support SVE ACLE, if support then define
> CC_SVE_ACLE_SUPPORT macro.
> b) Use the CC_SVE_ACLE_SUPPORT macro to include SVE header file.
>
> [1] ACLE: Arm C Language Extensions, the SVE ACLE header file is
> <arm_sve.h>, user should include it when writing ACLE SVE code.
>
> Fixes: 67b68824a82d ("lpm/arm: support SVE")
>
> Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>
> ---
> --- a/config/arm/meson.build
> +++ b/config/arm/meson.build
> +if (cc.get_define('__ARM_FEATURE_SVE', args: machine_args) != '' and
> + cc.check_header('arm_sve.h'))
> + dpdk_conf.set('CC_SVE_ACLE_SUPPORT', 1)
Any defined flag should start with RTE_.
I suggest RTE_HAS_SVE_ACLE.
Please add a comment before defining this flag to explain what it is.
prev parent reply other threads:[~2021-06-23 8:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 7:16 [dpdk-dev] [PATCH] lpm/arm: " Chengwen Feng
2021-05-20 8:17 ` Ruifeng Wang
2021-05-20 11:45 ` fengchengwen
2021-05-20 11:40 ` [dpdk-dev] [PATCH v2] build: " Chengwen Feng
2021-05-20 13:09 ` Bruce Richardson
2021-05-21 1:57 ` fengchengwen
2021-05-21 1:53 ` [dpdk-dev] [PATCH v3] " Chengwen Feng
2021-05-25 6:02 ` Ruifeng Wang
2021-05-27 7:12 ` Fengchengwen
2021-06-12 7:07 ` fengchengwen
2021-06-21 0:56 ` fengchengwen
2021-06-23 8:05 ` 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=6856400.AbmscCdnZU@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=ruifeng.wang@arm.com \
--cc=viktorin@rehivetech.com \
--cc=vladimir.medvedkin@intel.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).