From: Jerin Jacob <jerinjacobk@gmail.com>
To: Anoob Joseph <anoobj@marvell.com>
Cc: "Honnappa Nagarahalli" <honnappa.nagarahalli@arm.com>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>,
thomas@monjalon.net, david.marchand@redhat.com,
"Jerin Jacob" <jerinj@marvell.com>,
nd@arm.com, "Pavan Nikhilesh" <pbhagavatula@marvell.com>,
"Ruifeng Wang" <ruifeng.wang@arm.com>,
wathsala.vithanage@arm.com, dev@dpdk.org
Subject: Re: [PATCH] config/arm: add fallback march for Neoverse V2
Date: Thu, 14 Mar 2024 17:35:55 +0530 [thread overview]
Message-ID: <CALBAE1PMHX_fTQkx7g-aoP3zmKS_oBeoz+ZSfGXtF4ZR2fXhVQ@mail.gmail.com> (raw)
In-Reply-To: <20240307080627.177-1-anoobj@marvell.com>
On Thu, Mar 7, 2024 at 1:36 PM Anoob Joseph <anoobj@marvell.com> wrote:
>
> Add march & fallback march for Neoverse V2 to support build with older
> compilers that doesn't support mcpu = 'neoverse-v2'.
>
> Signed-off-by: Anoob Joseph <anoobj@marvell.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
> ---
>
> Depends-on: series-31402 ("config/arm: avoid mcpu and march conflicts")
>
> config/arm/meson.build | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/config/arm/meson.build b/config/arm/meson.build
> index 3f5fb0f242..2e655ece05 100644
> --- a/config/arm/meson.build
> +++ b/config/arm/meson.build
> @@ -106,8 +106,10 @@ part_number_config_arm = {
> ]
> },
> '0xd4f': {
> + 'march': 'armv9-a',
> 'march_features': ['sve2'],
> - 'compiler_options': ['-mcpu=neoverse-v2'],
> + 'mcpu': 'neoverse-v2',
> + 'fallback_march': 'armv8.5-a',
> 'flags': [
> ['RTE_MACHINE', '"neoverse-v2"'],
> ['RTE_ARM_FEATURE_ATOMICS', true],
> --
> 2.25.1
>
next prev parent reply other threads:[~2024-03-14 12:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 8:06 Anoob Joseph
2024-03-14 12:05 ` Jerin Jacob [this message]
2024-03-15 11:22 ` 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=CALBAE1PMHX_fTQkx7g-aoP3zmKS_oBeoz+ZSfGXtF4ZR2fXhVQ@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=anoobj@marvell.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerinj@marvell.com \
--cc=juraj.linkes@pantheon.tech \
--cc=nd@arm.com \
--cc=pbhagavatula@marvell.com \
--cc=ruifeng.wang@arm.com \
--cc=thomas@monjalon.net \
--cc=wathsala.vithanage@arm.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).