Displaying 2 results from an estimated 2 matches for "tceinstrinfo".
Did you mean:
mcinstrinfo
2007 Aug 03
1
[LLVMdev] Adding intrinsic with variable argument list HOWTO.
...i8*, ...)* @llvm.tce.customop( i8* getelementptr
([7 x i8]* @.str, i32 0, i32 0), i32 10 )
tail call void (i8*, ...)* @llvm.tce.customop( i8* getelementptr
([7 x i8]* @.str, i32 0, i32 0), i32 %tmp12 )
declare void @llvm.tce.customop(i8*, ...)
No I need to add code to llvm/lib/Target/TCE/TCEInstrInfo.td, for
recognizing that variable argument intrinsic and I have no idea how it's
done. Right now I'm trying following:
def CustomOpParams : SDTypeProfile<0,2,[]>;
def customop : SDNode<"ISD::INTRINSIC_VOID", CustomOpParams>;
def : Pat<(customop tglobaladd...
2012 Mar 19
1
[LLVMdev] floating point immediate problem
...o a floating point register.
def MOVF32fk : InstTCE<(outs F32Regs:$dst), (ins f32imm:$val),
"$val -> $dst;",
[(set F32Regs:$dst, (f32 imm:$val))]>;
This causes an type contradiction:
/home/hkultala26/src/devel/tce/src/applibs/LLVMBackend/plugin//TCEInstrInfo.td:109:1:
error: In MOVF32fk: Type inference contradiction found, 'f32' needs to
be integer
def MOVF32fk : InstTCE<(outs F32Regs:$dst), (ins f32imm:$val),
why? Why does llvm assume floating point immediate needs to be integer?