Lines Matching refs:pointer
22 alternative to frame pointer based unwinding
103 validates the correct frame pointer state at each instruction.
113 a) More reliable stack traces for frame pointer enabled kernels
125 frame pointers when the -fno-omit-frame-pointer option is used.
133 and update the frame pointer. If a first function doesn't properly
152 If we remove the frame pointer logic from cmdline_proc_show() by
153 replacing the frame pointer related instructions with nops, here's
215 correct frame pointer logic, if required by CONFIG_FRAME_POINTER or
219 This rule ensures that frame pointer based stack traces will work as
228 b) the jump matches sibling call semantics and the frame pointer has
259 -fno-omit-frame-pointer or adds -fomit-frame-pointer to the gcc options.
266 1. file.o: warning: objtool: func()+0x128: call without frame pointer save/setup
269 updating the frame pointer, and CONFIG_FRAME_POINTER is enabled.
272 function, add proper frame pointer logic using the FRAME_BEGIN and
280 stack pointer in its output operand. On x86_64, this means adding
291 …arch/x86/kvm/kvm.o: warning: objtool: .altinstr_replacement+0xc5: call without frame pointer save/…
352 assumed it's a sibling call and detected that the frame pointer
365 The instruction's frame pointer state is inconsistent, depending on
369 pushes and sets up the frame pointer (for x86_64, this means rbp) at
372 pointer.
375 does some unusual things to the stack or the frame pointer. In such