public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "geoffk at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug pch/14238] Dependency tracking and PCH
Date: Wed, 14 Apr 2004 08:04:00 -0000 [thread overview]
Message-ID: <20040414061453.28412.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040221172413.14238.carlo@gcc.gnu.org>
------- Additional Comments From geoffk at gcc dot gnu dot org 2004-04-14 06:14 -------
> It is not correct behaviour.
> If you delete a2.h then the PCH file SHOULD be made
> (it depends on a2.h) and would fail. Deleting it is
> no different than changing it. When you change it,
> then you want both, the PCH file to be remade as well
> as all compilation units depending on a2.h (not pch.h).
Right, but a.o does not directly depend on a2.h. a.o depends on pch.h.gch which depends on a2.h.
It sounds like what you want is the answer to the question "if the -include was not passed, what would
the dependencies of a.o be?" You can get that answer by asking that question: by using
g++-cvs-3.4 -E a.cc -MD -MP -MT a.o -MF a.deps -o /dev/null
Alternatively, you might be wanting the answer to the question "if PCH was not used, what would the
dependencies of a.o be?" You can get the answer to that question by using the -fpch-deps flag.
Bug 14933 already covers the problem that pch.h.gch is not mentioned in the dependency list of a.o.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14238
prev parent reply other threads:[~2004-04-14 6:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-21 17:24 [Bug preprocessor/14238] New: " carlo at gcc dot gnu dot org
2004-02-21 17:25 ` [Bug preprocessor/14238] " carlo at gcc dot gnu dot org
2004-04-13 4:27 ` [Bug pch/14238] " pinskia at gcc dot gnu dot org
2004-04-13 18:41 ` geoffk at gcc dot gnu dot org
2004-04-14 0:07 ` carlo at gcc dot gnu dot org
2004-04-14 8:04 ` geoffk at gcc dot gnu dot org [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=20040414061453.28412.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).