This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Parallelize the compilation using Threads
- From: Jeff Law <law at redhat dot com>
- To: Richard Biener <richard dot guenther at gmail dot com>, Giuliano Augusto Faulin Belinassi <giuliano dot belinassi at usp dot br>
- Cc: GCC Development <gcc at gcc dot gnu dot org>, kernel-usp at googlegroups dot com, gold at ime dot usp dot br, alfredo dot goldman at gmail dot com
- Date: Thu, 15 Nov 2018 09:56:09 -0700
- Subject: Re: Parallelize the compilation using Threads
- References: <CAEFO=4A0DJVDYze7P5mCOzDjGpJC1Y180nP_UmXxwqduy87=bA@mail.gmail.com> <CAFiYyc1kogmJ_5suHg+7fDaNjrYZnGjNGq4dew5uvc+w6-_BKQ@mail.gmail.com>
On 11/15/18 3:29 AM, Richard Biener wrote:
>
>> 2. Did I correctly understand the goal of the parallelization? Can
>> anyone provide extra details to me?
>
> You may want to search the mailing list archives since we had a
> student application (later revoked) for the task with some discussion.
>
> In my view (I proposed the thing) the most interesting parts are
> getting GCCs global state documented and reduced. The parallelization
> itself is an interesting experiment but whether there will be any
> substantial improvement for builds that can already benefit from make
> parallelism remains a question.
Agreed. Driving down the amount of global state is good in and of
itself. It's also a prerequisite for parallelizing GCC itself using
threads.
I suspect driving down global state probably isn't that interesting for
a master's thesis though :-)
jeff