search for: performtailcallopt

I'm just trying to test HLVM with the latest SVN of LLVM and discovered that llvm::PerformTailCallOpt has disappeared from the code but it is still referred to from LangRef.html. Where did it go? -- Dr Jon Harrop, Flying Frog Consultancy Ltd. http://www.ffconsultancy.com/?e

On Feb 18, 2010, at 2:12 AM, Jon Harrop wrote: > > I'm just trying to test HLVM with the latest SVN of LLVM and discovered that > llvm::PerformTailCallOpt has disappeared from the code but it is still > referred to from LangRef.html. > > Where did it go? It got renamed to GuaranteedTailCallOpt, to better reflect what it actually represents. --Owen -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p...

How do you get a tail call using the OCaml's LLVM API? -- Dr Jon Harrop, Flying Frog Consultancy Ltd. http://www.ffconsultancy.com/?e

Evan Cheng wrote: > As far as I can tell only PPC and X86 targets are supporting this option. Does anyone actually using it? I'd prefer to just remove it to clean up the implementation if no one has any objections. Don't know whether that is the same, but my Pure compiler sets llvm::PerformTailCallOpt. Pure needs TCO because it doesn't have any built-in looping constructs. In fact, most functional language implementations will rely on TCO. If you can make this work reliably on all supported platforms without needing special flags, that would be welcome. Otherwise please keep the flag. (That...

.... The calling convention of the function needs to be CallingConv::Fast (currently only fastcc calls are optimized) and the call has to be in tail position of course. To enable tail call optimization in an embedded vm i guess you would include llvm/Target/TargetOptions.h and set the static variable PerformTailCallOpt to true. Take this with a grain of salt or two since i have never done it ;) but i guess that setting those globals is what cl::ParseCommandLineOptions does in lli/llc.cpp. regards arnold > Quick question, how do you enable tail calls for the JIT when using > the API, not an external app;...

Hi everyone, vmkit requires to know the size of a jitted method before emitting the method. This allows to allocate the correct size for the method. The attached patch creates this functionality when the flag SizedMemoryCode is on. In order to implement this functionality, i had to virtualize some MachineCodeEmitter functions. Is it OK to commit the patch? Thanks, Nicolas --------------

...ted. >> extern bool ExceptionHandling; >> >> + /// SizedMemoryCode - This flags indicates that memory for code >> is allocated by >> + /// an external allocator which requires the size to allocate >> + extern bool SizedMemoryCode; >> + >> /// PerformTailCallOpt - This flag is enabled when -tailcallopt is >> specified >> /// on the commandline. When the flag is on, the target will >> perform tail call >> /// optimization (pop the caller's stack) providing it supports it. >> Index: include/llvm/CodeGen/SizeEmitter.h...

...4,6 +74,10 @@ > /// be emitted. > extern bool ExceptionHandling; > > + /// SizedMemoryCode - This flags indicates that memory for code > is allocated by > + /// an external allocator which requires the size to allocate > + extern bool SizedMemoryCode; > + > /// PerformTailCallOpt - This flag is enabled when -tailcallopt is > specified > /// on the commandline. When the flag is on, the target will > perform tail call > /// optimization (pop the caller's stack) providing it supports it. > Index: include/llvm/CodeGen/SizeEmitter.h > ==============...

...ol ExceptionHandling; >>> >>> + /// SizedMemoryCode - This flags indicates that memory for code >>> is allocated by >>> + /// an external allocator which requires the size to allocate >>> + extern bool SizedMemoryCode; >>> + >>> /// PerformTailCallOpt - This flag is enabled when -tailcallopt is >>> specified >>> /// on the commandline. When the flag is on, the target will >>> perform tail call >>> /// optimization (pop the caller's stack) providing it supports it. >>> Index: include/llvm/CodeGen...

...> Take this with a grain of salt or two since i have never done it ;) > but i guess that setting those globals is what > cl::ParseCommandLineOptions does in lli/llc.cpp. I can confirm that this is actually how it works (fastcc on the function + setTailCall on the call instruction + llvm::PerformTailCallOpt = true). I might add that of course you also have to make sure that the tail call is immediately before a ret instruction. :) Note that it also depends on the JIT for the target architecture whether this is actually supported. I verified that this does work on x86, -64. Not sure about the stat...

