Displaying 6 results from an estimated 6 matches for "llvm_empty_ty".
2014 Feb 26
2
[LLVMdev] How to 'define and use' a LOOP intrinsic that takes "iteration count" and the "label" to jump to ?
I have defined the intrinsic as
* def int_loop: Intrinsic<[],[llvm_i8_ty, llvm_empty_ty],[]>;*
and also got the Codegen backend support in Instructioninfo.td file.
Then created a .ll file to test it.
The .ll file is like this
*declare void @llvm.loop(i8, label)define void @fn() nounwind readnone
{entry: ..... ..... call void @llvm.loop(i8 10, label %entry) ret
void}...
2008 May 07
2
[LLVMdev] Creation of Intrinsics with Pointer Return Types
...ll of the pointer return type instructions.<br><br>I tried using the types such as:<br><br>def llvm_vararg_ty : LLVMType<isVoid>; // this means vararg here<br>def llvm_iPTR_ty : LLVMType<iPTR><br>def llvm_descriptor_ty : LLVMPointerType<llvm_empty_ty>; <br>and adding types<br>def llvm_ptriAny_ty : LLVMPointerType<llvm_anyint_ty>; <br>def llvm_ptrfAny_ty : LLVMPointerType<llvm_anyfloat_ty>;<br><br>but in vain. <br>I would
be happy to know the type or types required for hand...
2008 May 07
0
[LLVMdev] Creation of Intrinsics with Pointer Return Types
...I am not able to handle all of the pointer return type instructions.
>
> I tried using the types such as:
>
> def llvm_vararg_ty : LLVMType<isVoid>; // this means vararg here
> def llvm_iPTR_ty : LLVMType<iPTR>
> def llvm_descriptor_ty : LLVMPointerType<llvm_empty_ty>;
> and adding types
> def llvm_ptriAny_ty : LLVMPointerType<llvm_anyint_ty>;
> def llvm_ptrfAny_ty : LLVMPointerType<llvm_anyfloat_ty>;
>
> but in vain.
> I would be happy to know the type or types required for handling a
> pointer return type for an LL...
2007 Feb 05
0
[LLVMdev] automatically generating intrinsic declarations
On Mon, 5 Feb 2007, Dan Gohman wrote:
> LLVM knows what all the types of the intrinsic functions are; I thought,
> why are users (including llvm-gcc...) required to duplicate all this
> information in order to use them? I mean in order to call
> getOrInsertFunction to get declarations for them.
That is an excellent question! :) In the bad old days, we used to allow
intrinsics
2007 Feb 06
1
[LLVMdev] automatically generating intrinsic declarations
...ype::PointerTyID">; // i8**
-def llvm_descriptor_ty : LLVMType<iPTR, "Type::PointerTyID">; // global*
+def llvm_ptr_ty : LLVMPointerType<llvm_i8_ty>; // i8*
+def llvm_ptrptr_ty : LLVMPointerType<llvm_ptr_ty>; // i8**
+def llvm_empty_ty : LLVMEmptyStructType; // { }
+def llvm_descriptor_ty : LLVMPointerType<llvm_empty_ty>; // { }*
def llvm_v16i8_ty : LLVMPackedType<v16i8,16, llvm_i8_ty>; // 16 x i8
def llvm_v8i16_ty : LLVMPackedType<v8i16, 8, llvm_i16_ty>; //...
2007 Feb 05
2
[LLVMdev] automatically generating intrinsic declarations
LLVM knows what all the types of the intrinsic functions are; I thought,
why are users (including llvm-gcc...) required to duplicate all this
information in order to use them? I mean in order to call getOrInsertFunction
to get declarations for them.
So I wrote this patch, which allows all this code to be generated
automatically. Is this a good approach?
Dan
--
Dan Gohman, Cray Inc. <djg at