This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

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

From: Phil Edwards <phil at jaj dot com>
To: Geoff Keating <geoffk at geoffk dot org>
Cc: bkoz at redhat dot com, gcc at gcc dot gnu dot org
Date: Mon, 11 Aug 2003 19:32:28 -0400
Subject: Re: PCH not being used, but I can't tell why
References: <20030811131743.2fb92235.bkoz@redhat.com> <jm65l4gggc.fsf@desire.geoffk.org> <20030811192341.GA32024@disaster.jaj.com> <200308112133.h7BLXkj17028@desire.geoffk.org>

On Mon, Aug 11, 2003 at 02:33:46PM -0700, Geoff Keating wrote:
> > 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
> 
> Could you start gdb, break on c_common_valid_pch, and see what's going
> on?

That function is never called.

-- 
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

Follow-Ups:
- Re: PCH not being used, but I can't tell why
  - From: Geoff Keating

References:
- Re: PCH not being used, but I can't tell why
  - From: Benjamin Kosnik
- Re: PCH not being used, but I can't tell why
  - From: Geoff Keating
- Re: PCH not being used, but I can't tell why
  - From: Phil Edwards
- Re: PCH not being used, but I can't tell why
  - From: Geoff Keating

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]