maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/Assembler/metadata.ll

42 lines
1.1 KiB
LLVM
Raw Normal View History

FileCheckize these testcases. llvm-svn: 154281
2012-04-08 19:00:38 +08:00
; RUN: llvm-as < %s | llvm-dis | llvm-as | llvm-dis | FileCheck %s
verify-uselistorder: Force -preserve-bc-use-list-order llvm-svn: 216022
2014-08-20 05:08:27 +08:00
; RUN: verify-uselistorder %s
FileCheckize these testcases. llvm-svn: 154281
2012-04-08 19:00:38 +08:00
CHECK-LABEL-ize test. NFC llvm-svn: 238866
2015-06-03 05:25:03 +08:00
; CHECK-LABEL: @test
FileCheckize these testcases. llvm-svn: 154281
2012-04-08 19:00:38 +08:00
; CHECK: ret void, !bar !1, !foo !0
Do not crash when .ll printing metadata that smells like debug info, but isn't. llvm-svn: 92268
2009-12-30 05:17:33 +08:00
define void @test() {
Each instruction is allowed to have *multiple* different metadata objects on them. Though the entire compiler supports this, the asmparser didn't. llvm-svn: 92270
2009-12-30 05:25:40 +08:00
add i32 2, 1, !bar !0
add i32 1, 2, !foo !1
fix parsing of mdstring values. llvm-svn: 92290
2009-12-30 12:13:37 +08:00
call void @llvm.dbg.func.start(metadata !"foo")
reimplement insertvalue/extractvalue metadata handling to not blindly accept invalid input. Actually add a testcase. llvm-svn: 92297
2009-12-30 13:14:00 +08:00
extractvalue {{i32, i32}, i32} undef, 0, 1, !foo !0
Each instruction is allowed to have *multiple* different metadata objects on them. Though the entire compiler supports this, the asmparser didn't. llvm-svn: 92270
2009-12-30 05:25:40 +08:00
ret void, !foo !0, !bar !1
Do not crash when .ll printing metadata that smells like debug info, but isn't. llvm-svn: 92268
2009-12-30 05:17:33 +08:00
}
CHECK-LABEL-ize test. NFC llvm-svn: 238866
2015-06-03 05:25:03 +08:00
; CHECK-LABEL: define void @test2() !foo !2 !baz !3
IR: Add assembly/bitcode support for function metadata attachments Add serialization support for function metadata attachments (added in r235783). The syntax is: define @foo() !attach !0 { Metadata attachments are only allowed on functions with bodies. Since they come before the `{`, they're not really part of the body; since they require a body, they're not really part of the header. In `LLParser` I gave them a separate function called from `ParseDefine()`, `ParseOptionalFunctionMetadata()`. In bitcode, I'm using the same `METADATA_ATTACHMENT` record used by instructions. Instruction metadata attachments are included in a special "attachment" block at the end of a `Function`. The attachment records are laid out like this: InstID (KindID MetadataID)+ Note that these records always have an odd number of fields. The new code takes advantage of this to recognize function attachments (which don't need an instruction ID): (KindID MetadataID)+ This means we can use the same attachment block already used for instructions. This is part of PR23340. llvm-svn: 235785
2015-04-25 06:04:41 +08:00
define void @test2() !foo !2 !baz !3 {
unreachable
}
CHECK-LABEL-ize test. NFC llvm-svn: 238866
2015-06-03 05:25:03 +08:00
; CHECK-LABEL: define void @test3() !bar !3
IR: Add assembly/bitcode support for function metadata attachments Add serialization support for function metadata attachments (added in r235783). The syntax is: define @foo() !attach !0 { Metadata attachments are only allowed on functions with bodies. Since they come before the `{`, they're not really part of the body; since they require a body, they're not really part of the header. In `LLParser` I gave them a separate function called from `ParseDefine()`, `ParseOptionalFunctionMetadata()`. In bitcode, I'm using the same `METADATA_ATTACHMENT` record used by instructions. Instruction metadata attachments are included in a special "attachment" block at the end of a `Function`. The attachment records are laid out like this: InstID (KindID MetadataID)+ Note that these records always have an odd number of fields. The new code takes advantage of this to recognize function attachments (which don't need an instruction ID): (KindID MetadataID)+ This means we can use the same attachment block already used for instructions. This is part of PR23340. llvm-svn: 235785
2015-04-25 06:04:41 +08:00
; CHECK: unreachable, !bar !4
define void @test3() !bar !3 {
unreachable, !bar !4
}
[IR/AsmWriter] Output escape sequences if the first character isdigit() If the first character in a metadata attachment's name is a digit, it has to be output using an escape sequence, otherwise it's not valid text IR. Removed an over-zealous assert from LLVMContext which didn't allow this. The rule should only apply to text IR. Actual names can have any sequence of non-NUL bytes. Also added some documentation on accepted names. Bug found with AFL fuzz. llvm-svn: 238867
2015-06-03 05:25:08 +08:00
; CHECK-LABEL: define void @test_attachment_name() {
; CHECK: unreachable, !\342abc !4
define void @test_attachment_name() {
;; Escape the first character when printing text IR, since it's a digit
unreachable, !\34\32abc !4
}
IR: Give 'DI' prefix to debug info metadata Finish off PR23080 by renaming the debug info IR constructs from `MD*` to `DI*`. The last of the `DIDescriptor` classes were deleted in r235356, and the last of the related typedefs removed in r235413, so this has all baked for about a week. Note: If you have out-of-tree code (like a frontend), I recommend that you get everything compiling and tests passing with the *previous* commit before updating to this one. It'll be easier to keep track of what code is using the `DIDescriptor` hierarchy and what you've already updated, and I think you're extremely unlikely to insert bugs. YMMV of course. Back to *this* commit: I did this using the rename-md-di-nodes.sh upgrade script I've attached to PR23080 (both code and testcases) and filtered through clang-format-diff.py. I edited the tests for test/Assembler/invalid-generic-debug-node-*.ll by hand since the columns were off-by-three. It should work on your out-of-tree testcases (and code, if you've followed the advice in the previous paragraph). Some of the tests are in badly named files now (e.g., test/Assembler/invalid-mdcompositetype-missing-tag.ll should be 'dicompositetype'); I'll come back and move the files in a follow-up commit. llvm-svn: 236120
2015-04-30 00:38:44 +08:00
!0 = !DILocation(line: 662302, column: 26, scope: !1)
DI: Require subprogram definitions to be distinct As a follow-up to r246098, require `DISubprogram` definitions (`isDefinition: true`) to be 'distinct'. Specifically, add an assembler check, a verifier check, and bitcode upgrading logic to combat testcase bitrot after the `DIBuilder` change. While working on the testcases, I realized that test/Linker/subprogram-linkonce-weak-odr.ll isn't relevant anymore. Its purpose was to check for a corner case in PR22792 where two subprogram definitions match exactly and share the same metadata node. The new verifier check, requiring that subprogram definitions are 'distinct', precludes that possibility. I updated almost all the IR with the following script: git grep -l -E -e '= !DISubprogram\(.* isDefinition: true' | grep -v test/Bitcode | xargs sed -i '' -e 's/= \(!DISubprogram(.*, isDefinition: true\)/= distinct \1/' Likely some variant of would work for out-of-tree testcases. llvm-svn: 246327
2015-08-29 04:26:49 +08:00
!1 = distinct !DISubprogram(name: "foo")
IR: Add assembly/bitcode support for function metadata attachments Add serialization support for function metadata attachments (added in r235783). The syntax is: define @foo() !attach !0 { Metadata attachments are only allowed on functions with bodies. Since they come before the `{`, they're not really part of the body; since they require a body, they're not really part of the header. In `LLParser` I gave them a separate function called from `ParseDefine()`, `ParseOptionalFunctionMetadata()`. In bitcode, I'm using the same `METADATA_ATTACHMENT` record used by instructions. Instruction metadata attachments are included in a special "attachment" block at the end of a `Function`. The attachment records are laid out like this: InstID (KindID MetadataID)+ Note that these records always have an odd number of fields. The new code takes advantage of this to recognize function attachments (which don't need an instruction ID): (KindID MetadataID)+ This means we can use the same attachment block already used for instructions. This is part of PR23340. llvm-svn: 235785
2015-04-25 06:04:41 +08:00
!2 = distinct !{}
!3 = distinct !{}
!4 = distinct !{}
fix parsing of mdstring values. llvm-svn: 92290
2009-12-30 12:13:37 +08:00
declare void @llvm.dbg.func.start(metadata) nounwind readnone
add some basic named MD tests. llvm-svn: 92336
2009-12-31 11:00:49 +08:00
!foo = !{ !0 }
!bar = !{ !1 }