2016-09-27 21:15:54 +08:00
|
|
|
; RUN: llc -march=mips -mcpu=mips32 -O0 -relocation-model=pic -mips-tail-calls=1 < %s | FileCheck \
|
2016-09-21 17:43:40 +08:00
|
|
|
; RUN: %s -check-prefix=MIPS32
|
|
|
|
; RUN: llc -march=mips64 -mcpu=mips64 -O0 -relocation-model=pic -target-abi n64 \
|
2016-09-27 21:15:54 +08:00
|
|
|
; RUN: -mips-tail-calls=1 < %s | FileCheck %s -check-prefix=MIPS64
|
2016-09-21 17:43:40 +08:00
|
|
|
; RUN: llc -march=mips64 -mcpu=mips64 -O0 -relocation-model=pic -target-abi n32 \
|
2016-09-27 21:15:54 +08:00
|
|
|
; RUN: -mips-tail-calls=1 < %s | FileCheck %s -check-prefix=MIPS64
|
2016-09-21 17:43:40 +08:00
|
|
|
|
|
|
|
|
|
|
|
; LLVM PR/30197
|
|
|
|
; Test that the scheduler does not order loads and stores of arguments that
|
|
|
|
; are passed on the stack such that the arguments of the caller are clobbered
|
|
|
|
; too early.
|
|
|
|
|
|
|
|
; This test is more fragile than I'd like. The -NEXT directives enforce an
|
|
|
|
; assumption that any GOT related instructions will not appear between the
|
|
|
|
; loads and stores.
|
|
|
|
|
|
|
|
; O32 case: The last two arguments should appear at 16(sp), 20(sp). The order
|
|
|
|
; of the loads doesn't matter, but they have to become before the
|
|
|
|
; stores
|
2016-11-21 05:23:08 +08:00
|
|
|
define internal i32 @func2(i32 %a, i32 %b, i32 %c, i32 %d, i32 %e, i32 %f) {
|
|
|
|
%1 = add i32 %a, %b
|
|
|
|
%2 = add i32 %1, %c
|
|
|
|
%3 = add i32 %2, %d
|
|
|
|
%4 = add i32 %3, %e
|
|
|
|
%5 = add i32 %4, %f
|
|
|
|
ret i32 %5
|
|
|
|
}
|
2016-09-21 17:43:40 +08:00
|
|
|
|
|
|
|
define i32 @func1(i32 %a, i32 %b, i32 %c, i32 %d, i32 %e, i32 %f){
|
2016-10-18 21:05:42 +08:00
|
|
|
; MIPS32-LABEL: func1:
|
2016-09-21 17:43:40 +08:00
|
|
|
|
|
|
|
; MIPS32: lw ${{[0-9]+}}, {{[0-9]+}}($sp)
|
|
|
|
; MIPS32-NEXT: lw ${{[0-9]+}}, {{[0-9]+}}($sp)
|
|
|
|
; MIPS32-NEXT: sw ${{[0-9]+}}, {{[0-9]+}}($sp)
|
|
|
|
; MIPS32-NEXT: sw ${{[0-9]+}}, {{[0-9]+}}($sp)
|
2016-11-21 05:23:08 +08:00
|
|
|
%retval = tail call i32 @func2(i32 %a, i32 %f, i32 %c, i32 %d, i32 %e, i32 %b)
|
2016-09-21 17:43:40 +08:00
|
|
|
|
|
|
|
ret i32 %retval
|
|
|
|
}
|
|
|
|
|
|
|
|
; N64, N32 cases: N64 and N32 both pass 8 arguments in registers. The order
|
|
|
|
; of the loads doesn't matter, but they have to become before the
|
|
|
|
; stores
|
|
|
|
|
2016-11-21 05:23:08 +08:00
|
|
|
define internal i64 @func4(i64 %a, i64 %b, i64 %c, i64 %d, i64 %e,
|
|
|
|
i64 %f, i64 %g, i64 %h, i64 %i, i64 %j) {
|
|
|
|
%1 = add i64 %a, %b
|
|
|
|
%2 = add i64 %1, %c
|
|
|
|
%3 = add i64 %2, %d
|
|
|
|
%4 = add i64 %3, %e
|
|
|
|
%5 = add i64 %4, %f
|
|
|
|
%6 = add i64 %1, %g
|
|
|
|
%7 = add i64 %2, %h
|
|
|
|
%8 = add i64 %3, %i
|
|
|
|
%9 = add i64 %4, %j
|
|
|
|
ret i64 %5
|
|
|
|
}
|
2016-09-21 17:43:40 +08:00
|
|
|
define i64 @func3(i64 %a, i64 %b, i64 %c, i64 %d,
|
|
|
|
i64 %e, i64 %f, i64 %g, i64 %h,
|
|
|
|
i64 %i, i64 %j){
|
2016-10-18 21:05:42 +08:00
|
|
|
; MIPS64-LABEL: func3:
|
2016-09-21 17:43:40 +08:00
|
|
|
|
|
|
|
; MIPS64: ld ${{[0-9]+}}, {{[0-9]+}}($sp)
|
|
|
|
; MIPS64-NEXT: ld ${{[0-9]+}}, {{[0-9]+}}($sp)
|
|
|
|
; MIPS64-NEXT: sd ${{[0-9]+}}, {{[0-9]+}}($sp)
|
|
|
|
; MIPS64-NEXT: sd ${{[0-9]+}}, {{[0-9]+}}($sp)
|
|
|
|
%retval = tail call i64 @func4(i64 %a, i64 %j, i64 %c, i64 %d, i64 %e, i64 %f, i64 %g, i64 %h, i64 %i, i64 %b)
|
|
|
|
|
|
|
|
ret i64 %retval
|
|
|
|
}
|