Displaying 3 results from an estimated 3 matches for "mylazyfunctioncreator".
Did you mean:
lazyfunctioncreator
2012 Nov 25
2
[LLVMdev] MCJIT and Lazy Function Creators
Out of curiosity, I'm replacing the JIT with MCJIT on my compiler. As
all "external" functions are provided by the language's FFI mechanism,
it does
MyExecutionEngine->DisableSymbolSearching();
MyExecutionEngine->InstallLazyFunctionCreator(&MyLazyFunctionCreator);
which works fine with the JIT. However, MCJIT insists on resolving
unknown symbols by searching them outdoors and seems oblivious of the
existence of MyLazyFunctionCreator.
Is this a bug?
Is there a workaround, other than subclassing JITMemoryManager and
implementing my own getPointerToNamedFu...
2012 Nov 27
0
[LLVMdev] MCJIT and Lazy Function Creators
...> Out of curiosity, I'm replacing the JIT with MCJIT on my compiler. As
> all "external" functions are provided by the language's FFI mechanism,
> it does
>
> MyExecutionEngine->DisableSymbolSearching();
> MyExecutionEngine->InstallLazyFunctionCreator(&MyLazyFunctionCreator);
>
> which works fine with the JIT. However, MCJIT insists on resolving
> unknown symbols by searching them outdoors and seems oblivious of the
> existence of MyLazyFunctionCreator.
>
> Is this a bug?
>
> Is there a workaround, other than subclassing JITMemoryManager and
&g...
2012 Nov 27
2
[LLVMdev] MCJIT and Lazy Function Creators
...gt; Out of curiosity, I'm replacing the JIT with MCJIT on my compiler. As
> all "external" functions are provided by the language's FFI mechanism,
> it does
>
> MyExecutionEngine->DisableSymbolSearching();
> MyExecutionEngine->InstallLazyFunctionCreator(&MyLazyFunctionCreator);
>
> which works fine with the JIT. However, MCJIT insists on resolving
> unknown symbols by searching them outdoors and seems oblivious of the
> existence of MyLazyFunctionCreator.
>
> Is this a bug?
>
> Is there a workaround, other than subclassing JITMemoryManager and...