search for: getpointertofunctioneag

Displaying 7 results from an estimated 7 matches for "getpointertofunctioneag".

2009 Oct 30
2
[LLVMdev] Should LLVM JIT default to lazy or non-lazy?
...interToFunction{Eager, Lazy} functions when the >> getPointerToFunction is called by the JIT, not the user. For example, when >> Function F calls Function G and the JIT needs an address for G (either a >> callback or the function address), how will it know if it must call >> getPointerToFunctionEager or getPointerToFunctionLazy? Do you plan on >> continuing having a flag that enables/disables lazy compilation and poll >> this flag on each function call? How is that different than the existing >> system? >> > > Semantically, I'll thread the flag through a...
2009 Oct 29
3
[LLVMdev] Should LLVM JIT default to lazy or non-lazy?
...w you would implement the getPointerToFunction{Eager, Lazy} functions when the getPointerToFunction is called by the JIT, not the user. For example, when Function F calls Function G and the JIT needs an address for G (either a callback or the function address), how will it know if it must call getPointerToFunctionEager or getPointerToFunctionLazy? Do you plan on continuing having a flag that enables/disables lazy compilation and poll this flag on each function call? How is that different than the existing system? Thanks, Nicolas > Thanks all for the decision! > > On Thu, Oct 29, 2009 at 11:03 AM,...
2009 Nov 01
1
[LLVMdev] Should LLVM JIT default to lazy or non-lazy?
...ctions when the >>>> getPointerToFunction is called by the JIT, not the user. For example, when >>>> Function F calls Function G and the JIT needs an address for G (either a >>>> callback or the function address), how will it know if it must call >>>> getPointerToFunctionEager or getPointerToFunctionLazy? Do you plan on >>>> continuing having a flag that enables/disables lazy compilation and poll >>>> this flag on each function call? How is that different than the existing >>>> system? >>>> >>>> >&...
2009 Nov 01
0
[LLVMdev] Should LLVM JIT default to lazy or non-lazy?
...Eager, Lazy} functions when the >>> getPointerToFunction is called by the JIT, not the user. For example, when >>> Function F calls Function G and the JIT needs an address for G (either a >>> callback or the function address), how will it know if it must call >>> getPointerToFunctionEager or getPointerToFunctionLazy? Do you plan on >>> continuing having a flag that enables/disables lazy compilation and poll >>> this flag on each function call? How is that different than the existing >>> system? >>> >> >> Semantically, I'll thread...
2009 Oct 29
0
[LLVMdev] Should LLVM JIT default to lazy or non-lazy?
...lement the getPointerToFunction{Eager, Lazy} functions when the > getPointerToFunction is called by the JIT, not the user. For example, when > Function F calls Function G and the JIT needs an address for G (either a > callback or the function address), how will it know if it must call > getPointerToFunctionEager or getPointerToFunctionLazy? Do you plan on > continuing having a flag that enables/disables lazy compilation and poll > this flag on each function call? How is that different than the existing > system? Semantically, I'll thread the flag through all the calls that may eventually ne...
2009 Oct 29
0
[LLVMdev] Should LLVM JIT default to lazy or non-lazy?
Cool, I'll start implementing it. Thanks all for the decision! On Thu, Oct 29, 2009 at 11:03 AM, Evan Cheng <evan.cheng at apple.com> wrote: > I have no objection to Chris' proposal. > > Evan > > On Oct 29, 2009, at 9:45 AM, Jeffrey Yasskin wrote: > >> Are you objecting to Chris's proposal? I was waiting to implement it >> until you replied so I
2009 Oct 29
3
[LLVMdev] Should LLVM JIT default to lazy or non-lazy?
I have no objection to Chris' proposal. Evan On Oct 29, 2009, at 9:45 AM, Jeffrey Yasskin wrote: > Are you objecting to Chris's proposal? I was waiting to implement it > until you replied so I wouldn't have to implement two things. I > disagree with a lot of what you wrote below, but it's not worth > arguing about if there's a compromise we can both live with.