[PATCH] D105917: [llvm-objdump][CallGraphSection] Extract call graph information from binary

[Matt Morehouse via Phabricator via llvm-commits]

morehouse added a comment.

In D105917#2912614 <https://reviews.llvm.org/D105917#2912614>, @jhenderson wrote:

> If I get time, I will look at the patch series next week. Before you go ahead with landing anything though, I think you need to demonstrate that this feature is both useful and desired by the community: this is quite a large amount of code, and on my first glance, neither RFC attracted any feedback, which may suggest people aren't interested in this functionality.

We expect this feature to be useful for sanitizers, especially hardware-supported memory tagging, as it allows us to compress allocation/deallocation stack traces and reconstruct them offline.  This will reduce memory overhead from stack traces by 16x and make production deployment feasible in more scenarios.  I'd argue that this alone makes the added complexity worthwhile.

I also imagine the call graph would be useful for guided fuzzing (e.g., funcA calls funcB, and we want coverage of funcB, so we mutate inputs that touch funcA).


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D105917/new/

https://reviews.llvm.org/D105917