The dwarf standard says that the only differences between a out-of-line
authorRafael Espindola <rafael.espindola@gmail.com>
Sat, 12 Nov 2011 01:57:54 +0000 (01:57 +0000)
committerRafael Espindola <rafael.espindola@gmail.com>
Sat, 12 Nov 2011 01:57:54 +0000 (01:57 +0000)
commitd1ac3a47f2c2993e8bbda0a9f1c843e9efd0f00f
tree38d3ed5a2a3cfd87239ce9ed11eb857cacea15a6
parent9588c10b69121d9746b09e868fcc8879cbd98e3a
The dwarf standard says that the only differences between a out-of-line
instance and a concrete inlined instance are the use of DW_TAG_subprogram
instead of DW_TAG_inlined_subroutine and the who owns the tree.

We were also omitting DW_AT_inline from the abstract roots. To fix this,
make sure we mark abstract instance roots with DW_AT_inline even when
we have only out-of-line instances referring to them with DW_AT_abstract_origin.

FileCheck is not a very good tool for tests like this, maybe we should add
a -verify mode to llvm-dwarfdump.

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