rust/tests/codegen/force-frame-pointers.rs

//@ compile-flags: -C no-prepopulate-passes -C force-frame-pointers=y -Copt-level=0

#![crate_type="lib"]

// CHECK: attributes #{{.*}} "frame-pointer"="all"
pub fn foo() {}
Automatically enable cross-crate inlining for small functions 2023-10-06 20:29:42 -04:00			`//@ compile-flags: -C no-prepopulate-passes -C force-frame-pointers=y -Copt-level=0`
Don't force-enable frame pointers when generating debug info We apparently used to generate bad/incomplete debug info causing debuggers not to find symbols of stack allocated variables. This was somehow worked around by having frame pointers. With the current codegen, this seems no longer necessary, so we can remove the code that force-enables frame pointers whenever debug info is requested. Since certain situations, like profiling code profit from having frame pointers, we add a -Cforce-frame-pointers flag to always enable frame pointers. Fixes #11906 2018-01-03 10:29:27 +01:00
			`#![crate_type="lib"]`

Use function attribute "frame-pointer" instead of "no-frame-pointer-elim" LLVM 8 (D56351) introduced "frame-pointer". In LLVM 10 (D71863), "no-frame-pointer-elim"/"no-frame-pointer-elim-non-leaf" will be ignored. 2019-12-30 21:35:13 -08:00			`// CHECK: attributes #{{.*}} "frame-pointer"="all"`
Don't force-enable frame pointers when generating debug info We apparently used to generate bad/incomplete debug info causing debuggers not to find symbols of stack allocated variables. This was somehow worked around by having frame pointers. With the current codegen, this seems no longer necessary, so we can remove the code that force-enables frame pointers whenever debug info is requested. Since certain situations, like profiling code profit from having frame pointers, we add a -Cforce-frame-pointers flag to always enable frame pointers. Fixes #11906 2018-01-03 10:29:27 +01:00			`pub fn foo() {}`