DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: pbhagavatula@marvell.com, jerinj@marvell.com,
	Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, nd@arm.com
Subject: Re: [PATCH 2/2] config/arm: add armv9-a march
Date: Thu, 18 Jan 2024 10:19:12 +0800	[thread overview]
Message-ID: <a85cc799-d9b2-4473-87b6-7a46fe0f0920@arm.com> (raw)
In-Reply-To: <20240104091830.3245-2-pbhagavatula@marvell.com>


On 2024/1/4 5:18 PM, pbhagavatula@marvell.com wrote:
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
> 
> Now that major versions of GCC recognize armv9-a march option,
> add it to the list of supported march.
> Update neoverse-n2 part number to include march as armv9-a.
> 
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> ---
>   config/arm/meson.build | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/config/arm/meson.build b/config/arm/meson.build
> index 36f21d2259..0804877b57 100644
> --- a/config/arm/meson.build
> +++ b/config/arm/meson.build
> @@ -92,6 +92,7 @@ part_number_config_arm = {
>           'march': 'armv8.4-a',
>       },
>       '0xd49': {
> +        'march': 'armv9-a',
>           'march_features': ['sve2'],
>           'compiler_options': ['-mcpu=neoverse-n2'],
>           'flags': [
> @@ -701,7 +702,7 @@ if update_flags
>           if part_number_config.get('force_march', false)
>               candidate_march = part_number_config['march']
>           else
> -            supported_marchs = ['armv8.6-a', 'armv8.5-a', 'armv8.4-a', 'armv8.3-a',
> +            supported_marchs = ['armv9-a', 'armv8.6-a', 'armv8.5-a', 'armv8.4-a', 'armv8.3-a',

armv9.x-a have some overlap with armv8.x-a.
For armv9.0, the next candidate fallback should be armv8.4-a instead of 
armv8.6-a.
armv9 should be treated differently for fallback support.

>                                   'armv8.2-a', 'armv8.1-a', 'armv8-a']
>               check_compiler_support = false
>               foreach supported_march: supported_marchs

  reply	other threads:[~2024-01-18  2:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04  9:18 [PATCH 1/2] config/arm: fix CN10K minimum march requirement pbhagavatula
2024-01-04  9:18 ` [PATCH 2/2] config/arm: add armv9-a march pbhagavatula
2024-01-18  2:19   ` Ruifeng Wang [this message]
2024-01-20  7:09     ` [EXT] " Pavan Nikhilesh Bhagavatula
2024-01-18  2:02 ` [PATCH 1/2] config/arm: fix CN10K minimum march requirement Ruifeng Wang
2024-01-19 19:42   ` [EXT] " Pavan Nikhilesh Bhagavatula

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=a85cc799-d9b2-4473-87b6-7a46fe0f0920@arm.com \
    --to=ruifeng.wang@arm.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=nd@arm.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).