This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
libstdc++/9828 (was Re: zero-alloc cache)
- From: Jerry Quinn <jlquinn at optonline dot net>
- To: "B. Kosnik" <bkoz at nabi dot net>, libstdc++ at gcc dot gnu dot org
- Date: Fri, 02 May 2003 00:49:16 -0400
- Subject: libstdc++/9828 (was Re: zero-alloc cache)
- References: <E190xa9-0006B0-00@tiamat> <20030403103008.GA28026@alinoe.com><16012.17149.823856.404456@gargle.gargle.HOWL><20030411102928.GA32143@alinoe.com><16031.32556.123697.603768@gargle.gargle.HOWL><20030427153915.GA5850@alinoe.com><16044.51345.781643.861197@gargle.gargle.HOWL><16047.18989.705946.856897@gargle.gargle.HOWL><16048.47523.75693.638570@gargle.gargle.HOWL><20030501145155.7ce298cb.bkoz@nabi.net><16049.60536.905007.548382@gargle.gargle.HOWL>
Jerry Quinn writes:
> > I'm also having second thoughts about this approach to locale caching in
> > general. I've implemented __has_cache/__use_cache and while it's not as fast
> > as the __locale_cache code as present, it's still on par with 2.95 and
> > it seems like a better way to go.
> >
> > Awful lot of "I's" in the above text. Your honest feedback is appreciated.
>
> I'd rather see it in there than not. For sure, the ABI compatibility
> puts some limitations on what we can do. And I agree that the pword
> method has some unpleasant aspects to it. Also, we need something
> like the __has_cache approach to deal with the problem pointed out by
> Petur in this thread:
> http://gcc.gnu.org/ml/libstdc++/2003-04/msg00023.html
I actually see that PR 9828 is still broken on 3.3, even with the
locale cache scrapped.
Ouch! I just tried to look at it in gdb, and I can no longer use gdb
within the library itself. I was using the approach of rebuilding
just the library with:
make clean
make CXXFLAGS=-g3 install
after which i could step into library code. After updating, I can't
seem to do it anymore.
Anyone else having similar difficulty now?
Jerry