(Re-)Introduce ARMv7+NEON Android and GNU/Linux targets #49897
Labels
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
O-android
Operating system: Android
O-Arm
Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Even though ARMv7 Android doesn't guarantee the presence of NEON, most devices have it and e.g. Firefox opts not to support ARMv7 devices that don't have it. (Notably the Tegra 2-based ones.)
To allow Rust code, including the standard library, to unconditionally use NEON in such a scenario, it would help a lot if upstream Rust supported an ARMv7+NEON Android target. (NEON support was explicitly removed from
armv7-linux-androideabi
.In order to test code on a system that has all the usual tooling, it's useful to have a corresponding GNU/Linux target, too. NEON was explicitly removed from
armv7-unknown-linux-gnueabihf
and also fromarmv7-unknown-linux-musleabihf
.Please add new
androideabi
andgnueabihf
ARMv7 targets that have NEON enabled and a NEON-enabled standard library shipped viarustup
so thatstd::simd
ends up compiled with NEON enabled. (See the issue about boolean reductions there.)How to name these is a total bikeshed, but as a starting point, I suggest
armv7neon-unknown-linux-gnueabihf
andarmv7neon-linux-androideabi
.The text was updated successfully, but these errors were encountered: