[PATCH] [Review Request] Function-based parallel LLVM backend code generation

Eric Christopher echristo at gmail.com
Tue Oct 8 12:49:09 PDT 2013


Not much of a point in doing it in this case. The goal is to speed up code
generation of a large linked module, think LTO rather than normal linking.
On Oct 8, 2013 11:33 AM, "Renato Golin" <renato.golin at linaro.org> wrote:

> On 8 October 2013 19:28, Hal Finkel <hfinkel at anl.gov> wrote:
>
>> I think that, in the common case, the 'root' of the compilation tree is
>> where LTO optimizations are done (when building the final executable or
>> shared library), and at that point, there is limited make-level parallelism
>> available. There are obviously counter examples (like our test suite), but
>> so long as we provide an easy way to turn off the extra threading, I think
>> that it will help most people.
>>
>
> In that case, specifically, it probably helps.
>
> What about a Debug build of LLVM, that (when using gnu ld), can take
> several GB or RAM and trash the disk. Would the extra work create more
> copies of the tree, or more disk read, or anything?
>
> cheers,
> --renato
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20131008/d04e0539/attachment.html>


More information about the llvm-commits mailing list