-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(Re-)Introduce ARMv7+NEON Android and GNU/Linux targets #49897
Comments
Note that |
I thought that ARMv8 guaranteed 128-bit SIMD support like x86_64 guarantees SSE2. Is that not the case? |
It seems that Rust's Programmer’s Guide for ARMv8-A says:
I would hope that the Rust built-in |
I just tried it on stdsimd and aarch64-unknown-linux-gnu does indeed have neon/asimd always enabled :) |
These were added in #49902. |
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: