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: [PATCH] Slightly better way to __USE_MALLOC

> > I'd think you can just go ahead with the plot to have both allocators
> > available all the time. Add both the malloc_alloc_template, and the
> > pool_alloc_template instantiations. These new symbols can be put into
> > the GLIBCPP_3.2.1 version, or GLIBCPP_3.3, so that linkage is
> > versioned.
> 
> I agree that they can both be available all the time, but the default
> allocator used by the STL containers can only be one of them.  To me,
> there is value in being able to swap the malloc-based allocator in
> underneath everything, even if it means I have to recompile all
> application code.  I don't think it's possible to do things as
> efficiently and not have to recompile.

Right.

Then the --enable flag becomes --enable-default-allocator or whatever. 

Sounds like you are on the right track...

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