summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test
diff options
context:
space:
mode:
authorArtur Pilipenko <apilipenko@azulsystems.com>2019-08-28 21:27:50 +0000
committerArtur Pilipenko <apilipenko@azulsystems.com>2019-08-28 21:27:50 +0000
commit925afc1ce70ab4117073d52bf519ea7cf05ed03f (patch)
tree5348ad743af4bfb73cf552a001eb3c13dcdabcd1 /lldb/packages/Python/lldbsuite/test
parent5970076466cf9722b7b5bd08f50e6479c352baf3 (diff)
downloadbcm5719-llvm-925afc1ce70ab4117073d52bf519ea7cf05ed03f.tar.gz
bcm5719-llvm-925afc1ce70ab4117073d52bf519ea7cf05ed03f.zip
Fix for "DICompileUnit not listed in llvm.dbg.cu" verification error after ...
...cloning a function from a different module Currently when a function with debug info is cloned from a different module, the cloned function may have hanging DICompileUnits, so that the module with the cloned function fails debug info verification. The proposed fix inserts all DICompileUnits reachable from the cloned function to "llvm.dbg.cu" metadata operands of the cloned function module. Reviewed By: aprantl, efriedma Differential Revision: https://reviews.llvm.org/D66510 Patch by Oleg Pliss (Oleg.Pliss@azul.com) llvm-svn: 370265
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud