Displaying 6 results from an estimated 6 matches for "nativefunction".
2009 Mar 27
4
[LLVMdev] Connecting JITted code to gdb
...ow project,
and I'm having a bit of trouble getting gdb to step into functions
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=...
2009 Mar 27
0
[LLVMdev] Connecting JITted code to gdb
...le getting gdb to step into functions
> 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:
>
> Breakpoin...
2006 Sep 19
3
[LLVMdev] failed assertion in PPCJITInfo.cpp when calling native function
...ent address, closer to the native function.
When I run the same program (the very same binary) outside of gdb, the memory
for the JIT code is too far off.
When I run my program outside of gdb, the native function is more than 2^23
words from the JIT code, which is too far for a PC relative jump:
nativeFunction address 0x63b4d4c
JIT memory base 0x9008000 (allocated in JITMemoryManager constructor)
/Users/andreas/build/llvm-1.8/debugBuild/../llvm/lib/Target/PowerPC/PPCJITInfo.cpp:206:
failed assertion `ResultPtr >= -(1 << 23) && ResultPtr < (1 << 23) &&
"Relocation...
2006 Sep 16
0
[LLVMdev] failed assertion in PPCJITInfo.cpp when calling native function
...plete, minimal program that reproduces the error and the
call-stack. However, the relevant part of the program looks as follows. Am I
doing something wrong, or is this a bug in the JIT?
Regards,
Andreas
// the "native" function that the llvm code should call
extern "C" { void nativeFunction() {} }
int main() {
Module* module = new Module("module");
FunctionType* funType =
FunctionType::get(Type::VoidTy, vector<const Type*>(), false);
Function* nativeFunction = new Function(
funType, GlobalValue::ExternalLinkage, "native", module);
Function*...
2009 Mar 27
2
[LLVMdev] Connecting JITted code to gdb
...; 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...
2019 Aug 16
0
Wine release 4.14
...toString implementation.
jscript: Move function destructor implementation into vtbl.
jscript: Move function call implementation into vtbl.
jscript: Move value_proc to BuiltinFunction struct.
jscript: Introduce InterpretedFunction struct.
jscript: Move function name to NativeFunction.
jscript: Implement Function.prototype.bind.
mshtml: Add Function.prototype.bind tests.
Józef Kucia (2):
wined3d: Fix memory leak in wined3d_swapchain_state_create() (Coverity).
winevulkan: Pull in bitmask dependencies for function parameters.
Kai Krakow (1):
wined3d...