[llvm-commits] [PATCH] Review request: Lazy compilation for MCJIT

[Malea, Daniel]

Hi,

Yes, that's correct, MCJIT still only supports a single module, and a single compilation of that module. It's still a little brittle, but hopefully that will change.

Dan

-----Original Message-----
From: llvm-commits-bounces at cs.uiuc.edu [mailto:llvm-commits-bounces at cs.uiuc.edu] On Behalf Of Nuno Lopes
Sent: Thursday, August 02, 2012 6:08 PM
To: Kaylor, Andrew; llvm-commits at cs.uiuc.edu
Subject: Re: [llvm-commits] [PATCH] Review request: Lazy compilation for MCJIT

Hi,

Just to confirm: this patch still only allows 1 compilation per engine, right?
I still cannot add a function to a module, compile and execute it, and then add another function to the same module and compile it, right?


Thanks,
Nuno


----- Original Message -----
From: "Kaylor, Andrew" <andrew.kaylor at intel.com>
To: <llvm-commits at cs.uiuc.edu>
Sent: Thursday, August 02, 2012 10:11 PM


Hi everyone,

The attached patch implements lazy compilation for MCJIT.  That is, the 
module isn't JITed until a call is made to request a pointer to a function.

I tried to implement this in such a way as to move towards multiple module 
support.  There are still a few things to be cleaned up in that regard, but 
it seemed best to leave that for a future patch since I intend to refactor 
the memory ownership model somewhat extensively.

I'm not making any effort to respect the 'CompilingLazily' flag, since that 
couldn't be changed before the constructor and so would have no meaning in 
MCJIT.

-Andy 

_______________________________________________
llvm-commits mailing list
llvm-commits at cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits