[LLVMdev] Some basic questions regarding MCJIT and Kaleidoscope sample

[Dibyendu Majumdar]

Hi Lang,

Sincere apologies for the name typo below!

Regards

On 10 February 2015 at 22:46, Dibyendu Majumdar <mobile at majumdar.org.uk> wrote:
> Hi James,
>
> On 10 February 2015 at 22:28, Lang Hames wrote:
>>
>> A single MCJIT instance can notionally manage multiple modules, but there
>> are caveats (which I'm afraid I don't remember off the top of my head) that
>> make it unattractive in practice. I believe most clients opt for something
>> like the ExecutionEngine-per-Module model used in the Kaleidoscope
>> tutorials.
>
> I see. That's good to know.
>
>> As Dave mentioned, I'm also working on some new JIT APIs (Orc) that are
>> intended to be more feature-rich and easier to use than MCJIT. If you would
>> like to try them out and have any questions about how they work please don't
>> hesitate to ask. You'll need to live on the bleeding edge for those though -
>> they're not available on 3.5.
>>
>
> I am at an early stage of development so I can use Orc provided there
> is some assurance that this will be mainstream in future. Else I can
> use the MCJIT replacement that uses Orc. If I wanted to do this should
> I clone the latest code from github?
>
> In any case I am abstracting the creation and management of engines,
> modules etc in my code so that I can change this in future if
> necessary.
>
> Thanks and Regards
>
> Dibyendu