From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Tim Harvey <tharvey@gateworks.com>
Cc: buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] BR2_ARCH_IS_64 NEON support
Date: Mon, 15 Nov 2021 23:36:58 +0100 [thread overview]
Message-ID: <20211115233658.47839c65@windsurf> (raw)
In-Reply-To: <CAJ+vNU0pupEcDjVschLgBW9tdjy6MpnA0WCJE8cSzxqnCy9GGA@mail.gmail.com>
Hello Tim,
On Mon, 15 Nov 2021 13:46:40 -0800
Tim Harvey <tharvey@gateworks.com> wrote:
> I'm curious why NEON is not available for BR2_ARCH_IS_64?
>
> I'm working with boards with IMX8M SoC's which are arm64 and do have
> NEON support (per the NXP literature and I've run binaries using NEON
> on IMX8M). Is this a simple oversight or is there something wrong with
> my understanding of this?
This is explained in commit 0976cd6cd64a128a2ac921e4f35f0e7cbe306692,
which states:
commit 0976cd6cd64a128a2ac921e4f35f0e7cbe306692
Author: Peter Korsgaard <peter@korsgaard.com>
Date: Wed Dec 7 10:25:21 2016 +0100
arch/Config.in.arm: only enable BR2_ARM_CPU_HAS_NEON for ARMv8 in 32bit mode
A number of packages use BR2_ARM_CPU_HAS_NEON to know if the target handles
aarch32 neon instructions, which is only true for ARMv8 cores when they are
running in 32bit mode.
Notice: These cores do support neon-like instructions using a different
encoding in 64bit mode (it is a required part of ARMv8, similar to the FPU).
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
However, it does mean that we need to improve the situation, to also
properly support NEON for ARM 64-bit platforms, exactly as you say.
I'm not sure if this means:
* Fixing packages to use BR2_ARM_CPU_HAS_NEON && !BR2_ARCH_IS_64 when
they use aarch32 neon instructions
* Separating BR2_ARM_CPU_HAS_NEON into BR2_ARM_CPU_HAS_NEON32 and
BR2_ARM_CPU_HAS_NEON64 ?
* Something else?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-11-15 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 21:46 [Buildroot] BR2_ARCH_IS_64 NEON support Tim Harvey
2021-11-15 22:36 ` Thomas Petazzoni [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=20211115233658.47839c65@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=tharvey@gateworks.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