DPDK patches and discussions
 help / color / mirror / Atom feed
From: <pbhagavatula@marvell.com>
To: <jerinj@marvell.com>, Ruifeng Wang <ruifeng.wang@arm.com>,
	"Bruce Richardson" <bruce.richardson@intel.com>
Cc: <dev@dpdk.org>, Pavan Nikhilesh <pbhagavatula@marvell.com>,
	"Srikanth Yalavarthi" <syalavarthi@marvell.com>
Subject: [PATCH v2] config/arm: fix Neoverse N2 march flag
Date: Fri, 9 Jun 2023 01:04:56 +0530	[thread overview]
Message-ID: <20230608193456.11446-1-pbhagavatula@marvell.com> (raw)
In-Reply-To: <20230608072757.9513-1-pbhagavatula@marvell.com>

From: Pavan Nikhilesh <pbhagavatula@marvell.com>

The -march flag of Neoverse N2 should be removed with the introduction
of -mcpu='neoverse-n2' as they are incompatible.

Fixes: ea85ed1f6882 ("config/arm: increase nodes and cores for Neoverse N2")

Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
Tested-by: Srikanth Yalavarthi <syalavarthi@marvell.com>
---
 v2 Changes:
 - Remove adding armv9-a to march as it is incompatible with older GCC.

 config/arm/meson.build | 1 -
 1 file changed, 1 deletion(-)

diff --git a/config/arm/meson.build b/config/arm/meson.build
index 43f6a551a2..ae2226988e 100644
--- a/config/arm/meson.build
+++ b/config/arm/meson.build
@@ -89,7 +89,6 @@ part_number_config_arm = {
         'march': 'armv8.4-a',
     },
     '0xd49': {
-        'march': 'armv8.5-a',
         'march_features': ['sve2'],
         'compiler_options': ['-mcpu=neoverse-n2'],
         'flags': [
--
2.39.1


  parent reply	other threads:[~2023-06-08 19:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08  7:27 [PATCH] " pbhagavatula
2023-06-08  9:54 ` Srikanth Yalavarthi
2023-06-08 10:41 ` Ruifeng Wang
2023-06-08 12:58   ` Pavan Nikhilesh Bhagavatula
2023-06-08 14:20     ` Ruifeng Wang
2023-06-08 19:34 ` pbhagavatula [this message]
2023-06-09  4:02   ` [PATCH v2] " Ruifeng Wang
2023-06-12 17:06     ` 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=20230608193456.11446-1-pbhagavatula@marvell.com \
    --to=pbhagavatula@marvell.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=ruifeng.wang@arm.com \
    --cc=syalavarthi@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).