Package: libarmnn22 Version: 20.08-9 Severity: normal Tags: upstream X-Debbugs-Cc: francis.murt...@arm.com
Dear Maintainer, Neon is optional on Armhf devices and may lead to a crash on user installing the libarmnn-cpuacc-backend22 package and proceeding to choose the CpuAcc backend as a preffered backend. This would be a corner case as the reason for installing armnn is to get performance benefits using Neon, so a user would be unliekely to use a device lacking Neon but it would be nice to cover the case by checking for presence of Neon via HWCAPS. This check will throw an exception that is handled during the registration of the backends during Runtime creation. Thanks, Francis. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: armhf (armv7l) Kernel: Linux 4.15.0-107-generic (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages libarmnn22:armhf depends on: ii libc6 2.31-9 ii libgcc-s1 10.2.1-3 ii libstdc++6 10.2.1-3 libarmnn22:armhf recommends no packages. Versions of packages libarmnn22:armhf suggests: pn libarmnntfliteparser22 <none> pn python3-pyarmnn <none> -- no debconf information
