1; RUN: llc < %s -march=x86-64 | FileCheck %s 2; Verify that we are using the efficient uitofp --> sitofp lowering illustrated 3; by the compiler_rt implementation of __floatundisf. 4; <rdar://problem/8493982> 5 6target 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" 7target triple = "x86_64-apple-darwin10.0.0" 8 9; FIXME: This test could generate this code: 10; 11; ## BB#0: ## %entry 12; testq %rdi, %rdi 13; jns LBB0_2 14; ## BB#1: 15; movq %rdi, %rax 16; shrq %rax 17; andq $1, %rdi 18; orq %rax, %rdi 19; cvtsi2ssq %rdi, %xmm0 20; addss %xmm0, %xmm0 21; ret 22; LBB0_2: ## %entry 23; cvtsi2ssq %rdi, %xmm0 24; ret 25; 26; The blocks come from lowering: 27; 28; %vreg7<def> = CMOV_FR32 %vreg6<kill>, %vreg5<kill>, 15, %EFLAGS<imp-use>; FR32:%vreg7,%vreg6,%vreg5 29; 30; If the instruction had an EFLAGS<kill> flag, it wouldn't need to mark EFLAGS 31; as live-in on the new blocks, and machine sinking would be able to sink 32; everything below the test. 33 34; CHECK: shrq 35; CHECK: andq 36; CHECK-NEXT: orq 37; CHECK: testq %rdi, %rdi 38; CHECK-NEXT: jns LBB0_2 39; CHECK: cvtsi2ss 40; CHECK: LBB0_2 41; CHECK-NEXT: cvtsi2ss 42define float @test(i64 %a) { 43entry: 44 %b = uitofp i64 %a to float 45 ret float %b 46} 47