summaryrefslogtreecommitdiffstats
path: root/scripts/Makefile.lib
diff options
context:
space:
mode:
authorPeter Zijlstra <peterz@infradead.org>2022-10-28 15:50:42 +0200
committerPeter Zijlstra <peterz@infradead.org>2022-11-01 13:44:09 +0100
commit9f2899fe36a623885d8576604cb582328ad32b3c (patch)
tree2287e0ce43e4c90c254c565f5c63849d365cd614 /scripts/Makefile.lib
parentobjtool: Avoid O(bloody terrible) behaviour -- an ode to libelf (diff)
downloadlinux-9f2899fe36a623885d8576604cb582328ad32b3c.tar.xz
linux-9f2899fe36a623885d8576604cb582328ad32b3c.zip
objtool: Add option to generate prefix symbols
When code is compiled with: -fpatchable-function-entry=${PADDING_BYTES},${PADDING_BYTES} functions will have PADDING_BYTES of NOP in front of them. Unwinders and other things that symbolize code locations will typically attribute these bytes to the preceding function. Given that these bytes nominally belong to the following symbol this mis-attribution is confusing. Inspired by the fact that CFI_CLANG emits __cfi_##name symbols to claim these bytes, allow objtool to emit __pfx_##name symbols to do the same. Therefore add the objtool --prefix=N argument, to conditionally place a __pfx_##name symbol at N bytes ahead of symbol 'name' when: all these preceding bytes are NOP and name-N is an instruction boundary. Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Tested-by: Yujie Liu <yujie.liu@intel.com> Link: https://lkml.kernel.org/r/20221028194453.526899822@infradead.org
Diffstat (limited to 'scripts/Makefile.lib')
0 files changed, 0 insertions, 0 deletions