llvm-6502/test/Bitcode/DICompileUnit-no-DWOId.ll

; The input uses the older (r236428) form without a dwoId field.  This should
; default to 0, which is not displayed at all in the textual representation.
;
; RUN: llvm-dis %s.bc -o - | FileCheck %s
; CHECK: !DICompileUnit
; CHECK-NOT: dwoId:
!named = !{!0}
!0 = !DICompileUnit(language: 12, file: !1)
!1 = !DIFile(filename: "path/to/file", directory: "/path/to/dir")
IR / debug info: Add a DWOId field to DICompileUnit, so DWARF skeleton CUs can be expression in IR. A skeleton CU is a (typically empty) DW_TAG_compile_unit that has a DW_AT_(GNU)_dwo_name and a DW_AT_(GNU)_dwo_id attribute. It is used to refer to external debug info. This is a prerequisite for clang module debugging as discussed in http://lists.cs.uiuc.edu/pipermail/cfe-dev/2014-November/040076.html. In order to refer to external types stored in split DWARF (dwo) objects, such as clang modules, we need to emit skeleton CUs, which identify the dwarf object (i.e., the clang module) by filename (the SplitDebugFilename) and a hash value, the dwo_id. This patch only contains the IR changes. The idea is that a CUs with a non-zero dwo_id field will be emitted together with a DW_AT_GNU_dwo_name and DW_AT_GNU_dwo_id attribute. http://reviews.llvm.org/D9488 rdar://problem/20091852 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@237949 91177308-0d34-0410-b5e6-96231b3b80d8 2015-05-21 20:37:30 +00:00			`; The input uses the older (r236428) form without a dwoId field. This should`
			`; default to 0, which is not displayed at all in the textual representation.`
			`;`
			`; RUN: llvm-dis %s.bc -o - \| FileCheck %s`
			`; CHECK: !DICompileUnit`
			`; CHECK-NOT: dwoId:`
			`!named = !{!0}`
			`!0 = !DICompileUnit(language: 12, file: !1)`
			`!1 = !DIFile(filename: "path/to/file", directory: "/path/to/dir")`