Hi Ross,
On Fri, 1 Sept 2023 at 12:19, Ross Burton wrote:
> On 31 Aug 2023, at 10:16, Benjamin Bara via lists.openembedded.org
> wrote:
> >
> > From: Benjamin Bara
> >
> > This commit should look for unsupported instructions depending on the
> > active tune features. For now, it checks for
On 31 Aug 2023, at 10:16, Benjamin Bara via lists.openembedded.org
wrote:
>
> From: Benjamin Bara
>
> 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
Hi Alex,
thanks for the feedback!
On Thu, 31 Aug 2023 at 11:24, Alexander Kanavin wrote:
> objdump -d is a heavy operation, and the problem is both arm-specific
> and rare. Also SIGILL is a very clear indicator of what the problem
> is, even if it's annoying to see it at runtime.
As the grep
objdump -d is a heavy operation, and the problem is both arm-specific
and rare. Also SIGILL is a very clear indicator of what the problem
is, even if it's annoying to see it at runtime.
I don't think this should happen across all builds and components.
Alex
On Thu, 31 Aug 2023 at 11:16,
From: Benjamin Bara
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
