Jubilee Young 0c157b51d3 aarch64-linux: Default to FramePointer::NonLeaf ... For aarch64-apple and aarch64-windows, platform docs state that code must use frame pointers correctly. This is because the AAPCS64 mandates that a platform specify its frame pointer conformance requirements: - Apple: https://developer.apple.com/documentation/xcode/writing-arm64-code-for-apple-platforms#Respect-the-purpose-of-specific-CPU-registers - Windows: https://learn.microsoft.com/en-us/cpp/build/arm64-windows-abi-conventions?view=msvc-170#integer-registers - AAPCS64: 4492d1570e/aapcs64/aapcs64.rst (the-frame-pointer) Unwinding code either requires unwind tables or frame pointers, and on aarch64 the expectation is that one can use frame pointers for this. Most Linux targets represent a motley variety of possible distributions, so it is unclear who to defer to on conformance, other than perhaps Arm. In the absence of a specific edict for a given aarch64-linux target, Rust will assume aarch64-linux targets use non-leaf frame pointers. This reflects what compilers like clang do.		2025-05-17 06:42:46 +02:00
..
aarch64-el2vmsa.rs
aarch64-modifiers.rs
aarch64-outline-atomics.rs
aarch64-types.rs	aarch64-linux: Default to FramePointer::NonLeaf	2025-05-17 06:42:46 +02:00
arm-modifiers.rs
arm-types.rs
avr-modifiers.rs
avr-types.rs
bpf-types.rs
comments.rs
global_asm.rs
hexagon-types.rs
inline-asm-avx.rs
loongarch-type.rs
m68k-types.rs
mips-types.rs
msp430-types.rs
nvptx-types.rs
powerpc-types.rs
riscv-types.rs
s390x-types.rs
sparc-types.rs
wasm-types.rs
x86-modifiers.rs
x86-types.rs