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


> X-Original-To: geoffk@foam.wonderslug.com
> Date: Tue, 12 Aug 2003 18:14:21 -0400
> From: Phil Edwards <phil@jaj.com>
> Cc: bkoz@redhat.com, gcc@gcc.gnu.org
> Content-Disposition: inline
> User-Agent: Mutt/1.5.3i
> X-OriginalArrivalTime: 12 Aug 2003 22:18:33.0015 (UTC) FILETIME=[AA930C70:01C3611F]
> 
> On Mon, Aug 11, 2003 at 11:48:10PM -0700, Geoff Keating wrote:
> > > cc1plus: warning: /mnt/build/build-2003-08-11/i686-pc-linux-gnu/libstdc++-v3/include/i686-pc-linux-gnu/bits/stdc++.h.gch/O0g: not used because `__tune_i686__' not defined
> > > cc1plus: warning: /mnt/build/build-2003-08-11/i686-pc-linux-gnu/libstdc++-v3/include/i686-pc-linux-gnu/bits/stdc++.h.gch/O2g: not used because `__tune_i686__' not defined
> > > 
> > > ...whatever the fsck that means.
> > 
> > It probably means that there's a -mtune= mismatch between building the
> > PCH and using it.
> 
> Now I'm seeing the same warning because __NO_INLINE__ isn't defined.
> (We build the pch with xgcc, but run the testsuite with g++.  Maybe that's
> causing problems.)

Are you using the exact same options to GCC when building and using
the PCH?

-- 
- Geoffrey Keating <geoffk@geoffk.org>


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