1*9880d681SAndroid Build Coastguard Worker; RUN: opt < %s -instsimplify 2*9880d681SAndroid Build Coastguard Worker 3*9880d681SAndroid Build Coastguard Worker; The mul can be proved to always overflow (turning a negative value 4*9880d681SAndroid Build Coastguard Worker; into a positive one) and thus results in undefined behaviour. At 5*9880d681SAndroid Build Coastguard Worker; the same time we were deducing from the nsw flag that that mul could 6*9880d681SAndroid Build Coastguard Worker; be assumed to have a negative value (since if not it has an undefined 7*9880d681SAndroid Build Coastguard Worker; value, which can be taken to be negative). We were reporting the mul 8*9880d681SAndroid Build Coastguard Worker; as being both positive and negative, firing an assertion! 9*9880d681SAndroid Build Coastguard Workerdefine i1 @test1(i32 %a) { 10*9880d681SAndroid Build Coastguard Workerentry: 11*9880d681SAndroid Build Coastguard Worker %0 = or i32 %a, 1 12*9880d681SAndroid Build Coastguard Worker %1 = shl i32 %0, 31 13*9880d681SAndroid Build Coastguard Worker %2 = mul nsw i32 %1, 4 14*9880d681SAndroid Build Coastguard Worker %3 = and i32 %2, -4 15*9880d681SAndroid Build Coastguard Worker %4 = icmp ne i32 %3, 0 16*9880d681SAndroid Build Coastguard Worker ret i1 %4 17*9880d681SAndroid Build Coastguard Worker} 18