mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-23 19:23:23 +01:00
d2e6077460
`llc -march` is problematic because it only switches the target architecture, but leaves the operating system unchanged. This occasionally leads to indeterministic tests because the OS from LLVM_DEFAULT_TARGET_TRIPLE is used. However we can simply always use `llc -mtriple` instead. This changes all the tests to do this to avoid people using -march when they copy and paste parts of tests. See also the discussion in https://reviews.llvm.org/D35287 llvm-svn: 309755
35 lines
1.1 KiB
LLVM
35 lines
1.1 KiB
LLVM
; RUN: llc < %s -mtriple=thumb-linux-androideabi -mcpu=arm1156t2-s -mattr=+thumb2 -verify-machineinstrs | FileCheck %s -check-prefix=Thumb-android
|
|
; RUN: llc < %s -mtriple=thumb-linux-androideabi -mcpu=arm1156t2-s -mattr=+thumb2 -filetype=obj
|
|
|
|
|
|
; Just to prevent the alloca from being optimized away
|
|
declare void @dummy_use(i32*, i32)
|
|
|
|
define void @test_basic() #0 {
|
|
%mem = alloca i32, i32 10
|
|
call void @dummy_use (i32* %mem, i32 10)
|
|
ret void
|
|
|
|
; Thumb-android: test_basic:
|
|
|
|
; Thumb-android: push {r4, r5}
|
|
; Thumb-android-NEXT: mrc p15, #0, r4, c13, c0, #3
|
|
; Thumb-android-NEXT: mov r5, sp
|
|
; Thumb-android-NEXT: ldr r4, [r4, #252]
|
|
; Thumb-android-NEXT: cmp r4, r5
|
|
; Thumb-android-NEXT: blo .LBB0_2
|
|
|
|
; Thumb-android: mov r4, #48
|
|
; Thumb-android-NEXT: mov r5, #0
|
|
; Thumb-android-NEXT: push {lr}
|
|
; Thumb-android-NEXT: bl __morestack
|
|
; Thumb-android-NEXT: ldr lr, [sp], #4
|
|
; Thumb-android-NEXT: pop {r4, r5}
|
|
; Thumb-android-NEXT: bx lr
|
|
|
|
; Thumb-android: pop {r4, r5}
|
|
|
|
}
|
|
|
|
attributes #0 = { "split-stack" }
|