Lines Matching refs:objtool

9 objtool which runs at compile time.  It has a "check" subcommand which
88    The benefit of objtool here is that because it ensures that *all*
119 To achieve the validation, objtool enforces the following rules:
123    ENTRY/ENDPROC macros.  If objtool finds a return instruction
127    This rule is needed so that objtool can properly identify each
134    This rule is needed so that objtool can ignore non-callable code.
154    This rule is needed so that objtool can reliably analyze all of a
156    and it's not a sibling call, objtool has no way to follow the jump
179 Here are some examples of common warnings reported by objtool, what
183 1. file.o: warning: objtool: func()+0x128: call without frame pointer save/setup
205 2. file.o: warning: objtool: .text+0x53: unreachable instruction
213    macros in asm/unwind_hints.h so objtool and the unwinder can know the
217    a just a bad person, you can tell objtool to ignore it.  See the
224 4. file.o: warning: objtool: func(): can't find starting instruction
226    file.o: warning: objtool: func()+0x11dd: can't decode instruction
229    objtool's instruction decoder.  Move the data to a more appropriate
233 5. file.o: warning: objtool: func()+0x6: unsupported instruction in callable function
242 6. file.o: warning: objtool: func()+0x26: sibling call from callable instruction with modified stac…
256 7. file: warning: objtool: func()+0x5c: stack state mismatch
273 8. file.o: warning: objtool: funcA() falls through to next function funcB()
276    unconditional jump, and that objtool has determined that the function
282       objtool's hard-coded global_noreturns array.  Feel free to bug the
283       objtool maintainer, or you can submit a patch.
292 9. file.o: warning: objtool: funcA() call to funcB() with UACCESS enabled
313    3) add funcB to uaccess_safe_builtin whitelist in tools/objtool/check.c, if
336 If the error doesn't seem to make sense, it could be a bug in objtool.
337 Feel free to ask the objtool maintainer for help.
343 If you _really_ need objtool to ignore something, and are 100% sure
344 that it won't affect kernel stack traces, you can tell objtool to