[llvm-commits] [PATCH] [Lit] Use multiprocessing instead of threading

Tobias Grosser tobias at grosser.es
Mon Dec 3 03:59:16 PST 2012


On 11/28/2012 08:32 PM, Eli Bendersky wrote:
> On Fri, Nov 23, 2012 at 12:03 AM, NAKAMURA Takumi<geek4civic at gmail.com>  wrote:
>>
>> Threading is too slow possibly due to GIL.
>> multiprocessing brings 95% of processor usage. I believe it would scale up!
>>
>
> Sorry I missed this patch. I'm +10 for this change, as I believe
> threading is much less useful than multiprocessing in this case for
> true scaling. While we're at it, can we consider requiring Python 2.6?
> It was released more than 4 years ago! I realize some systems may come
> with an older Python out of the box, but can't we require users to
> install Python 2.6 in order to run LLVM tests? Are there any major
> platforms for which this is a problem?

I just pointed out in the other thread, the gcc compile farm has not yet 
python 2.6 installed. Removing python 2.5 support witout changing 
anything on that side, will break the dragonegg builders.

Cheers
Tobi



More information about the llvm-commits mailing list