maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/CodeGen/PowerPC/aix-xcoff-textdisassembly.ll

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

23 lines
742 B
LLVM
Raw Normal View History

[AIX][XCOFF] created a test case to verify the raw text section of xcoffobject file SUMMARY: in the patch https://reviews.llvm.org/D66969 . we need a test case to verify the out text section of the xcoffobject file is correct or not. but we do not have llvm disassembly tools to dump the xcoffobjectfile . since we commit the patch https://reviews.llvm.org/D70255, we have tools for it. we create this test case for it. Reviewers: daltenty,hubert.reinterpretcast, Differential Revision: https://reviews.llvm.org/D70719
2019-12-06 23:12:09 +08:00
; RUN: llc -verify-machineinstrs -mcpu=pwr9 -mtriple powerpc-ibm-aix-xcoff -filetype=obj -o %t.o < %s
; RUN: llvm-objdump -D %t.o | FileCheck --check-prefix=CHECK %s
define i32 @foo() #0 {
entry:
ret i32 0
}
define i32 @foo1() #0 {
entry:
ret i32 1
}
; CHECK: Disassembly of section .text:{{[[:space:]] *}}
[llvm-objdump] -d: print `00000000 <foo>:` instead of `00000000 foo:` The new behavior matches GNU objdump. A pair of angle brackets makes tests slightly easier. `.foo:` is not unique and thus cannot be used in a `CHECK-LABEL:` directive. Without `-LABEL`, the CHECK line can match the `Disassembly of section` line and causes the next `CHECK-NEXT:` to fail. ``` Disassembly of section .foo: 0000000000001634 .foo: ``` Bdragon: <> has metalinguistic connotation. it just "feels right" Reviewed By: rupprecht Differential Revision: https://reviews.llvm.org/D75713
2020-03-06 06:18:38 +08:00
; CHECK-NEXT: 00000000 <.text>:
[AIX][XCOFF] created a test case to verify the raw text section of xcoffobject file SUMMARY: in the patch https://reviews.llvm.org/D66969 . we need a test case to verify the out text section of the xcoffobject file is correct or not. but we do not have llvm disassembly tools to dump the xcoffobjectfile . since we commit the patch https://reviews.llvm.org/D70255, we have tools for it. we create this test case for it. Reviewers: daltenty,hubert.reinterpretcast, Differential Revision: https://reviews.llvm.org/D70719
2019-12-06 23:12:09 +08:00
; CHECK-NEXT: 0: 38 60 00 00 li 3, 0
; CHECK-NEXT: 4: 4e 80 00 20 blr
; CHECK-NEXT: 8: 60 00 00 00 nop
; CHECK-NEXT: c: 60 00 00 00 nop
[llvm-objdump] -d: print `00000000 <foo>:` instead of `00000000 foo:` The new behavior matches GNU objdump. A pair of angle brackets makes tests slightly easier. `.foo:` is not unique and thus cannot be used in a `CHECK-LABEL:` directive. Without `-LABEL`, the CHECK line can match the `Disassembly of section` line and causes the next `CHECK-NEXT:` to fail. ``` Disassembly of section .foo: 0000000000001634 .foo: ``` Bdragon: <> has metalinguistic connotation. it just "feels right" Reviewed By: rupprecht Differential Revision: https://reviews.llvm.org/D75713
2020-03-06 06:18:38 +08:00
; CHECK: 00000010 <.foo1>:
[AIX][XCOFF] created a test case to verify the raw text section of xcoffobject file SUMMARY: in the patch https://reviews.llvm.org/D66969 . we need a test case to verify the out text section of the xcoffobject file is correct or not. but we do not have llvm disassembly tools to dump the xcoffobjectfile . since we commit the patch https://reviews.llvm.org/D70255, we have tools for it. we create this test case for it. Reviewers: daltenty,hubert.reinterpretcast, Differential Revision: https://reviews.llvm.org/D70719
2019-12-06 23:12:09 +08:00
; CHECK-NEXT: 10: 38 60 00 01 li 3, 1
; CHECK-NEXT: 14: 4e 80 00 20 blr