diff options
| author | Jubilee Young <workingjubilee@gmail.com> | 2021-12-03 17:56:59 -0800 |
|---|---|---|
| committer | Jubilee Young <workingjubilee@gmail.com> | 2022-03-22 15:14:33 -0700 |
| commit | b807d5970bd5b20d2dd22d76a05a4f65dbea03a5 (patch) | |
| tree | b68676f8ec66ef17dab7f634b03a6b77163bcb78 /src/test/codegen/src-hash-algorithm/src-hash-algorithm-md5.rs | |
| parent | 58f11791af4f97572e7afd83f11cffe04bbbd12f (diff) | |
| download | rust-b807d5970bd5b20d2dd22d76a05a4f65dbea03a5.tar.gz rust-b807d5970bd5b20d2dd22d76a05a4f65dbea03a5.zip | |
Fold aarch64 feature +fp into +neon
Arm's FEAT_FP and Feat_AdvSIMD describe the same thing on AArch64: The Neon unit, which handles both floating point and SIMD instructions. Moreover, a configuration for AArch64 must include both or neither. Arm says "entirely proprietary" toolchains may omit floating point: https://developer.arm.com/documentation/102374/0101/Data-processing---floating-point In the Programmer's Guide for Armv8-A, Arm says AArch64 can have both FP and Neon or neither in custom implementations: https://developer.arm.com/documentation/den0024/a/AArch64-Floating-point-and-NEON In "Bare metal boot code for Armv8-A", enabling Neon and FP is just disabling the same trap flag: https://developer.arm.com/documentation/dai0527/a In an unlikely future where "Neon and FP" become unrelated, we can add "[+-]fp" as its own feature flag. Until then, we can simplify programming with Rust on AArch64 by folding both into "[+-]neon", which is valid as it supersets both. "[+-]neon" is retained for niche uses such as firmware, kernels, "I just hate floats", and so on.
Diffstat (limited to 'src/test/codegen/src-hash-algorithm/src-hash-algorithm-md5.rs')
0 files changed, 0 insertions, 0 deletions
