1*9880d681SAndroid Build Coastguard Worker; RUN: llc < %s -O3 -march=x86-64 |FileCheck %s 2*9880d681SAndroid Build Coastguard Workerdefine i64 @foo(i1 %z, i192* %p, i192* %q) 3*9880d681SAndroid Build Coastguard Worker{ 4*9880d681SAndroid Build Coastguard Worker; If const 128 is hoisted to a variable, then in basic block L_val2 we would 5*9880d681SAndroid Build Coastguard Worker; have %lshr2 = lshr i192 %data2, %const, and the definition of %const would 6*9880d681SAndroid Build Coastguard Worker; be in another basic block. As a result, a very inefficient code might be 7*9880d681SAndroid Build Coastguard Worker; produced. Here we check that this doesn't occur. 8*9880d681SAndroid Build Coastguard Workerentry: 9*9880d681SAndroid Build Coastguard Worker %data1 = load i192, i192* %p, align 8 10*9880d681SAndroid Build Coastguard Worker %lshr1 = lshr i192 %data1, 128 11*9880d681SAndroid Build Coastguard Worker %val1 = trunc i192 %lshr1 to i64 12*9880d681SAndroid Build Coastguard Worker br i1 %z, label %End, label %L_val2 13*9880d681SAndroid Build Coastguard Worker 14*9880d681SAndroid Build Coastguard Worker; CHECK: movq 16(%rdx), %rax 15*9880d681SAndroid Build Coastguard Worker; CHECK-NEXT: retq 16*9880d681SAndroid Build Coastguard WorkerL_val2: 17*9880d681SAndroid Build Coastguard Worker %data2 = load i192, i192* %q, align 8 18*9880d681SAndroid Build Coastguard Worker %lshr2 = lshr i192 %data2, 128 19*9880d681SAndroid Build Coastguard Worker %val2 = trunc i192 %lshr2 to i64 20*9880d681SAndroid Build Coastguard Worker br label %End 21*9880d681SAndroid Build Coastguard Worker 22*9880d681SAndroid Build Coastguard WorkerEnd: 23*9880d681SAndroid Build Coastguard Worker %p1 = phi i64 [%val1,%entry], [%val2,%L_val2] 24*9880d681SAndroid Build Coastguard Worker ret i64 %p1 25*9880d681SAndroid Build Coastguard Worker} 26