summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api
diff options
context:
space:
mode:
authorDavid Blaikie <dblaikie@gmail.com>2017-05-29 00:48:45 +0000
committerDavid Blaikie <dblaikie@gmail.com>2017-05-29 00:48:45 +0000
commitce0c205813c74b4225180ac8a6e40fd52ea88229 (patch)
tree28fff06a2349215fb760ae967fbed41d39755610 /lldb/packages/Python/lldbsuite/test/python_api
parent02f8a0768956d7f44fcbb1a154151eb1f4d7b060 (diff)
downloadbcm5719-llvm-ce0c205813c74b4225180ac8a6e40fd52ea88229.tar.gz
bcm5719-llvm-ce0c205813c74b4225180ac8a6e40fd52ea88229.zip
DebugInfo: Include .dwo file name when hashing multiple CUs in a single file
This is really a workaround for ThinLTO in particular - since it can import partial CUs that may end up looking very similar/the same as the same partial import in another ThinLTO compile. An alternative fix would be to change the DICompileUnit metadata to include a "primary file" or the like - and when importing for ThinLTO set the primary file to the name of the DICompileUnit that is being imported into. This involves changing the schema and would reduce the excessive uniqueness in the hash that this change creates - allowing diagnosing of more duplicate CUs than will be caught with this change. But duplicate CUs can still be caught in non-ThinLTO builds & are mostly a nuisance rather than a particularly deliberate/effective tool for finding broken code. (arguably the hash could always include the dwo file and nothing in fission would break, I think..) llvm-svn: 304119
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud