user0/rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Remove arm::t32-specific function pointer test.

Browse source 
All function pointers are currently treated as unaligned anyway;
any change implementing function pointer alignment during consteval should add
tests that it works properly on arm::t32 functions.
This commit is contained in:
Zachary S 2025-08-23 23:36:25 -05:00
parent 10fde9eafe
commit 25afbbc981
1 changed files with 3 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

22
tests/ui/consts/ptr_comparisons.rs
View file

@ -42,18 +42,6 @@ const ALIGNED_FN_PTR: *const () = {
unsafe { std::mem::transmute(aligned_foo as fn()) }
};
// Only on armv5te-* and armv4t-*
#[cfg(all(
target_arch = "arm",
not(target_feature = "v6"),
))]
const ALIGNED_THUMB_FN_PTR: *const () = {
#[rustc_align(2)]
#[instruction_set(arm::t32)]
fn aligned_thumb_foo() {}
unsafe { std::mem::transmute(aligned_thumb_foo as fn()) }
};
trait Trait {
#[allow(unused)]
fn method(&self) -> u8;
@ -204,14 +192,10 @@ do_test!(VTABLE_PTR_1, VTABLE_PTR_2, None);
// due to platform-specific semantics.
// See https://github.com/rust-lang/rust/issues/144661
// FIXME: This could return `Some` on platforms where function pointers' addresses actually
// correspond to function addresses including alignment, or on ARM if t32 function pointers
// have their low bit set for consteval.
// correspond to function addresses including alignment, or on platforms where all functions
// are aligned to some amount (e.g. ARM where a32 function pointers are at least 4-aligned,
// and t32 function pointers are 2-aligned-offset-by-1).
do_test!(ALIGNED_FN_PTR, ALIGNED_FN_PTR.wrapping_byte_offset(1), None);
#[cfg(all(
target_arch = "arm",
not(target_feature = "v6"),
))]
do_test!(ALIGNED_THUMB_FN_PTR, ALIGNED_THUMB_FN_PTR.wrapping_byte_offset(1), None);
// Conservatively say we don't know.
do_test!(FN_PTR, VTABLE_PTR_1, None);