Lines Matching refs:frame

14 Currently it only checks frame pointer usage, but there are plans to add
18 validates the correct frame pointer state at each instruction.
32 a) More reliable stack traces for frame pointer enabled kernels
39    For some architectures, frame pointers are enabled by
44    frame pointers when the -fno-omit-frame-pointer option is used.
46    But for asm code, the frame setup instructions have to be written by
50    For stack traces based on frame pointers to be reliable, all
51    functions which call other functions must first create a stack frame
52    and update the frame pointer.  If a first function doesn't properly
53    create a stack frame before calling a second function, the *caller*
56    For example, consider the following example backtrace with frame
71    If we remove the frame pointer logic from cmdline_proc_show() by
72    replacing the frame pointer related instructions with nops, here's
92        beginning of a function before the stack frame has been created,
93        or at the very end of the function after the stack frame has been
94        destroyed.  This is an inherent limitation of frame pointers.
100    As an alternative to frame pointers, DWARF Call Frame Information
101    (CFI) metadata can be used to walk the stack.  Unlike frame pointers,
175    correct frame pointer logic, if required by CONFIG_FRAME_POINTER or
179    This rule ensures that frame pointer based stack traces will work as
180    designed.  If function A doesn't create a stack frame before calling
188    b) the jump matches sibling call semantics and the frame pointer has
215 1. asm_file.o: warning: objtool: func()+0x128: call without frame pointer save/setup
218    updating the frame pointer.
220    If func() is indeed a callable function, add proper frame pointer
275 …o: warning: objtool: func()+0x26: sibling call from callable instruction with changed frame pointer
278    assumed it's a sibling call and detected that the frame pointer
288 7. asm_file: warning: objtool: func()+0x5c: frame pointer state mismatch
290    The instruction's frame pointer state is inconsistent, depending on
293    Make sure the function pushes and sets up the frame pointer (for
296    function touches the frame pointer.
329    Otherwise the stack frame may not get created before the call.
332    -fno-omit-frame-pointer or adds -fomit-frame-pointer to the gcc options.