This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ 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: Revert __use_cache relocation


More on this issue ...

Jerry Quinn writes:
 > Carlo Wood writes:
 >  > On Tue, Jul 01, 2003 at 11:51:47AM +0200, Carlo Wood wrote:
 >  > > On Tue, Jul 01, 2003 at 01:38:53AM -0400, Jerry Quinn wrote:
 >  > > > This patch http://gcc.gnu.org/ml/libstdc++/2003-06/msg00368.html is
 >  > > > causing the instantiation problems I'm getting in
 >  > > > http://gcc.gnu.org/ml/libstdc++/2003-07/msg00003.html
 >  > > > 
 >  > > > Reverting this patch until we can figure out how to solve this.
 >  > > > 
 >  > > > Index: include/bits/locale_facets.tcc
 >  > > > +    const __numpunct_cache<char>&
 >  > > > +    __use_cache(const locale& __loc);
 >  > > 

 > The library files get built with -fno-implicit-instantiation.  The one
 > exception is concept-inst.cc.  That's so that it can instantiate a
 > whole raft of stuff to perform concept checks (and beyond that, I
 > don't know what's going on in there).

I tried building the library without -fimplicit-instantiation on
concept-inst.cc and it does allow me to apply the patch I tried
before.  However, this is clearly opening a can of worms.

In general, why haven't instantiations in concept-inst.cc conflictd
with instantiations in other files?  It seems to me that sooner or
later this kind of thing is going to pop up.

Or am I missing something (entirely possible :-)

Jerry



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