[all-commits] [llvm/llvm-project] dab971: [llvm-readobj] Dump SFrame relocations as well (#1...

Pavel Labath via All-commits all-commits at lists.llvm.org
Fri Aug 15 03:31:03 PDT 2025


  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: dab971ed23064c915941b463d4ffaf2356418726
      https://github.com/llvm/llvm-project/commit/dab971ed23064c915941b463d4ffaf2356418726
  Author: Pavel Labath <pavel at labath.sk>
  Date:   2025-08-15 (Fri, 15 Aug 2025)

  Changed paths:
    M llvm/include/llvm/Object/SFrameParser.h
    M llvm/lib/Object/SFrameParser.cpp
    A llvm/test/tools/llvm-readobj/ELF/sframe-reloc.test
    M llvm/tools/llvm-readobj/ELFDumper.cpp

  Log Message:
  -----------
  [llvm-readobj] Dump SFrame relocations as well (#153161)

If there is a relocation for a particular FDE, print it as well. This is
mainly meant for human consumption (otherwise, there's no way to tell
which function a given (relocatable) FDE refers to). For testing of
relocation generation, I'd still recommend using the regular relocation
dumper, as this code will not detect (e.g.) any superfluous relocations.

I've considered handling relocations inside the SFrameParser class, but
I couldn't find an elegant way to do that. Right now, I don't have a use
case for resolving relocations there as lldb (my other use case for
SFrameParser) will always operate on linked objects.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications


More information about the All-commits mailing list