...>> As far as I can tell only PPC and X86 targets are supporting this option. Does anyone actually using it? I'd prefer to just remove it to clean up the implementation if no one has any objections. > > Don't know whether that is the same, but my Pure compiler sets > llvm::PerformTailCallOpt. Pure needs TCO because it doesn't have any > built-in looping constructs. In fact, most functional language > implementations will rely on TCO. If you can make this work reliably on > all supported platforms without needing special flags, that would be > welcome. Otherwise please k...

...t;>> >>>> + /// SizedMemoryCode - This flags indicates that memory for code >>>> is allocated by >>>> + /// an external allocator which requires the size to allocate >>>> + extern bool SizedMemoryCode; >>>> + >>>> /// PerformTailCallOpt - This flag is enabled when -tailcallopt is >>>> specified >>>> /// on the commandline. When the flag is on, the target will >>>> perform tail call >>>> /// optimization (pop the caller's stack) providing it supports it. >>>> Index:...

Hi all, I've added tail call optimization to x86. This is different from what -tailcallopt does, which forces fastcc function to be tail callable. My changes detect opportunities to do tail call without having to change the ABI. I've looked at the codegen of -tailcallopt and it doesn't look all that good. Running it as a llcbeta option shows it significantly pessimize code in most

On Thu, Sep 11, 2008 at 4:31 PM, Arnold Schwaighofer <arnold.schwaighofer at gmail.com> wrote: > Tail calls through function pointers should work.If not please send a testcase. > > I just added the two examples from the bug (1392) that calls for true > tail call support. They work on my machine (-tailcallopt needs to be > enabled) ;) > > That would be commit 56127. >

...dMemoryCode - This flags indicates that memory for code >>>>>> is allocated by >>>>>> + /// an external allocator which requires the size to allocate >>>>>> + extern bool SizedMemoryCode; >>>>>> + >>>>>> /// PerformTailCallOpt - This flag is enabled when -tailcallopt is >>>>>> specified >>>>>> /// on the commandline. When the flag is on, the target will >>>>>> perform tail call >>>>>> /// optimization (pop the caller's stack) providing it support...

...>>>>>>> code >>>>>>> is allocated by >>>>>>> + /// an external allocator which requires the size to allocate >>>>>>> + extern bool SizedMemoryCode; >>>>>>> + >>>>>>> /// PerformTailCallOpt - This flag is enabled when - >>>>>>> tailcallopt is >>>>>>> specified >>>>>>> /// on the commandline. When the flag is on, the target will >>>>>>> perform tail call >>>>>>> /// optimization (p...

...cations to each operand. + SmallVector<CCValAssign, 16> ArgLocs; + CCState CCInfo(CC, isVarArg, getTargetMachine(), ArgLocs); + CCInfo.AnalyzeCallOperands(Op.Val, CC_X86_32_TailCall); + if (isTailCall && + IsEligibleForTailCallElimination(Op, DAG,CC, Callee) && + PerformTailCallOpt) { IsEligibleForTailCallElimination() should be a target hook. This way TargetLowering::LowerCallTo() can determine whether a call is eligible for tail call elimination and insert the current ISD::CALL node. X86TargetLowering::LowerX86_32FastCCCallTo() will not have to handle non-tail cal...

...>> + /// SizedMemoryCode - This flags indicates that memory for code >>>>> is allocated by >>>>> + /// an external allocator which requires the size to allocate >>>>> + extern bool SizedMemoryCode; >>>>> + >>>>> /// PerformTailCallOpt - This flag is enabled when -tailcallopt is >>>>> specified >>>>> /// on the commandline. When the flag is on, the target will >>>>> perform tail call >>>>> /// optimization (pop the caller's stack) providing it supports >>>...

...t;>> code >>>>>>>> is allocated by >>>>>>>> + /// an external allocator which requires the size to allocate >>>>>>>> + extern bool SizedMemoryCode; >>>>>>>> + >>>>>>>> /// PerformTailCallOpt - This flag is enabled when - >>>>>>>> tailcallopt is >>>>>>>> specified >>>>>>>> /// on the commandline. When the flag is on, the target will >>>>>>>> perform tail call >>>>>>>>...

Tail calls through function pointers should work.If not please send a testcase. I just added the two examples from the bug (1392) that calls for true tail call support. They work on my machine (-tailcallopt needs to be enabled) ;) That would be commit 56127. regards On Thu, Sep 11, 2008 at 11:21 PM, Evan Cheng <evan.cheng at apple.com> wrote: > Arnold implemented tail call. We