1*9880d681SAndroid Build Coastguard Worker; RUN: llc < %s -mcpu=swift -mtriple=armv7s-apple-ios | FileCheck %s 2*9880d681SAndroid Build Coastguard Worker; RUN: llc < %s -arm-assume-misaligned-load-store -mcpu=swift -mtriple=armv7s-apple-ios | FileCheck %s 3*9880d681SAndroid Build Coastguard Worker 4*9880d681SAndroid Build Coastguard Worker; Check that we avoid producing vldm instructions using d registers that 5*9880d681SAndroid Build Coastguard Worker; begin in the most-significant half of a q register. These require more 6*9880d681SAndroid Build Coastguard Worker; micro-ops on swift and so aren't worth combining. 7*9880d681SAndroid Build Coastguard Worker 8*9880d681SAndroid Build Coastguard Worker; CHECK-LABEL: test_vldm 9*9880d681SAndroid Build Coastguard Worker; CHECK: vldmia r{{[0-9]+}}, {d2, d3, d4} 10*9880d681SAndroid Build Coastguard Worker; CHECK-NOT: vldmia r{{[0-9]+}}, {d1, d2, d3, d4} 11*9880d681SAndroid Build Coastguard Worker 12*9880d681SAndroid Build Coastguard Workerdeclare fastcc void @force_register(double %d0, double %d1, double %d2, double %d3, double %d4) 13*9880d681SAndroid Build Coastguard Worker 14*9880d681SAndroid Build Coastguard Workerdefine void @test_vldm(double* %x, double * %y) { 15*9880d681SAndroid Build Coastguard Workerentry: 16*9880d681SAndroid Build Coastguard Worker %addr1 = getelementptr double, double * %x, i32 1 17*9880d681SAndroid Build Coastguard Worker %addr2 = getelementptr double, double * %x, i32 2 18*9880d681SAndroid Build Coastguard Worker %addr3 = getelementptr double, double * %x, i32 3 19*9880d681SAndroid Build Coastguard Worker %d0 = load double , double * %y 20*9880d681SAndroid Build Coastguard Worker %d1 = load double , double * %x 21*9880d681SAndroid Build Coastguard Worker %d2 = load double , double * %addr1 22*9880d681SAndroid Build Coastguard Worker %d3 = load double , double * %addr2 23*9880d681SAndroid Build Coastguard Worker %d4 = load double , double * %addr3 24*9880d681SAndroid Build Coastguard Worker ; We are trying to force x[0-3] in registers d1 to d4 so that we can test we 25*9880d681SAndroid Build Coastguard Worker ; don't form a "vldmia rX, {d1, d2, d3, d4}". 26*9880d681SAndroid Build Coastguard Worker ; We are relying on the calling convention and that register allocation 27*9880d681SAndroid Build Coastguard Worker ; properly coalesces registers. 28*9880d681SAndroid Build Coastguard Worker call fastcc void @force_register(double %d0, double %d1, double %d2, double %d3, double %d4) 29*9880d681SAndroid Build Coastguard Worker ret void 30*9880d681SAndroid Build Coastguard Worker} 31