From: Richard Biener <richard.guenther@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>,gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Build *-match.o as early as possible
Date: Mon, 03 Aug 2015 15:27:00 -0000 [thread overview]
Message-ID: <79836FE5-010B-4AD1-A887-00D9E0DFF637@gmail.com> (raw)
In-Reply-To: <09e1ad477fcb2e9f0878f1e7e27385603c77c827.1438613840.git.segher@kernel.crashing.org>
On August 3, 2015 5:03:05 PM GMT+02:00, Segher Boessenkool <segher@kernel.crashing.org> wrote:
>The two files *-match.o files always finish building last, so if we
>start building them as soon as possible (instead of pretty late) the
>total build time will be less on a parallel build.
>
>Bootstrapped and tested on powerpc64-linux. Is this okay for trunk?
OK.
Richard.
>
>Segher
>
>
>2014-080-3 Segher Boessenkool <segher@kernel.crashing.org>
>
> * Makefile.in (OBJS): Put gimple-match.o and generic-match.o first.
>
>---
> gcc/Makefile.in | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
>diff --git a/gcc/Makefile.in b/gcc/Makefile.in
>index be259e8..683c42a 100644
>--- a/gcc/Makefile.in
>+++ b/gcc/Makefile.in
>@@ -1162,10 +1162,12 @@ C_COMMON_OBJS = c-family/c-common.o
>c-family/c-cppbuiltin.o c-family/c-dump.o \
> c-family/array-notation-common.o c-family/cilk.o c-family/c-ubsan.o
>
> # Language-independent object files.
>-# We put the insn-*.o files first so that a parallel make will build
>-# them sooner, because they are large and otherwise tend to be the
>-# last objects to finish building.
>+# We put the *-match.o and insn-*.o files first so that a parallel
>make
>+# will build them sooner, because they are large and otherwise tend to
>be
>+# the last objects to finish building.
> OBJS = \
>+ gimple-match.o \
>+ generic-match.o \
> insn-attrtab.o \
> insn-automata.o \
> insn-dfatab.o \
>@@ -1260,8 +1262,6 @@ OBJS = \
> gimple-fold.o \
> gimple-laddress.o \
> gimple-low.o \
>- gimple-match.o \
>- generic-match.o \
> gimple-pretty-print.o \
> gimple-ssa-isolate-paths.o \
> gimple-ssa-strength-reduction.o \
prev parent reply other threads:[~2015-08-03 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 15:03 Segher Boessenkool
2015-08-03 15:27 ` Richard Biener [this message]
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=79836FE5-010B-4AD1-A887-00D9E0DFF637@gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
/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).