-
Notifications
You must be signed in to change notification settings - Fork 12.7k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Rollup merge of #91608 - workingjubilee:fold-neon-fp, r=nagisa,Amanieu
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. I am... pretty sure no one is relying on this. An argument could be made that, as we are not an "entirely proprietary" toolchain, we should not support AArch64 without floats at all. I think that's a bit excessive. However, I want to recognize the intent: programming for AArch64 should be simplified where possible. For x86-64, programmers regularly set up illegal feature configurations because it's hard to understand them, see #89586. And per the above notes, plus the discussion in #86941, there should be no real use cases for leaving these features split: the two should in fact always go together. - Fixes #95002. - Fixes #95064. - Fixes #95122.
- Loading branch information
Showing
9 changed files
with
155 additions
and
12 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
// only-aarch64 | ||
// run-pass | ||
#![allow(dead_code)] | ||
use std::arch::*; | ||
use std::arch::aarch64::*; | ||
|
||
// Smoke test to verify aarch64 code that enables NEON compiles. | ||
fn main() { | ||
let _zero = if is_aarch64_feature_detected!("neon") { | ||
unsafe { | ||
let zeros = zero_vector(); | ||
vgetq_lane_u8::<1>(zeros) | ||
} | ||
} else { | ||
0 | ||
}; | ||
} | ||
|
||
|
||
#[target_feature(enable = "neon")] | ||
unsafe fn zero_vector() -> uint8x16_t { | ||
vmovq_n_u8(0) | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,58 @@ | ||
// revisions: aarch64-neon aarch64-sve2 | ||
// [aarch64-neon] compile-flags: -Ctarget-feature=+neon --target=aarch64-unknown-linux-gnu | ||
// [aarch64-neon] needs-llvm-components: aarch64 | ||
// [aarch64-sve2] compile-flags: -Ctarget-feature=-neon,+sve2 --target=aarch64-unknown-linux-gnu | ||
// [aarch64-sve2] needs-llvm-components: aarch64 | ||
// build-pass | ||
#![no_core] | ||
#![crate_type = "rlib"] | ||
#![feature(intrinsics, rustc_attrs, no_core, lang_items, staged_api)] | ||
#![stable(feature = "test", since = "1.0.0")] | ||
|
||
// Tests vetting "feature hierarchies" in the cases where we impose them. | ||
|
||
// Supporting minimal rust core code | ||
#[lang = "sized"] | ||
trait Sized {} | ||
#[lang = "copy"] | ||
trait Copy {} | ||
impl Copy for bool {} | ||
|
||
extern "rust-intrinsic" { | ||
#[rustc_const_stable(feature = "test", since = "1.0.0")] | ||
fn unreachable() -> !; | ||
} | ||
|
||
#[rustc_builtin_macro] | ||
macro_rules! cfg { | ||
($($cfg:tt)*) => {}; | ||
} | ||
|
||
// Test code | ||
const fn do_or_die(cond: bool) { | ||
if cond { | ||
} else { | ||
unsafe { unreachable() } | ||
} | ||
} | ||
|
||
macro_rules! assert { | ||
($x:expr $(,)?) => { | ||
const _: () = do_or_die($x); | ||
}; | ||
} | ||
|
||
|
||
#[cfg(aarch64_neon)] | ||
fn check_neon_not_sve2() { | ||
// This checks that a normal aarch64 target doesn't suddenly jump up the feature hierarchy. | ||
assert!(cfg!(target_feature = "neon")); | ||
assert!(cfg!(not(target_feature = "sve2"))); | ||
} | ||
|
||
#[cfg(aarch64_sve2)] | ||
fn check_sve2_includes_neon() { | ||
// This checks that aarch64's sve2 includes neon | ||
assert!(cfg!(target_feature = "neon")); | ||
assert!(cfg!(target_feature = "sve2")); | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,64 @@ | ||
// revisions: aarch64 x86-64 | ||
// [aarch64] compile-flags: -Ctarget-feature=+neon,+fp16,+fhm --target=aarch64-unknown-linux-gnu | ||
// [aarch64] needs-llvm-components: aarch64 | ||
// [x86-64] compile-flags: -Ctarget-feature=+sse4.2,+rdrand --target=x86_64-unknown-linux-gnu | ||
// [x86-64] needs-llvm-components: x86 | ||
// build-pass | ||
#![no_core] | ||
#![crate_type = "rlib"] | ||
#![feature(intrinsics, rustc_attrs, no_core, lang_items, staged_api)] | ||
#![stable(feature = "test", since = "1.0.0")] | ||
|
||
// Supporting minimal rust core code | ||
#[lang = "sized"] | ||
trait Sized {} | ||
#[lang = "copy"] | ||
trait Copy {} | ||
impl Copy for bool {} | ||
|
||
extern "rust-intrinsic" { | ||
#[rustc_const_stable(feature = "test", since = "1.0.0")] | ||
fn unreachable() -> !; | ||
} | ||
|
||
#[rustc_builtin_macro] | ||
macro_rules! cfg { | ||
($($cfg:tt)*) => {}; | ||
} | ||
|
||
// Test code | ||
const fn do_or_die(cond: bool) { | ||
if cond { | ||
} else { | ||
unsafe { unreachable() } | ||
} | ||
} | ||
|
||
macro_rules! assert { | ||
($x:expr $(,)?) => { | ||
const _: () = do_or_die($x); | ||
}; | ||
} | ||
|
||
|
||
#[cfg(target_arch = "aarch64")] | ||
fn check_aarch64() { | ||
// This checks that the rustc feature name is used, not the LLVM feature. | ||
assert!(cfg!(target_feature = "neon")); | ||
assert!(cfg!(not(target_feature = "fp-armv8"))); | ||
assert!(cfg!(target_feature = "fhm")); | ||
assert!(cfg!(not(target_feature = "fp16fml"))); | ||
assert!(cfg!(target_feature = "fp16")); | ||
assert!(cfg!(not(target_feature = "fullfp16"))); | ||
} | ||
|
||
#[cfg(target_arch = "x86_64")] | ||
fn check_x86_64() { | ||
// This checks that the rustc feature name is used, not the LLVM feature. | ||
assert!(cfg!(target_feature = "rdrand")); | ||
assert!(cfg!(not(target_feature = "rdrnd"))); | ||
|
||
// Likewise: We enable LLVM's crc32 feature with SSE4.2, but Rust says it's just SSE4.2 | ||
assert!(cfg!(target_feature = "sse4.2")); | ||
assert!(cfg!(not(target_feature = "crc32"))); | ||
} |