Displaying 4 results from an estimated 4 matches for "_get5".
Did you mean:
get5
2007 Jun 13
5
[LLVMdev] How to call native functions from bytecode run in JIT?
...s on linux again. Unfortunately it doesn't work
at all (neither using runFunction nor a CallInst). It simply says
function called get5 not known. Calling printf the same way works,
though. On linux the function is exported as "get5" from the
executable while it is called "_get5" on OS X. I could not spot any
other differences.. any thoughts?
greetings,
Jan
On 12. Jun 2007, at 23:08, Jan Rehders wrote:
> Hi,
>
>> Okay. If the function exists in your application's address space
>> already,
>> just name the LLVM function the same name a...
2007 Jun 12
0
[LLVMdev] How to call native functions from bytecode run in JIT?
Hi,
> Okay. If the function exists in your application's address space
> already,
> just name the LLVM function the same name as the native function
> and the
> JIT should find it an do the right thing. This is how it finds
> printf and
> a variety of other things. You don't need to call addGlobalMapping at
> all.
Looking at the output of "nm
2007 Jun 12
3
[LLVMdev] How to call native functions from bytecode run in JIT?
On Tue, 12 Jun 2007, Jan Rehders wrote:
>> Jan, how are you doing this? Are you creating an external LLVM
>> Function object named "get5", then using EE::addGlobalMapping? If
>> 'get5' exists in the address space, why not just let the JIT resolve it
>> (which will then create the stub)?
>
> Yes. I create a Function with matching signature,
2007 Jun 14
0
[LLVMdev] How to call native functions from bytecode run in JIT?
...fortunately it doesn't work
> at all (neither using runFunction nor a CallInst). It simply says
> function called get5 not known. Calling printf the same way works,
> though. On linux the function is exported as "get5" from the
> executable while it is called "_get5" on OS X. I could not spot any
> other differences.. any thoughts?
>
> greetings,
> Jan
>
> On 12. Jun 2007, at 23:08, Jan Rehders wrote:
>
>
>> Hi,
>>
>>
>>> Okay. If the function exists in your application's address space
>...