Lines Matching refs:it

14 For each function, it recursively follows all possible code paths and
20 instructions).  Similarly, it knows how to follow switch statements, for
74    what it looks like instead:
88    The benefit of objtool here is that because it ensures that *all*
101    band.  So it doesn't affect runtime performance and it can be
124    outside of a function, it flags an error since that usually indicates
152       the same value it had on function entry.
156    and it's not a sibling call, objtool has no way to follow the jump
157    because it only analyzes a single file at a time.
190    FRAME_END macros.  Otherwise, if it's not a callable function, remove
194    If it's a GCC-compiled .c file, the error may be because the function
217    a just a bad person, you can tell objtool to ignore it.  See the
220    If it's not actually in a callable function (e.g. kernel entry code),
245    assumed it's a sibling call and detected that the frame pointer
248    If it's not really a sibling call, you may need to move the
263    the beginning of the function and pops it at the end of the function.
269    cases it's probably appropriate to use the unwind hint macros in
336 If the error doesn't seem to make sense, it could be a bug in objtool.
344 that it won't affect kernel stack traces, you can tell objtool to
345 ignore it: