DebugInfo: Put concrete definitions referencing abstract definitions in the same...
authorDavid Blaikie <dblaikie@gmail.com>
Fri, 23 May 2014 20:25:15 +0000 (20:25 +0000)
committerDavid Blaikie <dblaikie@gmail.com>
Fri, 23 May 2014 20:25:15 +0000 (20:25 +0000)
commit169ffe41affece998de11f33b2ce0b8d191754b7
treebf9c524ad95e7ac6456efecf26cbc310cc5e62c7
parentbe4be16be3f358e08cba4676f057e46d51e08297
DebugInfo: Put concrete definitions referencing abstract definitions in the same scope as the abstract definition.

This seems like a simple cleanup/improved consistency, but also helps
lay the foundation to fix the bug mentioned in the test case: concrete
definitions preceeding any inlined usage aren't properly split into
concrete + abstract (because they're not known to need it until it's too
late).

Once we start deferring this choice until later, we won't have the
choice to put concrete definitions for inlined subroutines in a
different scope from concrete definitions for non-inlined subroutines
(since we won't know at time-of-construction which one it'll be). This
change brings those two cases into alignment ahead of that future
chaneg/fix.

llvm-svn: 209547
llvm/lib/CodeGen/AsmPrinter/DwarfDebug.cpp
llvm/test/DebugInfo/namespace_inline_function_definition.ll [new file with mode: 0644]