2014-05-22 07:14:12 +08:00
|
|
|
; REQUIRES: object-emission
|
|
|
|
|
2014-07-16 05:06:37 +08:00
|
|
|
; RUN: %llc_dwarf -O0 -filetype=obj < %s | llvm-dwarfdump -debug-dump=info - | FileCheck -implicit-check-not=DW_TAG %s
|
2014-11-15 03:30:08 +08:00
|
|
|
; RUN: %llc_dwarf -dwarf-accel-tables=Enable -O0 -filetype=obj < %s | llvm-dwarfdump - | FileCheck --check-prefix=CHECK-ACCEL --check-prefix=CHECK %s
|
2014-05-22 07:14:12 +08:00
|
|
|
|
|
|
|
; Build from source:
|
|
|
|
; $ clang++ a.cpp b.cpp -g -c -emit-llvm
|
|
|
|
; $ llvm-link a.bc b.bc -o ab.bc
|
|
|
|
; $ opt -inline ab.bc -o ab-opt.bc
|
|
|
|
; $ cat a.cpp
|
|
|
|
; extern int i;
|
|
|
|
; int func(int);
|
|
|
|
; int main() {
|
|
|
|
; return func(i);
|
|
|
|
; }
|
|
|
|
; $ cat b.cpp
|
|
|
|
; int __attribute__((always_inline)) func(int x) {
|
|
|
|
; return x * 2;
|
|
|
|
; }
|
|
|
|
|
|
|
|
; Ensure that func inlined into main is described and references the abstract
|
|
|
|
; definition in b.cpp's CU.
|
|
|
|
|
|
|
|
; CHECK: DW_TAG_compile_unit
|
|
|
|
; CHECK: DW_AT_name {{.*}} "a.cpp"
|
|
|
|
; CHECK: DW_TAG_subprogram
|
DebugInfo: Lazily attach definition attributes to definitions.
This is a precursor to fixing inlined debug info where the concrete,
out-of-line definition may preceed any inlined usage. To cope with this,
the attributes that may appear on the concrete definition or the
abstract definition are delayed until the end of the module. Then, if an
abstract definition was created, it is referenced (and no other
attributes are added to the out-of-line definition), otherwise the
attributes are added directly to the out-of-line definition.
In a couple of cases this causes not just reordering of attributes, but
reordering of types. When the creation of the attribute is delayed, if
that creation would create a type (such as for a DW_AT_type attribute)
then other top level DIEs may've been constructed during the delay,
causing the referenced type to be created and added after those
intervening DIEs. In the extreme case, in cross-cu-inlining.ll, this
actually causes the DW_TAG_basic_type for "int" to move from one CU to
another.
llvm-svn: 209674
2014-05-28 02:37:43 +08:00
|
|
|
; CHECK: DW_AT_type [DW_FORM_ref_addr] (0x00000000[[INT:.*]])
|
2014-11-13 07:48:14 +08:00
|
|
|
; CHECK: 0x[[INLINED:[0-9a-f]*]]:{{.*}}DW_TAG_inlined_subroutine
|
2014-10-06 11:36:31 +08:00
|
|
|
; CHECK: DW_AT_abstract_origin {{.*}}[[ABS_FUNC:........]] "_Z4funci"
|
2014-05-22 07:14:12 +08:00
|
|
|
; CHECK: DW_TAG_formal_parameter
|
2014-10-10 23:51:02 +08:00
|
|
|
; CHECK: DW_AT_abstract_origin {{.*}}[[ABS_VAR:........]] "x"
|
2014-05-22 07:14:12 +08:00
|
|
|
|
|
|
|
; Check the abstract definition is in the 'b.cpp' CU and doesn't contain any
|
|
|
|
; concrete information (address range or variable location)
|
|
|
|
; CHECK: DW_TAG_compile_unit
|
|
|
|
; CHECK: DW_AT_name {{.*}} "b.cpp"
|
|
|
|
; CHECK: 0x[[ABS_FUNC]]: DW_TAG_subprogram
|
|
|
|
; CHECK-NOT: DW_AT_low_pc
|
|
|
|
; CHECK: 0x[[ABS_VAR]]: DW_TAG_formal_parameter
|
2014-05-23 12:23:06 +08:00
|
|
|
; CHECK-NOT: DW_AT_location
|
DebugInfo: Lazily attach definition attributes to definitions.
This is a precursor to fixing inlined debug info where the concrete,
out-of-line definition may preceed any inlined usage. To cope with this,
the attributes that may appear on the concrete definition or the
abstract definition are delayed until the end of the module. Then, if an
abstract definition was created, it is referenced (and no other
attributes are added to the out-of-line definition), otherwise the
attributes are added directly to the out-of-line definition.
In a couple of cases this causes not just reordering of attributes, but
reordering of types. When the creation of the attribute is delayed, if
that creation would create a type (such as for a DW_AT_type attribute)
then other top level DIEs may've been constructed during the delay,
causing the referenced type to be created and added after those
intervening DIEs. In the extreme case, in cross-cu-inlining.ll, this
actually causes the DW_TAG_basic_type for "int" to move from one CU to
another.
llvm-svn: 209674
2014-05-28 02:37:43 +08:00
|
|
|
; CHECK: DW_AT_type [DW_FORM_ref4] {{.*}} {0x[[INT]]}
|
2014-05-22 07:14:12 +08:00
|
|
|
; CHECK-NOT: DW_AT_location
|
|
|
|
|
DebugInfo: Lazily attach definition attributes to definitions.
This is a precursor to fixing inlined debug info where the concrete,
out-of-line definition may preceed any inlined usage. To cope with this,
the attributes that may appear on the concrete definition or the
abstract definition are delayed until the end of the module. Then, if an
abstract definition was created, it is referenced (and no other
attributes are added to the out-of-line definition), otherwise the
attributes are added directly to the out-of-line definition.
In a couple of cases this causes not just reordering of attributes, but
reordering of types. When the creation of the attribute is delayed, if
that creation would create a type (such as for a DW_AT_type attribute)
then other top level DIEs may've been constructed during the delay,
causing the referenced type to be created and added after those
intervening DIEs. In the extreme case, in cross-cu-inlining.ll, this
actually causes the DW_TAG_basic_type for "int" to move from one CU to
another.
llvm-svn: 209674
2014-05-28 02:37:43 +08:00
|
|
|
; CHECK: 0x[[INT]]: DW_TAG_base_type
|
|
|
|
; CHECK: DW_AT_name {{.*}} "int"
|
|
|
|
|
2014-05-22 07:14:12 +08:00
|
|
|
; Check the concrete out of line definition references the abstract and
|
|
|
|
; provides the address range and variable location
|
2014-11-13 07:48:14 +08:00
|
|
|
; CHECK: 0x[[FUNC:[0-9a-f]*]]{{.*}}DW_TAG_subprogram
|
2014-05-22 07:14:12 +08:00
|
|
|
; CHECK: DW_AT_low_pc
|
2014-10-06 11:36:31 +08:00
|
|
|
; CHECK: DW_AT_abstract_origin {{.*}} {0x[[ABS_FUNC]]} "_Z4funci"
|
2014-05-22 07:14:12 +08:00
|
|
|
; CHECK: DW_TAG_formal_parameter
|
|
|
|
; CHECK: DW_AT_location
|
2014-10-10 23:51:02 +08:00
|
|
|
; CHECK: DW_AT_abstract_origin {{.*}} {0x[[ABS_VAR]]} "x"
|
2014-05-22 07:14:12 +08:00
|
|
|
|
2014-11-15 00:15:53 +08:00
|
|
|
; Check that both the inline and the non out of line version of func are
|
|
|
|
; correctly referenced in the accelerator table. Before r221837, the one
|
|
|
|
; in the second compilation unit had a wrong offset
|
|
|
|
; CHECK-ACCEL: .apple_names contents:
|
|
|
|
; CHECK-ACCEL: Name{{.*}}"func"
|
|
|
|
; CHECK-ACCEL-NOT: Name
|
|
|
|
; CHECK-ACCEL: Atom[0]{{.*}}[[INLINED]]
|
|
|
|
; CHECK-ACCEL-NOT: Name
|
|
|
|
; CHECK-ACCEL: Atom[0]{{.*}}[[FUNC]]
|
|
|
|
|
2014-05-22 07:14:12 +08:00
|
|
|
@i = external global i32
|
|
|
|
|
|
|
|
; Function Attrs: uwtable
|
|
|
|
define i32 @main() #0 {
|
|
|
|
entry:
|
|
|
|
%x.addr.i = alloca i32, align 4
|
|
|
|
%retval = alloca i32, align 4
|
|
|
|
store i32 0, i32* %retval
|
2015-02-28 05:17:42 +08:00
|
|
|
%0 = load i32, i32* @i, align 4, !dbg !19
|
2014-05-22 07:14:12 +08:00
|
|
|
%1 = bitcast i32* %x.addr.i to i8*
|
|
|
|
call void @llvm.lifetime.start(i64 4, i8* %1)
|
|
|
|
store i32 %0, i32* %x.addr.i, align 4
|
IR: Make metadata typeless in assembly
Now that `Metadata` is typeless, reflect that in the assembly. These
are the matching assembly changes for the metadata/value split in
r223802.
- Only use the `metadata` type when referencing metadata from a call
intrinsic -- i.e., only when it's used as a `Value`.
- Stop pretending that `ValueAsMetadata` is wrapped in an `MDNode`
when referencing it from call intrinsics.
So, assembly like this:
define @foo(i32 %v) {
call void @llvm.foo(metadata !{i32 %v}, metadata !0)
call void @llvm.foo(metadata !{i32 7}, metadata !0)
call void @llvm.foo(metadata !1, metadata !0)
call void @llvm.foo(metadata !3, metadata !0)
call void @llvm.foo(metadata !{metadata !3}, metadata !0)
ret void, !bar !2
}
!0 = metadata !{metadata !2}
!1 = metadata !{i32* @global}
!2 = metadata !{metadata !3}
!3 = metadata !{}
turns into this:
define @foo(i32 %v) {
call void @llvm.foo(metadata i32 %v, metadata !0)
call void @llvm.foo(metadata i32 7, metadata !0)
call void @llvm.foo(metadata i32* @global, metadata !0)
call void @llvm.foo(metadata !3, metadata !0)
call void @llvm.foo(metadata !{!3}, metadata !0)
ret void, !bar !2
}
!0 = !{!2}
!1 = !{i32* @global}
!2 = !{!3}
!3 = !{}
I wrote an upgrade script that handled almost all of the tests in llvm
and many of the tests in cfe (even handling many `CHECK` lines). I've
attached it (or will attach it in a moment if you're speedy) to PR21532
to help everyone update their out-of-tree testcases.
This is part of PR21532.
llvm-svn: 224257
2014-12-16 03:07:53 +08:00
|
|
|
call void @llvm.dbg.declare(metadata i32* %x.addr.i, metadata !20, metadata !{!"0x102"}), !dbg !21
|
2015-02-28 05:17:42 +08:00
|
|
|
%2 = load i32, i32* %x.addr.i, align 4, !dbg !22
|
2014-05-22 07:14:12 +08:00
|
|
|
%mul.i = mul nsw i32 %2, 2, !dbg !22
|
|
|
|
%3 = bitcast i32* %x.addr.i to i8*, !dbg !22
|
|
|
|
call void @llvm.lifetime.end(i64 4, i8* %3), !dbg !22
|
|
|
|
ret i32 %mul.i, !dbg !19
|
|
|
|
}
|
|
|
|
|
|
|
|
; Function Attrs: alwaysinline nounwind uwtable
|
|
|
|
define i32 @_Z4funci(i32 %x) #1 {
|
|
|
|
entry:
|
|
|
|
%x.addr = alloca i32, align 4
|
|
|
|
store i32 %x, i32* %x.addr, align 4
|
IR: Make metadata typeless in assembly
Now that `Metadata` is typeless, reflect that in the assembly. These
are the matching assembly changes for the metadata/value split in
r223802.
- Only use the `metadata` type when referencing metadata from a call
intrinsic -- i.e., only when it's used as a `Value`.
- Stop pretending that `ValueAsMetadata` is wrapped in an `MDNode`
when referencing it from call intrinsics.
So, assembly like this:
define @foo(i32 %v) {
call void @llvm.foo(metadata !{i32 %v}, metadata !0)
call void @llvm.foo(metadata !{i32 7}, metadata !0)
call void @llvm.foo(metadata !1, metadata !0)
call void @llvm.foo(metadata !3, metadata !0)
call void @llvm.foo(metadata !{metadata !3}, metadata !0)
ret void, !bar !2
}
!0 = metadata !{metadata !2}
!1 = metadata !{i32* @global}
!2 = metadata !{metadata !3}
!3 = metadata !{}
turns into this:
define @foo(i32 %v) {
call void @llvm.foo(metadata i32 %v, metadata !0)
call void @llvm.foo(metadata i32 7, metadata !0)
call void @llvm.foo(metadata i32* @global, metadata !0)
call void @llvm.foo(metadata !3, metadata !0)
call void @llvm.foo(metadata !{!3}, metadata !0)
ret void, !bar !2
}
!0 = !{!2}
!1 = !{i32* @global}
!2 = !{!3}
!3 = !{}
I wrote an upgrade script that handled almost all of the tests in llvm
and many of the tests in cfe (even handling many `CHECK` lines). I've
attached it (or will attach it in a moment if you're speedy) to PR21532
to help everyone update their out-of-tree testcases.
This is part of PR21532.
llvm-svn: 224257
2014-12-16 03:07:53 +08:00
|
|
|
call void @llvm.dbg.declare(metadata i32* %x.addr, metadata !20, metadata !{!"0x102"}), !dbg !23
|
2015-02-28 05:17:42 +08:00
|
|
|
%0 = load i32, i32* %x.addr, align 4, !dbg !24
|
2014-05-22 07:14:12 +08:00
|
|
|
%mul = mul nsw i32 %0, 2, !dbg !24
|
|
|
|
ret i32 %mul, !dbg !24
|
|
|
|
}
|
|
|
|
|
|
|
|
; Function Attrs: nounwind readnone
|
Move the complex address expression out of DIVariable and into an extra
argument of the llvm.dbg.declare/llvm.dbg.value intrinsics.
Previously, DIVariable was a variable-length field that has an optional
reference to a Metadata array consisting of a variable number of
complex address expressions. In the case of OpPiece expressions this is
wasting a lot of storage in IR, because when an aggregate type is, e.g.,
SROA'd into all of its n individual members, the IR will contain n copies
of the DIVariable, all alike, only differing in the complex address
reference at the end.
By making the complex address into an extra argument of the
dbg.value/dbg.declare intrinsics, all of the pieces can reference the
same variable and the complex address expressions can be uniqued across
the CU, too.
Down the road, this will allow us to move other flags, such as
"indirection" out of the DIVariable, too.
The new intrinsics look like this:
declare void @llvm.dbg.declare(metadata %storage, metadata %var, metadata %expr)
declare void @llvm.dbg.value(metadata %storage, i64 %offset, metadata %var, metadata %expr)
This patch adds a new LLVM-local tag to DIExpressions, so we can detect
and pretty-print DIExpression metadata nodes.
What this patch doesn't do:
This patch does not touch the "Indirect" field in DIVariable; but moving
that into the expression would be a natural next step.
http://reviews.llvm.org/D4919
rdar://problem/17994491
Thanks to dblaikie and dexonsmith for reviewing this patch!
Note: I accidentally committed a bogus older version of this patch previously.
llvm-svn: 218787
2014-10-02 02:55:02 +08:00
|
|
|
declare void @llvm.dbg.declare(metadata, metadata, metadata) #2
|
2014-05-22 07:14:12 +08:00
|
|
|
|
|
|
|
; Function Attrs: nounwind
|
|
|
|
declare void @llvm.lifetime.start(i64, i8* nocapture) #3
|
|
|
|
|
|
|
|
; Function Attrs: nounwind
|
|
|
|
declare void @llvm.lifetime.end(i64, i8* nocapture) #3
|
|
|
|
|
|
|
|
attributes #0 = { uwtable "less-precise-fpmad"="false" "no-frame-pointer-elim"="true" "no-frame-pointer-elim-non-leaf" "no-infs-fp-math"="false" "no-nans-fp-math"="false" "stack-protector-buffer-size"="8" "unsafe-fp-math"="false" "use-soft-float"="false" }
|
|
|
|
attributes #1 = { alwaysinline nounwind uwtable "less-precise-fpmad"="false" "no-frame-pointer-elim"="true" "no-frame-pointer-elim-non-leaf" "no-infs-fp-math"="false" "no-nans-fp-math"="false" "stack-protector-buffer-size"="8" "unsafe-fp-math"="false" "use-soft-float"="false" }
|
|
|
|
attributes #2 = { nounwind readnone }
|
|
|
|
attributes #3 = { nounwind }
|
|
|
|
|
|
|
|
!llvm.dbg.cu = !{!0, !9}
|
|
|
|
!llvm.module.flags = !{!16, !17}
|
|
|
|
!llvm.ident = !{!18, !18}
|
|
|
|
|
IR: Make metadata typeless in assembly
Now that `Metadata` is typeless, reflect that in the assembly. These
are the matching assembly changes for the metadata/value split in
r223802.
- Only use the `metadata` type when referencing metadata from a call
intrinsic -- i.e., only when it's used as a `Value`.
- Stop pretending that `ValueAsMetadata` is wrapped in an `MDNode`
when referencing it from call intrinsics.
So, assembly like this:
define @foo(i32 %v) {
call void @llvm.foo(metadata !{i32 %v}, metadata !0)
call void @llvm.foo(metadata !{i32 7}, metadata !0)
call void @llvm.foo(metadata !1, metadata !0)
call void @llvm.foo(metadata !3, metadata !0)
call void @llvm.foo(metadata !{metadata !3}, metadata !0)
ret void, !bar !2
}
!0 = metadata !{metadata !2}
!1 = metadata !{i32* @global}
!2 = metadata !{metadata !3}
!3 = metadata !{}
turns into this:
define @foo(i32 %v) {
call void @llvm.foo(metadata i32 %v, metadata !0)
call void @llvm.foo(metadata i32 7, metadata !0)
call void @llvm.foo(metadata i32* @global, metadata !0)
call void @llvm.foo(metadata !3, metadata !0)
call void @llvm.foo(metadata !{!3}, metadata !0)
ret void, !bar !2
}
!0 = !{!2}
!1 = !{i32* @global}
!2 = !{!3}
!3 = !{}
I wrote an upgrade script that handled almost all of the tests in llvm
and many of the tests in cfe (even handling many `CHECK` lines). I've
attached it (or will attach it in a moment if you're speedy) to PR21532
to help everyone update their out-of-tree testcases.
This is part of PR21532.
llvm-svn: 224257
2014-12-16 03:07:53 +08:00
|
|
|
!0 = !{!"0x11\004\00clang version 3.5.0 \000\00\000\00\001", !1, !2, !2, !3, !2, !2} ; [ DW_TAG_compile_unit ] [/tmp/dbginfo/a.cpp] [DW_LANG_C_plus_plus]
|
|
|
|
!1 = !{!"a.cpp", !"/tmp/dbginfo"}
|
|
|
|
!2 = !{}
|
|
|
|
!3 = !{!4}
|
|
|
|
!4 = !{!"0x2e\00main\00main\00\003\000\001\000\006\00256\000\003", !1, !5, !6, null, i32 ()* @main, null, null, !2} ; [ DW_TAG_subprogram ] [line 3] [def] [main]
|
|
|
|
!5 = !{!"0x29", !1} ; [ DW_TAG_file_type ] [/tmp/dbginfo/a.cpp]
|
|
|
|
!6 = !{!"0x15\00\000\000\000\000\000\000", i32 0, null, null, !7, null, null, null} ; [ DW_TAG_subroutine_type ] [line 0, size 0, align 0, offset 0] [from ]
|
|
|
|
!7 = !{!8}
|
|
|
|
!8 = !{!"0x24\00int\000\0032\0032\000\000\005", null, null} ; [ DW_TAG_base_type ] [int] [line 0, size 32, align 32, offset 0, enc DW_ATE_signed]
|
|
|
|
!9 = !{!"0x11\004\00clang version 3.5.0 \000\00\000\00\001", !10, !2, !2, !11, !2, !2} ; [ DW_TAG_compile_unit ] [/tmp/dbginfo/b.cpp] [DW_LANG_C_plus_plus]
|
|
|
|
!10 = !{!"b.cpp", !"/tmp/dbginfo"}
|
|
|
|
!11 = !{!12}
|
|
|
|
!12 = !{!"0x2e\00func\00func\00_Z4funci\001\000\001\000\006\00256\000\001", !10, !13, !14, null, i32 (i32)* @_Z4funci, null, null, !2} ; [ DW_TAG_subprogram ] [line 1] [def] [func]
|
|
|
|
!13 = !{!"0x29", !10} ; [ DW_TAG_file_type ] [/tmp/dbginfo/b.cpp]
|
|
|
|
!14 = !{!"0x15\00\000\000\000\000\000\000", i32 0, null, null, !15, null, null, null} ; [ DW_TAG_subroutine_type ] [line 0, size 0, align 0, offset 0] [from ]
|
|
|
|
!15 = !{!8, !8}
|
|
|
|
!16 = !{i32 2, !"Dwarf Version", i32 4}
|
|
|
|
!17 = !{i32 2, !"Debug Info Version", i32 2}
|
|
|
|
!18 = !{!"clang version 3.5.0 "}
|
2015-01-15 06:27:36 +08:00
|
|
|
!19 = !MDLocation(line: 4, scope: !4)
|
IR: Make metadata typeless in assembly
Now that `Metadata` is typeless, reflect that in the assembly. These
are the matching assembly changes for the metadata/value split in
r223802.
- Only use the `metadata` type when referencing metadata from a call
intrinsic -- i.e., only when it's used as a `Value`.
- Stop pretending that `ValueAsMetadata` is wrapped in an `MDNode`
when referencing it from call intrinsics.
So, assembly like this:
define @foo(i32 %v) {
call void @llvm.foo(metadata !{i32 %v}, metadata !0)
call void @llvm.foo(metadata !{i32 7}, metadata !0)
call void @llvm.foo(metadata !1, metadata !0)
call void @llvm.foo(metadata !3, metadata !0)
call void @llvm.foo(metadata !{metadata !3}, metadata !0)
ret void, !bar !2
}
!0 = metadata !{metadata !2}
!1 = metadata !{i32* @global}
!2 = metadata !{metadata !3}
!3 = metadata !{}
turns into this:
define @foo(i32 %v) {
call void @llvm.foo(metadata i32 %v, metadata !0)
call void @llvm.foo(metadata i32 7, metadata !0)
call void @llvm.foo(metadata i32* @global, metadata !0)
call void @llvm.foo(metadata !3, metadata !0)
call void @llvm.foo(metadata !{!3}, metadata !0)
ret void, !bar !2
}
!0 = !{!2}
!1 = !{i32* @global}
!2 = !{!3}
!3 = !{}
I wrote an upgrade script that handled almost all of the tests in llvm
and many of the tests in cfe (even handling many `CHECK` lines). I've
attached it (or will attach it in a moment if you're speedy) to PR21532
to help everyone update their out-of-tree testcases.
This is part of PR21532.
llvm-svn: 224257
2014-12-16 03:07:53 +08:00
|
|
|
!20 = !{!"0x101\00x\0016777217\000", !12, !13, !8} ; [ DW_TAG_arg_variable ] [x] [line 1]
|
2015-01-15 06:27:36 +08:00
|
|
|
!21 = !MDLocation(line: 1, scope: !12, inlinedAt: !19)
|
|
|
|
!22 = !MDLocation(line: 2, scope: !12, inlinedAt: !19)
|
|
|
|
!23 = !MDLocation(line: 1, scope: !12)
|
|
|
|
!24 = !MDLocation(line: 2, scope: !12)
|
2014-05-22 07:14:12 +08:00
|
|
|
|