[llvm-commits] Patch, enable reusing a module pass manager across multiple modules

[Eric Christopher]

On Tue, Nov 13, 2012 at 4:28 PM, Owen Anderson <resistor at mac.com> wrote:

>
> On Nov 13, 2012, at 4:17 PM, Eric Christopher <echristo at gmail.com> wrote:
>
> On Tue, Nov 13, 2012 at 4:05 PM, Pedro Artigas <partigas at apple.com> wrote:
>
>
>> The idea is that we will compile many modules together and save compile
>> time by reusing the module passes data structures.
>>
>>
> Isn't this what we have llvm-link for (or the library equivalent)? This is
> why I asked the question.
>
>
> The intended use case is for a JIT or other long-running compilation
> process, where we will compile many distinct modules that were not all
> available to be linked together at the same time.  If we can reuse the
> PassManager structure across multiple module compilations, we can save the
> compile time cost of setting up the PassManager on all but the first module.
>
>
With the (possible) assumption that all globals/functions/etc are going to
be unique per additional module and not held over. Also how would this
affect things like inlining or cross function optimization? In other words,
are you going to just have the information and not the original module or
are you going to keep a list of modules to the side and the passes remember
in which module the code they care about resides?

-eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20121113/c3625309/attachment.html>