[all-commits] [llvm/llvm-project] 266877: [llvm-objdump] Print method name from debug info i...

[Jordan Rupprecht via All-commits]

  Branch: refs/heads/master
  Home:   https://github.com/llvm/llvm-project
  Commit: 266877a2a8b2d1939f3b08fcfb711890fefc96e3
      https://github.com/llvm/llvm-project/commit/266877a2a8b2d1939f3b08fcfb711890fefc96e3
  Author: Jordan Rupprecht <rupprecht at google.com>
  Date:   2020-02-21 (Fri, 21 Feb 2020)

  Changed paths:
    M llvm/test/tools/llvm-objdump/AMDGPU/source-lines.ll
    M llvm/test/tools/llvm-objdump/Hexagon/source-interleave-hexagon.ll
    A llvm/test/tools/llvm-objdump/X86/source-interleave-function-from-debug.test
    M llvm/test/tools/llvm-objdump/X86/source-interleave-x86_64.test
    M llvm/test/tools/llvm-objdump/embedded-source.test
    M llvm/tools/llvm-objdump/llvm-objdump.cpp

  Log Message:
  -----------
  [llvm-objdump] Print method name from debug info in disassembly output.

Summary:
GNU objdump prints the method name in disassembly output, and upon further investigation this seems to come from debug info, not the symbol table.

Some additional refactoring is necessary to make this work even when the line number is 0/the filename is unknown. The added test case includes a note for this scenario.

See http://llvm.org/PR41341 for more info.

Reviewers: dblaikie, MaskRay, jhenderson

Reviewed By: MaskRay

Subscribers: ormris, jvesely, aprantl, kerbowa, llvm-commits

Tags: #llvm

Differential Revision: https://reviews.llvm.org/D74507