public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Bernd Edlinger <edlinger@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-1106] Generate gimple-match.c and generic-match.c earlier Date: Fri, 28 May 2021 06:51:26 +0000 (GMT) [thread overview] Message-ID: <20210528065126.54DD43857011@sourceware.org> (raw) https://gcc.gnu.org/g:c9114f2804b91690e030383de15a24e0b738e856 commit r12-1106-gc9114f2804b91690e030383de15a24e0b738e856 Author: Bernd Edlinger <bernd.edlinger@hotmail.de> Date: Fri May 28 06:27:27 2021 +0200 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 and 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 Diff: --- gcc/Makefile.in | 1 + 1 file changed, 1 insertion(+) diff --git a/gcc/Makefile.in b/gcc/Makefile.in index da2ef246c81..4cb2966157e 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
reply other threads:[~2021-05-28 6:51 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210528065126.54DD43857011@sourceware.org \ --to=edlinger@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.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: linkBe 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).