David Blaikie 5f3c0bafeb 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. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@219249 91177308-0d34-0410-b5e6-96231b3b80d8		2014-10-07 22:59:46 +00:00
..
AddressSanitizer	[asan-asm-instrumentation] CFI directives are generated for .S files.	2014-10-07 11:03:09 +00:00
BoundsChecking	Allow aliases to be unnamed_addr.	2014-06-06 01:20:28 +00:00
DataFlowSanitizer	DebugInfo+DFSan: Ensure that debug info references to llvm::Functions remain pointing to the underlying function when wrappers are created	2014-10-07 22:59:46 +00:00
MemorySanitizer	Revert "Revert "DI: Fold constant arguments into a single MDString""	2014-10-03 20:01:09 +00:00
ThreadSanitizer	[TSan] Fixup a test case after r209939	2014-05-31 00:26:03 +00:00