aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Writer/BitcodeWriterPass.cpp
diff options
context:
space:
mode:
authoralx32 <103613512+alx32@users.noreply.github.com>2024-11-26 16:07:40 -0800
committerGitHub <noreply@github.com>2024-11-26 16:07:40 -0800
commit5147e5941d40ae89b6ecab89aa36f8f5def28f1e (patch)
tree7d1f1aa9c5b51550a6cf2a8a86651d62115f59d5 /llvm/lib/Bitcode/Writer/BitcodeWriterPass.cpp
parent06514c550105b3111c23751421265c318bd69ac6 (diff)
downloadllvm-5147e5941d40ae89b6ecab89aa36f8f5def28f1e.zip
llvm-5147e5941d40ae89b6ecab89aa36f8f5def28f1e.tar.gz
llvm-5147e5941d40ae89b6ecab89aa36f8f5def28f1e.tar.bz2
[GSYM] Callsites: Add data format support and loading from YAML (#109781)
This PR adds support in the gSYM format for call site information and adds support for loading call sites from a YAML file. The support for YAML input is mostly for testing purposes - so we have a way to test the functionality. Note that this data is not currently used in the gSYM tooling - the logic to use call sites will be added in a later PR. The reason why we need call site information in gSYM files is so that we can support better call stack function disambiguation in the case where multiple functions have been merged due to optimization (linker ICF). When resolving a merged function on the callstack, we can use the call site information of the calling function to narrow down the actual function that is being called, from the set of all merged functions. See [this RFC](https://discourse.llvm.org/t/rfc-extending-gsym-format-with-call-site-information-for-merged-function-disambiguation/80682) for more details on this change.
Diffstat (limited to 'llvm/lib/Bitcode/Writer/BitcodeWriterPass.cpp')
0 files changed, 0 insertions, 0 deletions