PCH not being used, but I can't tell why

[Phil Edwards]

On Mon, Aug 11, 2003 at 12:08:35PM -0700, Geoff Keating wrote:
> Benjamin Kosnik <bkoz@redhat.com> writes:
> 
> > Geoff, pretty sure this is not a directory naming thing. 
> 
> Hmmm.  The 'x' means that indeed it's being found and is considered to
> be invalid, so it ought to print out a message with -Winvalid-pch.  
> 
> Looking at the code, it seems like there are some exit paths from
> cpp_valid_state that don't print a warning message.  Try this patch
> and tell me if it helps.

No difference:

x /mnt/build/build-2003-08-11/i686-pc-linux-gnu/libstdc++-v3/include/i686-pc-linux-gnu/bits/stdc++.h.gch/O0g
x /mnt/build/build-2003-08-11/i686-pc-linux-gnu/libstdc++-v3/include/i686-pc-linux-gnu/bits/stdc++.h.gch/O2g
. /mnt/build/build-2003-08-11/i686-pc-linux-gnu/libstdc++-v3/include/i686-pc-linux-gnu/bits/stdc++.h


-- 
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it.
    - Brian W. Kernighan