diff options
| author | David Blaikie <dblaikie@gmail.com> | 2014-10-07 22:59:46 +0000 |
|---|---|---|
| committer | David Blaikie <dblaikie@gmail.com> | 2014-10-07 22:59:46 +0000 |
| commit | c6c6c7b177e2c42fb67bc5a215aa1f181a40ca5c (patch) | |
| tree | a5eabfa70745e0f3999df51de8bf72d513b6d2f4 /clang/lib/CodeGen/CodeGenModule.cpp | |
| parent | 95c39ce2f3ce692b542e798aaa66a9f9e675e0d8 (diff) | |
| download | llvm-c6c6c7b177e2c42fb67bc5a215aa1f181a40ca5c.zip llvm-c6c6c7b177e2c42fb67bc5a215aa1f181a40ca5c.tar.gz llvm-c6c6c7b177e2c42fb67bc5a215aa1f181a40ca5c.tar.bz2 | |
DebugInfo+DFSan: Ensure that debug info references to llvm::Functions remain pointing to the underlying function when wrappers are created
This is somewhat the inverse of how similar bugs in DAE and ArgPromo
manifested and were addressed. In those passes, individual call sites
were visited explicitly, and then the old function was deleted. This
left the debug info with a null llvm::Function* that needed to be
updated to point to the new function.
In the case of DFSan, it RAUWs the old function with the wrapper, which
includes debug info. So now the debug info refers to the wrapper, which
doesn't actually have any instructions with debug info in it, so it is
ignored entirely - resulting in a DW_TAG_subprogram with no high/low pc,
etc. Instead, fix up the debug info to refer to the original function
after the RAUW messed it up.
Reviewed/discussed with Peter Collingbourne on the llvm-dev mailing
list.
llvm-svn: 219249
Diffstat (limited to 'clang/lib/CodeGen/CodeGenModule.cpp')
0 files changed, 0 insertions, 0 deletions