Displaying 6 results from an estimated 6 matches for "jittargetaddress".
2019 Jun 27
2
Questions about moving from MCJIT to Orc JIT
...Bjoern,
CC'ing Lang hames
For questions,
1. In short yes, you can replace the memory manager, default one provided
is section memory manager.
2. If you mean by " address of already compiled code", yes you can do that.
Like this
JITDylib.define(absoluteSymbols, ( Your_own_symbol ,
JITTargetAddress(Address of function))), now ORC can resolve all the
references to Your_own_symbol to the provided the Address.
3. Yes, all the class/function with legacy prefix will be removed in
subsequent releases.
4. Could please provide some more context on this? Like it's usage model,
what goal you are...
2017 Apr 19
2
RPC on LLVM IR: any example programs for this?
Hi Lang,
Thanks for your reply! It seems that the code of ORC has been changed a lot
these months. Actually what I wanted to see then was quite simple, Let's
say we have two modules M1.bc and M2.bc, and in M1 we want to call function
foo(defined in M2.bc)with the function type
int foo(float, char*){...}
what basic steps do I need to do to make M1.bc call foo remotely?
BTW, does the
2019 Jun 27
2
Questions about moving from MCJIT to Orc JIT
...hort yes, you can replace the memory manager, default one provided
> is section memory manager.
>
>
>
> 2. If you mean by " address of already compiled code", yes you can do
> that.
>
> Like this
>
> JITDylib.define(absoluteSymbols, ( Your_own_symbol ,
> JITTargetAddress(Address of function))), now ORC can resolve all the
> references to Your_own_symbol to the provided the Address.
>
>
>
> 3. Yes, all the class/function with legacy prefix will be removed in
> subsequent releases.
>
>
>
> 4. Could please provide some more context on thi...
2020 Sep 14
2
ORC JIT Weekly #21 -- OrcV1 removal, Removable code, and Remote TargetProcessControl
Hi All,
Everything is landing all at once, just not in the mainline... yet.
As discussed in
http://lists.llvm.org/pipermail/llvm-dev/2020-September/144885.html: OrcV1
will be removed very soon. I have posted a branch with the removal,
"orcv1-removal", in my llvm fork at https://github.com/lhames/llvm-project.
In addition to removing OrcV1, the orcv1-removal branch also contains a
2019 Jun 19
2
Questions about moving from MCJIT to Orc JIT
Hello LLVM-Mailing list,
in the past I was using the MCJIT (if I understand it correctly) to load IR modules, compile them and execute them. The speciality of this JIT was, that it was writing the compiled code into a shared memory - for a different process to execute them. For that task the JIT used a 'custom' memory manager, memory mapping and also resolved undefined references itself.
2017 May 07
2
[cfe-dev] JIT doens't resolve address - Resolve obj-Addresses?
Hi Bjoern,
CCing cfg-dev (since that's where the conversation started) and llvm-dev
(since it's relevant there).
Do you know if there is a way to obtain the fully resolved obj-code? I
> wanted to load the functions into a shared memory, but how? The only thing
> I receive is a function pointer, but I don't know how large the function
> 'behind' is. Even a call to