1*9880d681SAndroid Build Coastguard Worker; RUN: llc < %s | FileCheck %s 2*9880d681SAndroid Build Coastguard Worker; rdar://8051990 3*9880d681SAndroid Build Coastguard Worker 4*9880d681SAndroid Build Coastguard Workertarget datalayout = "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64" 5*9880d681SAndroid Build Coastguard Workertarget triple = "x86_64-apple-darwin11" 6*9880d681SAndroid Build Coastguard Worker 7*9880d681SAndroid Build Coastguard Worker; ISel doesn't yet know how to eliminate this extra zero-extend. But until 8*9880d681SAndroid Build Coastguard Worker; it knows how to do so safely, it shouldn;t eliminate it. 9*9880d681SAndroid Build Coastguard Worker; CHECK: movzbl (%rdi), %eax 10*9880d681SAndroid Build Coastguard Worker; CHECK: movzwl %ax, %eax 11*9880d681SAndroid Build Coastguard Worker 12*9880d681SAndroid Build Coastguard Workerdefine i64 @_ZL5matchPKtPKhiR9MatchData(i8* %tmp13) nounwind { 13*9880d681SAndroid Build Coastguard Workerentry: 14*9880d681SAndroid Build Coastguard Worker %tmp14 = load i8, i8* %tmp13, align 1 15*9880d681SAndroid Build Coastguard Worker %tmp17 = zext i8 %tmp14 to i16 16*9880d681SAndroid Build Coastguard Worker br label %bb341 17*9880d681SAndroid Build Coastguard Worker 18*9880d681SAndroid Build Coastguard Workerbb341: 19*9880d681SAndroid Build Coastguard Worker %tmp18 = add i16 %tmp17, -1 20*9880d681SAndroid Build Coastguard Worker %tmp23 = sext i16 %tmp18 to i64 21*9880d681SAndroid Build Coastguard Worker ret i64 %tmp23 22*9880d681SAndroid Build Coastguard Worker} 23