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)
commitae13f23de63ce045bd11c34d667c76d7ce4636f2
treea23b8d4e0f91acc0acfd18c2535ca475598a8fa7
parentab0d042a74f2e454a516be7a956b091f0ae7e1af
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.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@209547 91177308-0d34-0410-b5e6-96231b3b80d8
lib/CodeGen/AsmPrinter/DwarfDebug.cpp
test/DebugInfo/namespace_inline_function_definition.ll [new file with mode: 0644]