public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Shani Peretz <shperetz@nvidia.com>
To: <dev@dpdk.org>
Cc: <thomas@monjalon.net>, Shani Peretz <shperetz@nvidia.com>,
	<stable@dpdk.org>,
	Wathsala Vithanage <wathsala.vithanage@arm.com>,
	"Bruce Richardson" <bruce.richardson@intel.com>
Subject: [PATCH] config/arm: drop crypto extension from armv8.4-a build
Date: Tue, 24 Mar 2026 16:25:45 +0200	[thread overview]
Message-ID: <20260324142546.321236-1-shperetz@nvidia.com> (raw)

Remove the crypto march extension added by commit 6e6cc1dc3548
("config/arm: support crypto with Cortex-A78AE"). The extension
was added under the incorrect assumption that missing crypto ISA
caused an infinite loop, the actual cause was a GCC scheduling
issue with -mcpu=cortex-a78ae. This was avoided by switching to
-march=armv8.4-a in the same commit.

The extension is unnecessary and causes build failures on
toolchains without AES support. The -march=armv8.4-a build
without -mcpu is intentionally kept to avoid the scheduling issue.

Fixes: 6e6cc1dc3548 ("config/arm: support crypto with Cortex-A78AE")
Cc: stable@dpdk.org

Signed-off-by: Shani Peretz <shperetz@nvidia.com>
---
 config/arm/meson.build | 1 -
 1 file changed, 1 deletion(-)

diff --git a/config/arm/meson.build b/config/arm/meson.build
index 523b0fc0ed..5a9c16b9b1 100644
--- a/config/arm/meson.build
+++ b/config/arm/meson.build
@@ -706,7 +706,6 @@ mcpu_defs = {
     },
     'mcpu_cortex-a78ae': {
         'march': 'armv8.4-a',
-        'march_extensions': ['crypto']
     },
     'mcpu_ft2000plus': {
         'march': 'armv8-a',
-- 
2.34.1


             reply	other threads:[~2026-03-24 14:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-24 14:25 Shani Peretz [this message]
2026-03-25 14:28 ` [PATCH] config/arm: drop crypto extension from armv8.4-a build 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=20260324142546.321236-1-shperetz@nvidia.com \
    --to=shperetz@nvidia.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --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