From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: giuliano.belinassi@usp.br, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
kernel-usp@googlegroups.com, gold@ime.usp.br,
alfredo.goldman@gmail.com
Subject: Re: Parallelize the compilation using Threads
Date: Thu, 15 Nov 2018 15:54:00 -0000 [thread overview]
Message-ID: <CAH6eHdS+tE3HvkGoqU4oURCnD8cLyoLATokUs=-aCQCPzK3wQg@mail.gmail.com> (raw)
In-Reply-To: <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.
next prev parent reply other threads:[~2018-11-15 11:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 10:12 Giuliano Augusto Faulin Belinassi
2018-11-15 11:44 ` Richard Biener
2018-11-15 15:54 ` Jonathan Wakely [this message]
2018-11-15 18:07 ` Jeff Law
2018-11-15 18:36 ` Szabolcs Nagy
2018-11-16 14:25 ` Martin Jambor
2018-11-16 22:40 ` Giuliano Augusto Faulin Belinassi
2018-11-19 14:36 ` Richard Biener
2018-12-12 15:46 ` Giuliano Augusto Faulin Belinassi
2018-12-13 8:12 ` Bin.Cheng
2018-12-14 14:15 ` Giuliano Belinassi
2018-12-17 11:06 ` Richard Biener
2019-01-14 11:42 ` Giuliano Belinassi
2019-01-14 12:23 ` Richard Biener
2019-01-15 21:45 ` Giuliano Belinassi
2019-01-16 12:44 ` Richard Biener
2019-02-07 14:14 ` Giuliano Belinassi
2019-02-11 21:46 ` Giuliano Belinassi
2019-02-12 14:12 ` Richard Biener
2019-02-16 4:35 ` Oleg Endo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH6eHdS+tE3HvkGoqU4oURCnD8cLyoLATokUs=-aCQCPzK3wQg@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=alfredo.goldman@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=giuliano.belinassi@usp.br \
--cc=gold@ime.usp.br \
--cc=kernel-usp@googlegroups.com \
--cc=richard.guenther@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).