1*9880d681SAndroid Build Coastguard Worker; RUN: llc %s -o - -verify-machineinstrs -fast-isel=true | FileCheck %s 2*9880d681SAndroid Build Coastguard Worker 3*9880d681SAndroid Build Coastguard Workertarget datalayout = "e-m:o-p:32:32-f64:32:64-v64:32:64-v128:32:128-a:0:32-n32-S32" 4*9880d681SAndroid Build Coastguard Workertarget triple = "thumbv7-apple-ios8.0.0" 5*9880d681SAndroid Build Coastguard Worker 6*9880d681SAndroid Build Coastguard Worker; When materializing the '2' for the shifts below, the second shift kills the vreg 7*9880d681SAndroid Build Coastguard Worker; we materialize in to. However, the first shift was also killing that vreg. 8*9880d681SAndroid Build Coastguard Worker; This fails the machine verifier because the second use then thinks its reading an 9*9880d681SAndroid Build Coastguard Worker; undefined register. 10*9880d681SAndroid Build Coastguard Worker 11*9880d681SAndroid Build Coastguard Worker; CHECK: lsr.w 12*9880d681SAndroid Build Coastguard Worker; CHECK: lsr.w 13*9880d681SAndroid Build Coastguard Worker 14*9880d681SAndroid Build Coastguard Workerdeclare void @foo(i32, i32) 15*9880d681SAndroid Build Coastguard Worker 16*9880d681SAndroid Build Coastguard Worker; Function Attrs: minsize 17*9880d681SAndroid Build Coastguard Workerdefine i32 @test(i32 %tmp3, i32 %tmp9) #0 { 18*9880d681SAndroid Build Coastguard Workerbb: 19*9880d681SAndroid Build Coastguard Worker %tmp4 = lshr i32 %tmp3, 2 20*9880d681SAndroid Build Coastguard Worker %tmp10 = lshr i32 %tmp9, 2 21*9880d681SAndroid Build Coastguard Worker call void @foo(i32 %tmp10, i32 %tmp4) 22*9880d681SAndroid Build Coastguard Worker unreachable 23*9880d681SAndroid Build Coastguard Worker} 24*9880d681SAndroid Build Coastguard Worker 25*9880d681SAndroid Build Coastguard Workerattributes #0 = { minsize } 26