2015-02-13 01:43:22 +00:00
|
|
|
; RUN: llvm-as < %s | llvm-dis | llvm-as | llvm-dis | FileCheck %s
|
|
|
|
|
; RUN: verify-uselistorder %s
|
|
|
|
|
|
|
|
|
|
; CHECK: !named = !{!0, !1, !2, !3, !4, !4}
|
|
|
|
|
!named = !{!0, !1, !2, !3, !4, !5}
|
|
|
|
|
|
IR: Change MDFile to directly store the filename/directory
In the old (well, current) schema, there are two types of file
references: untagged and tagged (the latter references the former).
!0 = !{!"filename", !"/directory"}
!1 = !{!"0x29", !1} ; DW_TAG_file_type [filename] [/directory]
The interface to `DIBuilder` universally takes the tagged version,
described by `DIFile`. However, most `file:` references actually use
the untagged version directly.
In the new hierarchy, I'm merging this into a single node: `MDFile`.
Originally I'd planned to keep the old schema unchanged until after I
moved the new hierarchy into place.
However, it turns out to be trivial to make `MDFile` match both nodes at
the same time.
- Anyone referencing !1 does so through `DIFile`, whose implementation
I need to gut anyway (as I do the rest of the `DIDescriptor`s).
- Anyone referencing !0 just references an `MDNode`, and expects a
node with two `MDString` operands.
This commit achieves that, and updates all the testcases for the parts
of the new hierarchy that used the two-node schema (I've replaced the
untagged nodes with `distinct !{}` to make the diff clear (otherwise the
metadata all gets renumbered); it might be worthwhile to come back and
delete those nodes and renumber the world, not sure).
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@230057 91177308-0d34-0410-b5e6-96231b3b80d8
2015-02-20 20:35:17 +00:00
|
|
|
!0 = distinct !{}
|
2015-02-13 01:43:22 +00:00
|
|
|
!1 = !MDFile(filename: "path/to/file", directory: "/path/to/dir")
|
|
|
|
|
!2 = distinct !{}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
; CHECK: !2 = distinct !{}
|
IR: Change MDFile to directly store the filename/directory
In the old (well, current) schema, there are two types of file
references: untagged and tagged (the latter references the former).
!0 = !{!"filename", !"/directory"}
!1 = !{!"0x29", !1} ; DW_TAG_file_type [filename] [/directory]
The interface to `DIBuilder` universally takes the tagged version,
described by `DIFile`. However, most `file:` references actually use
the untagged version directly.
In the new hierarchy, I'm merging this into a single node: `MDFile`.
Originally I'd planned to keep the old schema unchanged until after I
moved the new hierarchy into place.
However, it turns out to be trivial to make `MDFile` match both nodes at
the same time.
- Anyone referencing !1 does so through `DIFile`, whose implementation
I need to gut anyway (as I do the rest of the `DIDescriptor`s).
- Anyone referencing !0 just references an `MDNode`, and expects a
node with two `MDString` operands.
This commit achieves that, and updates all the testcases for the parts
of the new hierarchy that used the two-node schema (I've replaced the
untagged nodes with `distinct !{}` to make the diff clear (otherwise the
metadata all gets renumbered); it might be worthwhile to come back and
delete those nodes and renumber the world, not sure).
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@230057 91177308-0d34-0410-b5e6-96231b3b80d8
2015-02-20 20:35:17 +00:00
|
|
|
; CHECK-NEXT: !3 = !MDObjCProperty(name: "foo", file: !1, line: 7, setter: "setFoo", getter: "getFoo", attributes: 7, type: !2)
|
|
|
|
|
!3 = !MDObjCProperty(name: "foo", file: !1, line: 7, setter: "setFoo",
|
2015-02-13 01:43:22 +00:00
|
|
|
getter: "getFoo", attributes: 7, type: !2)
|
|
|
|
|
|
2015-03-16 19:01:54 +00:00
|
|
|
; CHECK-NEXT: !4 = !MDObjCProperty()
|
|
|
|
|
!4 = !MDObjCProperty(name: "", file: null, line: 0, setter: "", getter: "",
|
2015-02-13 01:43:22 +00:00
|
|
|
attributes: 0, type: null)
|
2015-03-16 19:01:54 +00:00
|
|
|
!5 = !MDObjCProperty()
|