search for: returntype

...ound: when calling a function residing in a different module (context2) from a module (context1), we first need to introduce a function declaration of the function with empty body. However, in order to do so, we need the function type. pFuncInContext2->getType gives us the type in context2. The returnType or argument type might refer to some types yet only defined in context2 (e.g. special structs). In order to get the functin declaration right, I would need to find out if we have in context 1every necessary type referred to by the function (in context2) and introduce it if not. Is there an elegan...

...mory, and get pointer to first function pointer %theKernel = malloc %kernel %FirstFunctionPTR = getelementptr %kernel* %theKernel, long 0, ubyte 0 ;Load code %myNewFunction = %getPointerToGlobal(%dynamically_compiled_function_code) ; Write memory address of myNewFunction() into kernel struct store RETURNTYPE (PARAMTYPE*)* %myNewFunction, RETURNTYPE (PARAMTYPE*)** %FirstFunctionPTR ;Any code using first function element in %kernel is now_ ;using dynamically updated function!? ret int 0 } %----------- The questionmark is at this pseudocode row: %myNewFunction = %getPointerToGlobal(%dynamically_compil...

I don't know how to do that. Rather new to LLVM. The functions that get stripped out are native C++ functions that I'm registering in my execution engine by doing: // Create a function type object for the function llvm::FunctionType* pFuncType = llvm::FunctionType::get(returnType, argTypes, false); // Create a function object with external linkage and the specified function type llvm::Function* pFuncObj = llvm::Function::Create( pFuncType, llvm::Function::ExternalLinkage, name, s_pModule ); // Add a global mapping in the execut...

...rnal(printDeferredWarnings()) } invisible(structure(msg, class = "try-error", condition = e))}) 6: try(am.inv(a = g11), silent = TRUE) 7: amsweep(thetareal, c(FALSE, o[ss, ])) 8: emfred(x, thetaold, indx$o, indx$m, indx$ivector, indx$icap, indx$AMr1, indx$AMr2, AM1stln = AM1stln, returntype = "theta", priors = priors, empri = empri, collect = collect) 9: emarch(x.stacked$x, p2s = p2s, thetaold = NULL, tolerance = tolerance, startvals = startvals, x.stacked$priors, empri = empri, frontend = frontend, collect = collect, autopri = prepped$autopri, emburn = emburn) 10:...

Nyx wrote: > The linkage type is set to external, I have little code snippet I use to > register those native functions in the first post of this topic. The global > DCE pass deletes the unused native functions when run. I commented it out > for now... Can you make this happen by writing a custom .ll to demonstrate the problem? For example: $ cat gdce.ll define i32 @foo() {

On 29 nov 2010 03:47 "Xu Zhongxing" <xuzhongxing at gmail.com> wrote: > Hi, > I enjoyed the new coding style in recent patches. Camel case makes it > easy to pick a descriptive name. Starting functions and variables with > lower cases reduces chances to conflict with a type name. On the other hand, having names that only differ in the case of a single character, is not

...nconsistency both within LangRef and between LangRef and the implementation regarding what is an allowed return type. LangRef says: "The return type of a function type is a first class type or a void type." <http://llvm.org/docs/LangRef.html#id14> and also, contrarily, "<returntype>‘ is any type except label." <http://llvm.org/docs/LangRef.html#id15> On the other hand, the actual implementation of FunctionType::isValidReturnType opines that: bool FunctionType::isValidReturnType(Type *RetTy) { return !RetTy->isFunctionTy() && !RetTy->isLabelTy()...

Hi, I''m connecting to a cf web service.... <cfcomponent> <cffunction name="myname" returntype="string" access="remote"> <cfreturn "fred" > </cffunction> </cfcomponent> using require ''soap/wsdlDriver'' wsdlfile = "http://localhost/docsearch/mainsearch.cfc?wsdl" factory = SOAP::WSDLDriverFactory.new(wsdlfile)...

Okay after translating the headers to Delphi, i found more inconsistencies: > LLVMTypeRef LLVMFunctionType(LLVMTypeRef ReturnType, > LLVMTypeRef *ParamTypes, unsigned ParamCount, > LLVMBool IsVarArg); > In this case it is the other way around. 0 means False and anything else means true :/ (so it acts more like a "traditional" bool) 2016-09-12 11:17...

...%theKernel = malloc %kernel %FirstFunctionPTR = getelementptr %kernel* %theKernel, long 0, ubyte 0 ;Load code %myNewFunction = %getPointerToGlobal(%dynamically_compiled_function_code) ; Write memory address of myNewFunction() into kernel struct store RETURNTYPE (PARAMTYPE*)* %myNewFunction, RETURNTYPE (PARAMTYPE*)** %FirstFunctionPTR ;Any code using first function element in %kernel is now_ ;using dynamically updated function!? ret int 0 } %----------------------------------------------------- The questionmark is at this pseudo...

Of course, this is normal for C-APIs. But maybe change the name to LLVMResult to propagate the real use? I am not arguing about the results themself. They are standard. But the name is missguiding. As long as it's consistent i know that i have to write an extra record operator in Delphi to reflect this. 2016-09-12 11:11 GMT+02:00 David Chisnall <David.Chisnall at cl.cam.ac.uk>: > On

On 5 September 2010 19:32, Talin <viridia at gmail.com> wrote: > I've carefully studied the source code of CGDebugInfo in clang as a working > example. One puzzlement is that there's a discrepancy between what the > "source level debugging with LLVM" docs say and what clang does: According > to the docs, DW_TAG_formal_parameter is used to specify a formal

...false /* isOptimized */, f); DASSERT(sp.Verify()); } return sp; } And here's the code that generates function type descriptors: DICompositeType CodeGenerator::genDIFunctionType(const FunctionType * type) { DIDescriptorArray args; args.push_back(genDIType(type->returnType())); if (type->selfParam() != NULL) { const ParameterDefn * param = type->selfParam(); // genDIParameterType() calls genDIType and then makes it a pointer // if the underlying type is a reference type. args.push_back(genDIParameterType(param->type())); } const Param...

I'm implementing a JIT and getting some strange crashes. I'm unsure exactly what's causing them, but it seems to occur when I call the getReturnType() method on some LLVM function objects. More precisely, I'm registering some native C++ functions as LLVM functions through the addGlobalMapping method of an execution engine object. I then keep a pointer to those LLVM function objects, which I use later on to create call instructions to those...

I hate to be a nag, but after several days of working on this I am still utterly stumped. Let me recap the situation as it currently stands: I'm trying to write code that generates DWARF debugging information for my compiler using DIFactory and friends. Unfortunately the information I am generating appears to be invalid, but I can't figure out the cause. Based on the advice in the

Hi, I enjoyed the new coding style in recent patches. Camel case makes it easy to pick a descriptive name. Starting functions and variables with lower cases reduces chances to conflict with a type name. 2010/11/23 Zhanyong Wan (λx.x x) <wan at google.com> > On Mon, Nov 22, 2010 at 11:41 PM, Zhanyong Wan (λx.x x) <wan at google.com> > wrote: > > +llvmdev > > >

...nValue(\"<undefined/>\"); }"; + } else { + request += "\"<undefined/>\"; }"; + } + var result = flash.external.ExternalInterface._evalJS (request); + if (result == null) { + request = "<invoke name=\"" + name + "\" returntype=\"xml\">" + flash.external.ExternalInterface._argumentsToXML (arguments) + "</invoke>"; + result = flash.external.ExternalInterface._callOut (request); + } + if (result == null) + return null; + + var xml = new XML (); + xml.ignoreWhite = true; + xml.par...