Matthias Krüger d6a61daf60 Rollup merge of #140832 - workingjubilee:aarch64-linux-should-use-frame-pointers, r=compiler-errors ... 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 also use non-leaf frame pointers. This reflects what compilers like clang do.		2025-05-23 20:30:09 +02:00
..
asm	Rename is_like_osx to is_like_darwin	2025-03-25 21:53:52 +01:00
callconv	Rollup merge of #135808 - tiif:conv_display, r=workingjubilee	2025-05-17 15:45:19 +02:00
spec	Rollup merge of #140832 - workingjubilee:aarch64-linux-should-use-frame-pointers, r=compiler-errors	2025-05-23 20:30:09 +02:00
json.rs	compiler: internally merge Conv::PtxKernel into GpuKernel	2025-02-09 23:14:55 -08:00
lib.rs	update cfg(bootstrap)	2025-05-12 15:33:37 +02:00
target_features.rs	aarch64-softfloat: forbid enabling the neon target feature	2025-05-22 12:19:25 +02:00
tests.rs	Use serde_json for target spec json	2022-06-03 16:46:19 +00:00