summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/signals
diff options
context:
space:
mode:
authorTeresa Johnson <tejohnson@google.com>2015-11-03 15:11:27 +0000
committerTeresa Johnson <tejohnson@google.com>2015-11-03 15:11:27 +0000
commit07b825b01cdf6af0facb10744d48c78d07cca375 (patch)
treee4ede8c36f0eb3845b2578975a1dd743c387879f /lldb/packages/Python/lldbsuite/test/python_api/signals
parent04e5877430a33022ebd23187efc65c6fdf100fe7 (diff)
downloadbcm5719-llvm-07b825b01cdf6af0facb10744d48c78d07cca375.tar.gz
bcm5719-llvm-07b825b01cdf6af0facb10744d48c78d07cca375.zip
Move metadata linking after lazy global materialization/linking.
Summary: Currently, named metadata is linked before the LazilyLinkGlobalValues list is walked and materialized/linked. As a result, references from DISubprogram and DIGlobalVariable metadata to yet unmaterialized functions and variables cause them to be added to the lazy linking list and their definitions are materialized and linked. This makes the llvm-link -only-needed option not have the intended effect when debug information is present, as the otherwise unneeded functions/variables are still linked in. Additionally, for ThinLTO I have implemented a mechanism to only link in debug metadata needed by imported functions. Moving named metadata linking after lazy GV linking will facilitate applying this mechanism to the LTO and "llvm-link -only-needed" cases as well. Reviewers: dexonsmith, tra, dblaikie Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D14195 llvm-svn: 251926
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/signals')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud