From: Jason Merrill <jason@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] * Makefile.in (build/genmatch.o): Depend on $(CPPLIB_H).
Date: Mon, 16 Sep 2019 16:19:00 -0000 [thread overview]
Message-ID: <20190916161904.3344-1-jason@redhat.com> (raw)
So that rebuilding my tree with or without the operator<=> patches properly
rebuilds genmatch.
Tested x86_64-pc-linux-gnu, applying to trunk as obvious.
---
gcc/Makefile.in | 2 +-
gcc/ChangeLog | 4 ++++
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/gcc/Makefile.in b/gcc/Makefile.in
index 0fe02fb27a1..152df9fa9b3 100644
--- a/gcc/Makefile.in
+++ b/gcc/Makefile.in
@@ -2783,7 +2783,7 @@ build/genmddump.o : genmddump.c $(RTL_BASE_H) $(BCONFIG_H) $(SYSTEM_H) \
$(CORETYPES_H) $(GTM_H) errors.h $(READ_MD_H) $(GENSUPPORT_H)
build/genmatch.o : genmatch.c $(BCONFIG_H) $(SYSTEM_H) \
$(CORETYPES_H) errors.h $(HASH_TABLE_H) hash-map.h $(GGC_H) is-a.h \
- tree.def builtins.def internal-fn.def case-cfn-macros.h
+ tree.def builtins.def internal-fn.def case-cfn-macros.h $(CPPLIB_H)
build/gencfn-macros.o : gencfn-macros.c $(BCONFIG_H) $(SYSTEM_H) \
$(CORETYPES_H) errors.h $(HASH_TABLE_H) hash-set.h builtins.def \
internal-fn.def
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 1921bc775d6..63fae8615e5 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,7 @@
+2019-09-16 Jason Merrill <jason@redhat.com>
+
+ * Makefile.in (build/genmatch.o): Depend on $(CPPLIB_H).
+
2019-09-16 Martin Liska <mliska@suse.cz>
* gimple-fold.c (or_comparisons_1): Remove rules moved
base-commit: 4bc26ca2c40a29d0f49bad7a8326dbac6f764c35
--
2.21.0
reply other threads:[~2019-09-16 16:19 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=20190916161904.3344-1-jason@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@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: 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).