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 was able to reproduce the problem after all.  The goal has to be to
> emit an undefined symbol into every object file that "tags" it as
> being compiled against one or the other ABI.  I'm trying to work out
> different ways to do this and then choose the one with the minimal
> side effects (i.e. runtime cost, etc).

We already have symbol versioning that does this. You don't need another
mechanism.

I don't understand why this isn't much simpler. 

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.

-benjamin


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