summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Object/MachOObjectFile.cpp
diff options
context:
space:
mode:
authorDiego Novillo <dnovillo@google.com>2014-03-18 12:03:12 +0000
committerDiego Novillo <dnovillo@google.com>2014-03-18 12:03:12 +0000
commit213bb0024564cbd0119452bd1c21b273857b9531 (patch)
tree039518fa85cf3aad1e8e9e433245d79861d09d3b /llvm/lib/Object/MachOObjectFile.cpp
parent9e5341d64ad32d3d4eec7c892a4f601039dd6c8f (diff)
downloadbcm5719-llvm-213bb0024564cbd0119452bd1c21b273857b9531.tar.gz
bcm5719-llvm-213bb0024564cbd0119452bd1c21b273857b9531.zip
Tolerate unmangled names in sample profiles.
Summary: The compiler does not always generate linkage names. If a function has been inlined and its body elided, its linkage name may not be generated. When the binary executes, the profiler will use its unmangled name when attributing samples. This results in unmangled names in the input profile. We are currently failing hard when this happens. However, in this case all that happens is that we fail to attribute samples to the inlined function. While this means fewer optimization opportunities, it should not cause a compilation failure. This patch accepts all valid function names, regardless of whether they were mangled or not. Reviewers: chandlerc CC: llvm-commits Differential Revision: http://llvm-reviews.chandlerc.com/D3087 llvm-svn: 204142
Diffstat (limited to 'llvm/lib/Object/MachOObjectFile.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud