llvm-project/llvm/test/CodeGen/MIR/X86/external-symbol-operands.mir

65 lines
2.2 KiB
Plaintext
Raw Normal View History

# RUN: llc -march=x86-64 -run-pass none -o - %s | FileCheck %s
# This test ensures that the MIR parser parses the external symbol machine
# operands correctly.
--- |
@__stack_chk_guard = external global i8*
define i32 @test(i32 %n) #0 {
entry:
%StackGuardSlot = alloca i8*
%StackGuard = load i8*, i8** @__stack_chk_guard
call void @llvm.stackprotector(i8* %StackGuard, i8** %StackGuardSlot)
%a = alloca [128 x i32], align 16
%idxprom = sext i32 %n to i64
%arrayidx = getelementptr inbounds [128 x i32], [128 x i32]* %a, i64 0, i64 %idxprom
%0 = load i32, i32* %arrayidx, align 4
call void @llvm.stackprotectorcheck(i8** @__stack_chk_guard)
ret i32 %0
}
declare void @llvm.stackprotector(i8*, i8**) #1
declare void @llvm.stackprotectorcheck(i8**) #1
attributes #0 = { ssp "stack-protector-buffer-size"="8" }
attributes #1 = { nounwind }
...
---
name: test
tracksRegLiveness: true
MIR Serialization: Change MIR syntax - use custom syntax for MBBs. This commit modifies the way the machine basic blocks are serialized - now the machine basic blocks are serialized using a custom syntax instead of relying on YAML primitives. Instead of using YAML mappings to represent the individual machine basic blocks in a machine function's body, the new syntax uses a single YAML block scalar which contains all of the machine basic blocks and instructions for that function. This is an example of a function's body that uses the old syntax: body: - id: 0 name: entry instructions: - '%eax = MOV32r0 implicit-def %eflags' - 'RETQ %eax' ... The same body is now written like this: body: | bb.0.entry: %eax = MOV32r0 implicit-def %eflags RETQ %eax ... This syntax change is motivated by the fact that the bundled machine instructions didn't map that well to the old syntax which was using a single YAML sequence to store all of the machine instructions in a block. The bundled machine instructions internally use flags like BundledPred and BundledSucc to determine the bundles, and serializing them as MI flags using the old syntax would have had a negative impact on the readability and the ease of editing for MIR files. The new syntax allows me to serialize the bundled machine instructions using a block construct without relying on the internal flags, for example: BUNDLE implicit-def dead %itstate, implicit-def %s1 ... { t2IT 1, 24, implicit-def %itstate %s1 = VMOVS killed %s0, 1, killed %cpsr, implicit killed %itstate } This commit also converts the MIR testcases to the new syntax. I developed a script that can convert from the old syntax to the new one. I will post the script on the llvm-commits mailing list in the thread for this commit. llvm-svn: 244982
2015-08-14 07:10:16 +08:00
body: |
bb.0.entry:
successors: %bb.1.entry, %bb.2.entry
liveins: %edi
%rsp = SUB64ri32 %rsp, 520, implicit-def %eflags
%rcx = LOAD_STACK_GUARD
MOV64mr %rsp, 1, _, 512, _, %rcx
%rax = MOVSX64rr32 %edi
%eax = MOV32rm %rsp, 4, %rax, 0, _
CMP64rm %rcx, %rsp, 1, _, 512, _, implicit-def %eflags
JNE_1 %bb.2.entry, implicit %eflags
bb.1.entry:
liveins: %eax
%rsp = ADD64ri32 %rsp, 520, implicit-def %eflags
RETQ %eax
bb.2.entry:
; CHECK: CALL64pcrel32 $__stack_chk_fail,
; CHECK-NEXT: CALL64pcrel32 $__stack_chk_fail.09-_,
; CHECK-NEXT: CALL64pcrel32 $"__stack_chk_fail$",
; CHECK-NEXT: CALL64pcrel32 $"$Quoted \09 External symbol \11 ",
; CHECK-NEXT: CALL64pcrel32 $__stack_chk_fail + 2,
; CHECK-NEXT: CALL64pcrel32 $" check stack - 20" - 20,
CALL64pcrel32 $__stack_chk_fail, csr_64, implicit %rsp, implicit-def %rsp
CALL64pcrel32 $__stack_chk_fail.09-_, csr_64, implicit %rsp, implicit-def %rsp
CALL64pcrel32 $__stack_chk_fail$, csr_64, implicit %rsp, implicit-def %rsp
CALL64pcrel32 $"$Quoted \09 External symbol \11 ", csr_64, implicit %rsp, implicit-def %rsp
CALL64pcrel32 $__stack_chk_fail + 2, csr_64, implicit %rsp, implicit-def %rsp
CALL64pcrel32 $" check stack - 20" - 20, csr_64, implicit %rsp, implicit-def %rsp
...