[Gc] gcc34 c++ support
elanthis at awesomeplay.com
Fri Apr 23 11:46:56 PDT 2004
On Fri, 2004-04-23 at 13:46, Boehm, Hans wrote:
> Did you try gc_allocator.h instead of new_gc_alloc.h?
OK, having converted one of my smaller projects (and writing a few
wrapper classes; defining a std::map with a non-standard allocator using
the "standard" allocator style gets very very ugly very very quickly...)
it does compile and work.
There is a bits/allocator.h in libstdc++4, that may be usable instead of
bits/std_alloc.h. It appears there is already some detection code in
new_gc_alloc.h for older compilers, perhaps it's possible to do so for
the newer one as well, for backwards compatibility with apps that don't
want to rewrite swaths of code that use the older allocator interface.
> The former is intended to be standards-conforming. Hence it should be broken
> only by buggy C++ implementations, and we know there aren't any of those :-) .
> > -----Original Message-----
> > From: gc-bounces at napali.hpl.hp.com
> > [mailto:gc-bounces at napali.hpl.hp.com]On Behalf Of Sean Middleditch
> > Sent: Friday, April 23, 2004 10:33 AM
> > To: gc at napali.hpl.hp.com
> > Subject: [Gc] gcc34 c++ support
> > GCC 3.4 seems to have removed the bits/stl_alloc.h header from
> > libstdc++, which the GC library requires, making it impossible to
> > compile a C++ using the library's C++ support.
> > I haven't had time to check if another header provides the necessary
> > declarations/templates/etc, but I thought I'd provide a heads up that
> > the problem exists.
> > --
> > Sean Middleditch <elanthis at awesomeplay.com>
> > AwesomePlay Productions, Inc.
> > _______________________________________________
> > Gc mailing list
> > Gc at linux.hpl.hp.com
> > https://www.hpl.hp.com/hosted/linux/mail-archives/gc/
Sean Middleditch <elanthis at awesomeplay.com>
AwesomePlay Productions, Inc.
More information about the Gc