From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Richard Biener <rguenther@suse.de>
Subject: Re: [PATCH] Generate gimple-match.c and generic-match.c earlier
Date: Fri, 28 May 2021 06:51:13 +0200 [thread overview]
Message-ID: <AM8PR10MB47089F6A21B528C61CB80A13E4229@AM8PR10MB4708.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <AM8PR10MB4708E4C8765686EC627AE24DE4229@AM8PR10MB4708.EURPRD10.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
On 5/28/21 6:42 AM, Bernd Edlinger wrote:
> Hi,
>
> I was wondering, why gimple-match.c and generic-match.c
> are not built early but always last, which slows down parallel
> makes significantly.
>
> The reason seems to be that generated_files does not
> mention gimple-match.c and generic-match.c.
>
> This comment in Makefile.in says it all:
>
Oh, dear, git commit did eliminate the comments
starting with "#"
the mentined comment is
# Dependency information.
# In order for parallel make to really start compiling the expensive
# objects from $(OBJS) as early as possible, build all their
# prerequisites strictly before all objects.
> $(ALL_HOST_OBJS) : | $(generated_files)
>
> So this patch adds gimple-match.c generic-match.c to generated_files.
>
>
> Tested on x86_64-pc-linux-gnu.
> Is it OK for trunk?
>
>
> Thanks
> Bernd.
>
>
> 2021-05-28 Bernd Edlinger <bernd.edlinger@hotmail.de>
>
> * Makefile.in (generated_files): Add gimple-match.c and
> generic-match.c
>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Generate-gimple-match.c-and-generic-match.c-earlier.patch --]
[-- Type: text/x-patch; name="0001-Generate-gimple-match.c-and-generic-match.c-earlier.patch", Size: 1529 bytes --]
From 99eab77ebfaa02ee22263d89eb3ca812cf65263b Mon Sep 17 00:00:00 2001
From: Bernd Edlinger <bernd.edlinger@hotmail.de>
Date: Fri, 28 May 2021 06:27:27 +0200
Subject: [PATCH] Generate gimple-match.c and generic-match.c earlier
I was wondering, why gimple-match.c and generic-match.c
are not built early but always last, which slows down parallel
makes significantly.
The reason seems to be that generated_files does not
mention gimple-match.c and generic-match.c.
This comment in Makefile.in says it all:
"In order for parallel make to really start compiling the expensive
objects from $(OBJS) as early as possible, build all their
prerequisites strictly before all objects."
So this patch adds gimple-match.c generic-match.c to generated_files.
2021-05-28 Bernd Edlinger <bernd.edlinger@hotmail.de>
* Makefile.in (generated_files): Add gimple-match.c and
generic-match.c
---
gcc/Makefile.in | 1 +
1 file changed, 1 insertion(+)
diff --git a/gcc/Makefile.in b/gcc/Makefile.in
index da2ef24..4cb2966 100644
--- a/gcc/Makefile.in
+++ b/gcc/Makefile.in
@@ -2753,6 +2753,7 @@ generated_files = config.h tm.h $(TM_P_H) $(TM_D_H) $(TM_H) multilib.h \
$(ALL_GTFILES_H) gtype-desc.c gtype-desc.h version.h \
options.h target-hooks-def.h insn-opinit.h \
common/common-target-hooks-def.h pass-instances.def \
+ gimple-match.c generic-match.c \
c-family/c-target-hooks-def.h d/d-target-hooks-def.h \
case-cfn-macros.h \
cfn-operators.pd omp-device-properties.h
--
1.9.1
next prev parent reply other threads:[~2021-05-28 4:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 4:42 Bernd Edlinger
2021-05-28 4:51 ` Bernd Edlinger [this message]
2021-05-28 6:41 ` Richard Biener
2021-05-28 6:48 ` Bernd Edlinger
2021-05-28 7:26 ` Andrew Pinski
2021-05-28 7:33 ` Bernd Edlinger
2021-05-28 8:48 ` Jakub Jelinek
2021-05-28 15:33 ` Michael Matz
2021-07-14 12:47 ` Tamar Christina
2021-07-14 13:12 ` Richard Biener
2021-07-14 13:15 ` Richard Biener
2021-07-14 13:19 ` Richard Biener
2021-07-14 13:25 ` Tamar Christina
2021-07-14 15:56 ` Bernd Edlinger
2021-07-14 16:47 ` Tamar Christina
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=AM8PR10MB47089F6A21B528C61CB80A13E4229@AM8PR10MB4708.EURPRD10.PROD.OUTLOOK.COM \
--to=bernd.edlinger@hotmail.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).