[llvm-readobj] Display multiple function names for stack size entriesThe current implementation of displaying .stack_size informationpresumes that each entry represents a single function but this
[llvm-readobj] Display multiple function names for stack size entriesThe current implementation of displaying .stack_size informationpresumes that each entry represents a single function but this is notalways the case. For example with the use of ICF multiple functions canbe represented with the same code, meaning that the address found in a.stack_size entry corresponds to multiple function symbols.This change allows multiple function names to be displayed whenappropriate.Differential Revision: https://reviews.llvm.org/D105884
show more ...
BPF: fix relocation types in lib/Object/RelocationResolver.cppCommit 6a2ea84600ba ("BPF: Add more relocation kinds")added new relocations R_BPF_64_ABS64 and R_BPF_64_ABS32for normal 64-bit and 32
BPF: fix relocation types in lib/Object/RelocationResolver.cppCommit 6a2ea84600ba ("BPF: Add more relocation kinds")added new relocations R_BPF_64_ABS64 and R_BPF_64_ABS32for normal 64-bit and 32-bit data relocations.This is to replace some of functionalities withR_BPF_64_64 and R_BPF_64_32 so that new R_BPF_64_64and R_BPF_64_32 semantics are for ld_imm64 andcall instructions only.The BPF support in lib/Object/RelocationResolver.cppis used to perform normal data relocations forthe case like DWARFObjInMemory with an object file(search function getRelocationResolver() in fileDebugInfo/DWARF/DWARFContext.cpp) or llvm-readobjto dump ".stack_sizes" section data.In all these casees, normal 64-bit and 32-bit relocationsare performed and such resolution resolutionis exactly what implemented in RelocationResolver.cpp.But Commit 6a2ea84600ba missed to changeR_BPF_64_64/R_BPF_64_32 to R_BPF_64_ABS64/R_BPF_64_ABS32.This patch fixed the issue and added a test for itwith llvm-readobj dumping ".stack_sizes" section.Differential Revision: https://reviews.llvm.org/D103864