Lines Matching refs:code
41 ("noinstr") code rules, preventing instrumentation in low-level C
42 entry code
112 code and C inline assembly code so that stack traces can be reliable.
114 For each function, it recursively follows all possible code paths and
117 It also follows code paths involving special sections, like
128 code and debug tools to be able to walk the stack to determine the
130 code.
136 For C code, gcc automatically generates instructions for setting up
139 But for asm code, the frame setup instructions have to be written by
141 CONFIG_FRAME_POINTER is honored for C code but not for most asm code.
211 function type. In asm code, this is typically done using the
214 callable code which should be annotated accordingly.
219 2. Conversely, each section of code which is *not* callable, or is
226 the architecture's back chain rules. This can by done in asm code
242 function's code paths. If a function jumps to code in another file,
247 The only code which needs such instructions is kernel entry code,
263 first make sure that the affected code follows the above rules.
268 Another possible cause for errors in C code is if the Makefile removes
320 Objtool couldn't find a code path to reach the instruction.
326 Otherwise, SYM_CODE_START can be used. In that case the code needs
329 If you're sure the code won't affect the reliability of runtime stack
354 likely part of the kernel entry code. Such code should probably be
365 and/or move the destination code to the local file.
368 kernel entry code), use SYM_CODE_{START,END} and unwind hints.
379 Also make sure that no other code in the function touches the frame
382 Another possibility is that the code has some asm or inline asm which
400 b) funcA() uses the unreachable() annotation in a section of code
435 macro, the code paths have conflicting modifications to the stack.
438 instruction boundaries regardless of which code has been patched.