This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Parallelize the compilation using Threads
- From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: Richard Guenther <richard dot guenther at gmail dot com>
- Cc: giuliano dot belinassi at usp dot br, "gcc at gcc dot gnu dot org" <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 11:44:36 +0000
- Subject: Re: Parallelize the compilation using Threads
- References: <CAEFO=4A0DJVDYze7P5mCOzDjGpJC1Y180nP_UmXxwqduy87=bA@mail.gmail.com> <CAFiYyc1kogmJ_5suHg+7fDaNjrYZnGjNGq4dew5uvc+w6-_BKQ@mail.gmail.com>
On Thu, 15 Nov 2018 at 10:29, Richard Biener <richard.guenther@gmail.com> wrote:
>
> On Wed, Nov 14, 2018 at 10:47 PM Giuliano Augusto Faulin Belinassi
> <giuliano.belinassi@usp.br> wrote:
> > Additionally, I know that GCC must not
> > change the project layout, but from the software engineering perspective,
> > this may be a bad smell that indicates that the file should be broken
> > into smaller files. Finally, the Makefiles will take care of the
> > parallelization task.
>
> What do you mean by GCC must not change the project layout?
I think this is in response to a comment I made on IRC. Giuliano said
that if a project has a very large file that dominates the total build
time, the file should be split up into smaller pieces. I said "GCC
can't restructure people's code. it can only try to compile it
faster". We weren't referring to code transformations in the compiler
like re-ordering functions, but physically refactoring the source
code.