1*9880d681SAndroid Build Coastguard Worker; Test use of RISBG vs RISBGN on zEC12. 2*9880d681SAndroid Build Coastguard Worker; 3*9880d681SAndroid Build Coastguard Worker; RUN: llc < %s -mtriple=s390x-linux-gnu -mcpu=zEC12 | FileCheck %s 4*9880d681SAndroid Build Coastguard Worker 5*9880d681SAndroid Build Coastguard Worker; On zEC12, we generally prefer RISBGN. 6*9880d681SAndroid Build Coastguard Workerdefine i64 @f1(i64 %a, i64 %b) { 7*9880d681SAndroid Build Coastguard Worker; CHECK-LABEL: f1: 8*9880d681SAndroid Build Coastguard Worker; CHECK: risbgn %r2, %r3, 60, 62, 0 9*9880d681SAndroid Build Coastguard Worker; CHECK: br %r14 10*9880d681SAndroid Build Coastguard Worker %anda = and i64 %a, -15 11*9880d681SAndroid Build Coastguard Worker %andb = and i64 %b, 14 12*9880d681SAndroid Build Coastguard Worker %or = or i64 %anda, %andb 13*9880d681SAndroid Build Coastguard Worker ret i64 %or 14*9880d681SAndroid Build Coastguard Worker} 15*9880d681SAndroid Build Coastguard Worker 16*9880d681SAndroid Build Coastguard Worker; But we may fall back to RISBG if we can use the condition code. 17*9880d681SAndroid Build Coastguard Workerdefine i64 @f2(i64 %a, i64 %b, i32* %c) { 18*9880d681SAndroid Build Coastguard Worker; CHECK-LABEL: f2: 19*9880d681SAndroid Build Coastguard Worker; CHECK: risbg %r2, %r3, 60, 62, 0 20*9880d681SAndroid Build Coastguard Worker; CHECK-NEXT: ipm 21*9880d681SAndroid Build Coastguard Worker; CHECK: br %r14 22*9880d681SAndroid Build Coastguard Worker %anda = and i64 %a, -15 23*9880d681SAndroid Build Coastguard Worker %andb = and i64 %b, 14 24*9880d681SAndroid Build Coastguard Worker %or = or i64 %anda, %andb 25*9880d681SAndroid Build Coastguard Worker %cmp = icmp sgt i64 %or, 0 26*9880d681SAndroid Build Coastguard Worker %conv = zext i1 %cmp to i32 27*9880d681SAndroid Build Coastguard Worker store i32 %conv, i32* %c, align 4 28*9880d681SAndroid Build Coastguard Worker ret i64 %or 29*9880d681SAndroid Build Coastguard Worker} 30*9880d681SAndroid Build Coastguard Worker 31