public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug pch/13218] Potential problems with PCH and includes relative to current directory
Date: Fri, 28 Nov 2003 18:03:00 -0000	[thread overview]
Message-ID: <20031128180323.27086.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031128171002.13218.carlo@gcc.gnu.org>


------- Additional Comments From carlo at gcc dot gnu dot org  2003-11-28 18:03 -------
Well, an alternative would be to re-run the preprocessor
on the source of the pch file and compare the resulting
outcome.  This takes some time, but you only have to
do it for every different 'current directory' that gcc
is in at the moment it includes the pch file.

The pch file should then included:
- The current directory.
- A checksum on the preprocessor output till then.

Extra cpu needed: rerun the preprocessor for every
additional current directory from which the pch
seems to be needed.



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13218


  parent reply	other threads:[~2003-11-28 18:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-28 17:10 [Bug pch/13218] New: " carlo at gcc dot gnu dot org
2003-11-28 17:12 ` [Bug pch/13218] " carlo at gcc dot gnu dot org
2003-11-28 17:44 ` pinskia at gcc dot gnu dot org
2003-11-28 18:03 ` carlo at gcc dot gnu dot org [this message]
2003-11-28 18:05 ` carlo at gcc dot gnu dot org
2003-11-28 18:10 ` pinskia at gcc dot gnu dot org
2003-11-28 23:06 ` carlo at gcc dot gnu dot org
2003-11-30  6:12 ` geoffk at gcc dot gnu dot org
2003-11-30 17:10   ` Carlo Wood
2003-12-01  6:54     ` Geoff Keating
2003-11-30 17:10 ` carlo at alinoe dot com
2003-11-30 17:13 ` carlo at alinoe dot com
2003-12-01  4:42 ` geoffk at gcc dot gnu dot org

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=20031128180323.27086.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).