This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug pch/13218] Potential problems with PCH and includes relative to current directory
- From: "carlo at alinoe dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 30 Nov 2003 17:10:46 -0000
- Subject: [Bug pch/13218] Potential problems with PCH and includes relative to current directory
- References: <20031128171002.13218.carlo@gcc.gnu.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From carlo at alinoe dot com 2003-11-30 17:10 -------
Subject: Re: Potential problems with PCH and includes relative to current directory
On Sun, Nov 30, 2003 at 06:12:12AM -0000, geoffk at gcc dot gnu dot org wrote:
>
> ------- Additional Comments From geoffk at gcc dot gnu dot org 2003-11-30 06:12 -------
> This is perfectly normal behaviour. Conceptually, PCH operates *after* include directives are
> processed. It would not make sense for it to operate before, since PCH requires include directives
> to determine which PCH file to use.
It is the same PCH in both cases. Same directory, same pch.h, same pch.h.cgh,
same commandline parameters. Completely 100% such that one would expect PCH
to work; and even when it would not work, one would expect a warning or simply
the pch file NOT to be used and lead to world destruction.
It is just that the pch.h uses an #include *somewhere* that is a different
header file based on the current directory.
You can call it "perfectly normal behaviour", but I liked the "damn, but we can't fix
this - lets document it"-remark more.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13218