Home
last modified time | relevance | path

Searched refs:objtool (Results 1 – 25 of 33) sorted by relevance

12

/OK3568_Linux_fs/kernel/tools/objtool/
H A DBuild1 objtool-y += arch/$(SRCARCH)/
3 objtool-y += weak.o
5 objtool-$(SUBCMD_CHECK) += check.o
6 objtool-$(SUBCMD_CHECK) += special.o
7 objtool-$(SUBCMD_ORC) += check.o
8 objtool-$(SUBCMD_ORC) += orc_gen.o
9 objtool-$(SUBCMD_ORC) += orc_dump.o
11 objtool-y += builtin-check.o
12 objtool-y += builtin-orc.o
13 objtool-y += elf.o
[all …]
H A DMakefile19 OBJTOOL := $(OUTPUT)objtool
30 -I$(srctree)/tools/objtool/arch/$(SRCARCH)/include
55 @$(MAKE) $(build)=objtool
65 $(call QUIET_CLEAN, objtool) $(RM) $(OBJTOOL)
H A D.gitignore3 objtool
H A Dsync-check.sh54 if [ ! -d ../../kernel ] || [ ! -d ../../tools ] || [ ! -d ../objtool ]; then
/OK3568_Linux_fs/kernel/tools/objtool/Documentation/
H A Dstack-validation.txt9 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
[all …]
/OK3568_Linux_fs/kernel/Documentation/x86/
H A Dorc-unwinder.rst15 The ORC data consists of unwind tables which are generated by objtool.
93 The ORC data is generated by objtool. With the existing compile-time
94 stack metadata validation feature, objtool already follows all code
117 So the advantages of using objtool to generate ORC data are that it
123 The downside is that the unwinder now becomes dependent on objtool's
125 too complicated for objtool to follow, the ORC data generation might
127 already has such a dependency on objtool's ability to follow GCC code
131 objtool, we may need to revisit the current implementation. Some
133 palatable, or having objtool use DWARF as an additional input, or
134 creating a GCC plugin to assist objtool with its analysis. But for now,
[all …]
/OK3568_Linux_fs/kernel/tools/objtool/arch/x86/
H A DBuild1 objtool-y += special.o
2 objtool-y += decode.o
/OK3568_Linux_fs/device/rockchip/common/scripts/
H A Dmk-kbuild.sh95 make_subdir tools/objtool
97 make_subdir tools/objtool install
/OK3568_Linux_fs/device/rockchip/common/linux-kbuild/
H A Dmk-kbuild.sh95 make_subdir tools/objtool
97 make_subdir tools/objtool install
/OK3568_Linux_fs/device/rockchip/common/linux-kbuild/aarch64/linux-kbuild-5.10/scripts/
H A DMakefile.modfinal46 $(objtree)/tools/objtool/objtool $(objtool_args) \
H A DMakefile.build224 __objtool_obj := $(objtree)/tools/objtool/objtool
258 $(call cmd,objtool)
266 $(call cmd,objtool)
/OK3568_Linux_fs/device/rockchip/common/linux-kbuild/armhf/linux-kbuild-5.10/scripts/
H A DMakefile.modfinal46 $(objtree)/tools/objtool/objtool $(objtool_args) \
H A DMakefile.build224 __objtool_obj := $(objtree)/tools/objtool/objtool
258 $(call cmd,objtool)
266 $(call cmd,objtool)
/OK3568_Linux_fs/kernel/scripts/
H A DMakefile.modfinal46 $(objtree)/tools/objtool/objtool $(objtool_args) \
H A DMakefile.build224 __objtool_obj := $(objtree)/tools/objtool/objtool
258 $(call cmd,objtool)
266 $(call cmd,objtool)
H A Dlink-vmlinux.sh151 tools/objtool/objtool ${objtoolcmd} ${objtoolopt} ${1}
/OK3568_Linux_fs/kernel/tools/
H A DMakefile67 cgroup firewire hv guest bootconfig spi usb virtio vm bpf iio gpio objtool leds wmi pci firmware de… target
105 tmon freefall iio objtool kvm_stat wmi \
/OK3568_Linux_fs/kernel/
H A Dbuild.config.x86_6410 prepare-objtool
H A DMakefile1171 objtool_target := tools/objtool FORCE
1345 prepare: prepare0 prepare-objtool prepare-resolve_btfids
1358 PHONY += prepare-objtool prepare-resolve_btfids
1359 prepare-objtool: $(objtool_target)
/OK3568_Linux_fs/device/rockchip/common/linux-kbuild/aarch64/linux-kbuild-4.19/scripts/
H A DMakefile.build268 __objtool_obj := $(objtree)/tools/objtool/objtool
313 $(call echo-cmd,objtool) $(cmd_objtool) \
320 $(call echo-cmd,objtool) $(cmd_objtool) \
/OK3568_Linux_fs/device/rockchip/common/linux-kbuild/armhf/linux-kbuild-4.19/scripts/
H A DMakefile.build268 __objtool_obj := $(objtree)/tools/objtool/objtool
313 $(call echo-cmd,objtool) $(cmd_objtool) \
320 $(call echo-cmd,objtool) $(cmd_objtool) \
/OK3568_Linux_fs/kernel/Documentation/
H A Dasm-annotations.rst43 information. In particular, on properly annotated objects, ``objtool`` can be
44 run to check and fix the object if needed. Currently, ``objtool`` can report
82 Checking tools like ``objtool`` should ensure such marked functions conform
103 ``objtool`` requires that all code must be contained in an ELF symbol. Symbol
/OK3568_Linux_fs/kernel/scripts/package/
H A Dbuilddeb71 echo tools/objtool/objtool
/OK3568_Linux_fs/yocto/poky/meta/recipes-kernel/linux/
H A Dkernel-devsrc.bb146 # if our build dir had objtool, it will also be rebuilt on target, so
148 if [ -f ${B}/tools/objtool/objtool ]; then
149 # these are a few files associated with objtool, since we'll need to
157 cp -a --parents tools/objtool/* $kerneldir/build/
265 # objtool requires these files
/OK3568_Linux_fs/yocto/poky/meta/classes/
H A Dkernel.bbclass586 # With CONFIG_UNWINDER_ORC (the default in 4.14), objtool is required for
588 if [ -x tools/objtool/objtool ]; then
589 mkdir -p ${kerneldir}/tools/objtool
590 cp tools/objtool/objtool ${kerneldir}/tools/objtool/

12