Lines Matching full:warning

257 NOTE: When requesting help with an objtool warning, please recreate with
259 output, including any disassembly or backtrace below the warning, to the
276 1. file.o: warning: objtool: func()+0x128: call without frame pointer save/setup
301 …arch/x86/kvm/kvm.o: warning: objtool: .altinstr_replacement+0xc5: call without frame pointer save/…
302    arch/x86/kvm/kvm.o: warning: objtool:   em_loop.part.0+0x29: (alt)
303    arch/x86/kvm/kvm.o: warning: objtool:   em_loop.part.0+0x0: <=== (sym)
318 2. file.o: warning: objtool: .text+0x53: unreachable instruction
333 3. file.o: warning: objtool: foo+0x48c: bar() missing __noreturn in .c/.h or NORETURN() in noreturn…
341 4. file.o: warning: objtool: func(): can't find starting instruction
343    file.o: warning: objtool: func()+0x11dd: can't decode instruction
350 5. file.o: warning: objtool: func()+0x6: unsupported instruction in callable function
358 6. file.o: warning: objtool: func()+0x26: sibling call from callable instruction with modified stac…
371 7. file: warning: objtool: func()+0x5c: stack state mismatch
388 8. file.o: warning: objtool: funcA() falls through to next function funcB()
406 9. file.o: warning: objtool: funcA() call to funcB() with UACCESS enabled
416    The intention of the warning is to prevent calls to funcB() from eventually
432 10. file.o: warning: func()+0x5c: stack layout conflict in alternatives
443 11. file.o: warning: unannotated intra-function call
445     This warning means that a direct call is done to a destination which
447     can remove this warning by putting the ANNOTATE_INTRA_FUNCTION_CALL
451 12. file.o: warning: func(): not an indirect call target