search for: functionty

Displaying 4 results from an estimated 4 matches for "functionty".

2013 Apr 16
0
[LLVMdev] Name mangling and getOrInsertFunction
...accepting 3 parameters. I can build the correct FuntionType, but I cannot use the M->getOrInsertFunction, since I cannot get the correct name of the function. Do you have any suggestions on how can I: (i) either retrieve the function name (ii) directly retrieve the function I need, based on its FunctionTy and knowing that the name has a common substring with the other function (or based on the original name it has in the source code). To be more precise, originally, the function is called task and it is overloaded. Therefore, in the LLVM IR one of them becomes @_Z6_task_PFvPvS_S_S_ES1_S_S_S_S_  and...
2008 Mar 15
0
[LLVMdev] improving the ocaml binding's type safety
...enum via classify_type. In order to be useful, I think it will also be necessary to provide a new class of functions, a set of type checking helpers which play the same role as bool T::isa<U>(T*), U* T::cast<U>(T*), and U* T::dyn_cast<U>(T*): (** @see [bool Type::isa<FunctionType>(Type*)] *) val is_function_type : lltype t -> bool (** @see [FunctionType *Type::dyn_cast<FunctionType>(Type*)] @raise Invalid_cast if the conversion is impossible. *) val as_function_type : lltype t -> `FunctionTy t For Value, it will be important to push the ISA routines...
2012 Mar 28
0
[LLVMdev] GSoC 2012 Proposal: Python bindings for LLVM
...*return ctor_LLVMValueRef( LLVMAddFunction (arg1, arg2, arg3));* we finally get the C function that my_module.add_function in the example calls : *LLVMAddFunction*, which is defined in the file *core.h *of LLVM libries. *LLVMValueRef LLVMAddFunction(LLVMModuleRef M, const char *Name, LLVMTypeRef FunctionTy);* -- Best Regards, Baozeng Ding OSTG,NFS,ISCAS -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120328/edbcc73c/attachment.html&g...
2008 Mar 15
4
[LLVMdev] improving the ocaml binding's type safety
I was talking to Gordon on #llvm earlier, and he challenged me with coming up with a way to improve the ocaml binding's type safety. We can't go letting haskell beat us now, can we? I think I got an easy solution with phantom types. For those who don't know what the problem is, the ocaml bindings share one type between whole class branches (like values). This means we need to downcast