Generalize ExpandIntToFP to handle the case where the operand is legal

and it's the result that requires expansion. This code is a little confusing
because the TargetLoweringInfo tables for [US]INT_TO_FP use the operand type
(the integer type) rather than the result type. 


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@48206 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Dan Gohman
2008-03-11 01:59:03 +00:00
parent b779580100
commit 034f60ed24
4 changed files with 37 additions and 11 deletions

View File

@@ -0,0 +1,17 @@
; RUN: llvm-as < %s | llc -march=ppc64 > %t
; RUN: grep __floattitf %t
; RUN: grep __fixunstfti %t
target datalayout = "E-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:32:64-f32:32:32-f64:32:64-v64:64:64-v128:128:128-a0:0:64-f128:64:128"
target triple = "powerpc64-apple-darwin9.2.0"
define ppc_fp128 @foo(i128 %a) nounwind {
entry:
%tmp2829 = uitofp i128 %a to ppc_fp128 ; <i64> [#uses=1]
ret ppc_fp128 %tmp2829
}
define i128 @boo(ppc_fp128 %a) nounwind {
entry:
%tmp2829 = fptoui ppc_fp128 %a to i128 ; <i64> [#uses=1]
ret i128 %tmp2829
}