[llvm-dev] Using a function from lib/Target/(any arch)/ in lib/ExecutionEngine/RuntimeDyld/

[Lang Hames via llvm-dev]

Hi Siddharth,

As far as I know this is not currently possible. Current RuntimeDyld
implementations are all self-contained and do not reference code from their
targets.

Having RuntimeDyld depend on code from a custom target seems reasonable
though. It might be better in the long term if we moved all the
target-specific code out of ExecutionEngine and just provided registration
functions so that targets could register their respective RuntimeDyld
implementations with ExecutionEngine. This would be a significant refactor
though, and we'd want to sanity-check its impact on LLVM's library layering.

Cheers,
Lang.


On Thu, Apr 13, 2017 at 5:36 AM, 陳韋任 via llvm-dev <llvm-dev at lists.llvm.org>
wrote:

>   Maybe you can see how other targets under ExecitionEngine/RuntimeDyld/Targets
> do?
>
> HTH,
> chenwj
>
> 2017-04-13 13:36 GMT+08:00 Siddharth Shankar Swain via llvm-dev <
> llvm-dev at lists.llvm.org>:
>
>> Hello LLVMDevs,
>>
>> I have written a .cpp file in lib/Target/(some arch)/ and i want to use
>> one of its function in a file in lib/ExecutionEngine/RuntimeDyld/. So is
>> there any specific way to do that. This may be a general question for any
>> one who writes a .cpp file in Target/(any arch)/ and tries to use it
>> somewhere in ExecitionEngine/RuntimeDyld/. Please guide.
>>
>> Thanks,
>> Siddharth
>>
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>>
>>
>
>
> --
>
> --
> Wei-Ren Chen (陳韋任)
> Homepage: https://people.cs.nctu.edu.tw/~chenwj
>
> _______________________________________________
> 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/20170413/b05735b7/attachment.html>