Displaying 4 results from an estimated 4 matches for "foremitfunctionstub".
Did you mean:
forceemitfunctionstub
2010 Feb 17
3
[LLVMdev] Work in progress patch to bug 2606
...p thinks about the approach.
>
> - If the jit is in non-lazy mode, I'm not really fan of the "stub" solution. Is it not possible to use the same mechanism as it already exists : add the function to pending list and emit it after the current functions ? In fact, can you replace forEmitFunctionStub with getLazyFunctionStub ? With a non-lazy jit, I want the first execution of my function to be the same execution speed as the second one. A stub in non-lazy mode doesn't fell natural to me.
So as best as I can determine, the problem with leveraging pending, as used by getLazyFunctionStub(......
2010 Feb 17
0
[LLVMdev] Work in progress patch to bug 2606
...s treated
by a stub (like every calls).
- If the jit is in non-lazy mode, I'm not really fan of the "stub" solution.
Is it not possible to use the same mechanism as it already exists : add the
function to pending list and emit it after the current functions ? In fact,
can you replace forEmitFunctionStub with getLazyFunctionStub ? With a
non-lazy jit, I want the first execution of my function to be the same
execution speed as the second one. A stub in non-lazy mode doesn't fell
natural to me.
- I don't see why functions external to every modules (let's say "printf" ?)
are del...
2010 Feb 17
0
[LLVMdev] Work in progress patch to bug 2606
...t the approach.
>
>>
>> - If the jit is in non-lazy mode, I'm not really fan of the "stub" solution. Is it not possible to use the same mechanism as it already exists : add the function to pending list and emit it after the current functions ? In fact, can you replace forEmitFunctionStub with getLazyFunctionStub ? With a non-lazy jit, I want the first execution of my function to be the same execution speed as the second one. A stub in non-lazy mode doesn't fell natural to me.
>
> So as best as I can determine, the problem with leveraging pending, as used by getLazyFuncti...
2010 Feb 16
2
[LLVMdev] Work in progress patch to bug 2606
The patch I recently attached to bug 2606, reproduced here, is my first attempt to solve this issue
as represented by the attached test cases. To solve the foreign Module GlobalVariable problem,
I modified JIT::getOrEmitGlobalVariable(...) to directly attempt to map a found "external" GlobalVariable.
To solve the foreign Module Function problem, I modified both JIT.{h,cpp} and