All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Bara <bbara93@gmail.com>
To: ross.burton@arm.com
Cc: bbara93@gmail.com, benjamin.bara@skidata.com,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] insane.bbclass: introduce SIGILL finder
Date: Mon,  4 Sep 2023 09:39:46 +0200	[thread overview]
Message-ID: <20230904073946.4134459-1-bbara93@gmail.com> (raw)
In-Reply-To: <0E234875-B7BC-46F4-B830-2DB4A9230955@arm.com>

Hi Ross,

On Fri, 1 Sept 2023 at 12:19, Ross Burton <Ross.Burton@arm.com> wrote:
> On 31 Aug 2023, at 10:16, Benjamin Bara via lists.openembedded.org <bbara93=gmail.com@lists.openembedded.org> wrote:
> >
> > From: Benjamin Bara <benjamin.bara@skidata.com>
> >
> > This commit should look for unsupported instructions depending on the
> > active tune features. For now, it checks for vfpv3d16 and other non-neon
> > machines, but it can be easily extended for other architectures/checks.
> >
> > Reason for this check is that a couple of packages assume neon support
> > for armv7, but it is actually optional.
>
> Presumably this will trigger on recipes which generate the code for all the extended instructions (neon, sve, etc) and pick and runtime what functions to run?

Yep, that's true. So far, I found openssl[1] and pulseaudio[2], but I am still
testing. I would insane_skip these in a V2 if it is considered useful.

Regards,
Benjamin

[1] https://github.com/openssl/openssl/blob/openssl-3.1.2/crypto/armcap.c#L71
[2] https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/blob/v16.1/src/pulsecore/cpu-arm.c?ref_type=tags#L115


      reply	other threads:[~2023-09-04  7:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31  9:16 [PATCH] insane.bbclass: introduce SIGILL finder Benjamin Bara
2023-08-31  9:24 ` [OE-core] " Alexander Kanavin
2023-08-31 10:22   ` Benjamin Bara
2023-09-01 10:19 ` Ross Burton
2023-09-04  7:39   ` Benjamin Bara [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=20230904073946.4134459-1-bbara93@gmail.com \
    --to=bbara93@gmail.com \
    --cc=benjamin.bara@skidata.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.