Displaying 3 results from an estimated 3 matches for "getexecutionengin".
Did you mean:
getexecutionengine
2009 Mar 27
4
[LLVMdev] Connecting JITted code to gdb
...nctions
I've compiled with LLVM's JIT compiler. The attached a_module.ll is
the module I produce from compiling
def foo(r):
for i in r:
pass
I'm JIT-compiling and running foo() with:
typedef PyObject *(*NativeFunction)(PyFrameObject *);
llvm::ExecutionEngine *engine = ...->getExecutionEngine();
NativeFunction native =
(NativeFunction)engine->getPointerToFunction(function);
return native(frame);
However, when I try to step into the call with gdb, I get:
Breakpoint 1, eval_llvm_function (function_obj=0x142f6e0,
frame=0x1350b98) at ../src/Python/ceval.cc:2549
2549 (NativeFunct...
2009 Mar 27
0
[LLVMdev] Connecting JITted code to gdb
...compiler. The attached a_module.ll is
> the module I produce from compiling
>
> def foo(r):
> for i in r:
> pass
>
> I'm JIT-compiling and running foo() with:
>
> typedef PyObject *(*NativeFunction)(PyFrameObject *);
> llvm::ExecutionEngine *engine = ...->getExecutionEngine();
> NativeFunction native =
> (NativeFunction)engine->getPointerToFunction(function);
> return native(frame);
>
> However, when I try to step into the call with gdb, I get:
>
> Breakpoint 1, eval_llvm_function (function_obj=0x142f6e0,
> frame=0x1350b98) at ../src/Py...
2009 Mar 27
2
[LLVMdev] Connecting JITted code to gdb
...e module I produce from compiling
>>
>> def foo(r):
>> for i in r:
>> pass
>>
>> I'm JIT-compiling and running foo() with:
>>
>> typedef PyObject *(*NativeFunction)(PyFrameObject *);
>> llvm::ExecutionEngine *engine = ...->getExecutionEngine();
>> NativeFunction native =
>> (NativeFunction)engine->getPointerToFunction(function);
>> return native(frame);
>>
>> However, when I try to step into the call with gdb, I get:
>>
>> Breakpoint 1, eval_llvm_function (function...