From: Tom Tromey <tromey@redhat.com>
To: Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Patch: FYI: two missing dependencies
Date: Wed, 07 Nov 2007 18:00:00 -0000 [thread overview]
Message-ID: <m31wb2rmde.fsf@fleche.redhat.com> (raw)
I'm checking this in as obvious.
I happened to notice that basic-block.h includes function.h while
BASIC_BLOCK_H does not mention FUNCTION_H.
Likewise, I noticed that tree-ssa-structalias.o erroneously does not
mention FUNCTION_H.
Bootstrapped on x86 FC-6.
Tom
2007-11-07 Tom Tromey <tromey@redhat.com>
* Makefile.in (tree-ssa-structalias.o): Depend on $(FUNCTION_H)
(BASIC_BLOCK_H): Add vec.h, $(FUNCTION_H).
Index: Makefile.in
===================================================================
--- Makefile.in (revision 129934)
+++ Makefile.in (working copy)
@@ -779,7 +779,8 @@
input.h statistics.h vec.h treestruct.def $(HASHTAB_H) \
double-int.h alias.h
BASIC_BLOCK_H = basic-block.h bitmap.h sbitmap.h varray.h $(PARTITION_H) \
- hard-reg-set.h cfghooks.h $(OBSTACK_H)
+ hard-reg-set.h $(PREDICT_H) vec.h $(FUNCTION_H) \
+ cfghooks.h $(OBSTACK_H)
GCOV_IO_H = gcov-io.h gcov-iov.h auto-host.h
COVERAGE_H = coverage.h $(GCOV_IO_H)
DEMANGLE_H = $(srcdir)/../include/demangle.h
@@ -1981,7 +1982,7 @@
tree-ssa-structalias.o: tree-ssa-structalias.c tree-ssa-structalias.h \
$(SYSTEM_H) $(CONFIG_H) $(GGC_H) $(TREE_H) $(TREE_FLOW_H) \
$(TM_H) coretypes.h $(CGRAPH_H) tree-pass.h $(TIMEVAR_H) \
- gt-tree-ssa-structalias.h $(PARAMS_H) $(ALIAS_H) pointer-set.h
+ gt-tree-ssa-structalias.h $(PARAMS_H) $(ALIAS_H) pointer-set.h $(FUNCTION_H)
tree-ssa.o : tree-ssa.c $(TREE_FLOW_H) $(CONFIG_H) $(SYSTEM_H) \
$(RTL_H) $(TREE_H) $(TM_P_H) $(EXPR_H) output.h $(DIAGNOSTIC_H) \
toplev.h $(FUNCTION_H) $(TIMEVAR_H) $(TM_H) coretypes.h \
reply other threads:[~2007-11-07 18:00 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=m31wb2rmde.fsf@fleche.redhat.com \
--to=tromey@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).