[llvm-dev] RPC on LLVM IR: any example programs for this?

[Shen Liu via llvm-dev]

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 RPCUtility supports handling pointers now?

Thanks very much!

Best regards,

Shen

On Thu, Apr 13, 2017 at 9:13 PM, Lang Hames via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> Hi Shen,
>
> The best place to look for examples is currently the RPCUtilsTest unit
> test: llvm/unittests/ExecutionEngine/Orc/RPCUtilsTest.cpp
>
> What API do you want to be able to call via RPC? If it's small I can
> probably write up an example for you.
>
> Cheers,
> Lang.
>
>
>
> On Fri, Dec 16, 2016 at 7:37 AM, Shen Liu via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>> Hi everyone,
>>
>> I want to use an LLVM new feature (llvm::orc::remote::RPCBase) to
>> implement a simple RPC framework between two LLVM modules. It seems by
>> this new class we can do serialization/deserialization on LLVM IR type
>> system directly. But I haven't found any helpful stuff on google showing me
>> how to use these RPC APIs. Can anyone give me some hints or example
>> programs showing me how to use these API correctly? Just a simple
>> serialization/deserialization toy demo is OK, Thanks very much!
>>
>> Best regards,
>>
>> Shen
>>
>>
>>
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>>
>>
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170418/57480127/attachment.html>