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: [v3] default linux allocator


Benjamin Kosnik wrote:

If you think that all GNU/Linux users should have this new behavior, then it should be the default in the configury. But, on the 3.4 branch, we should convince ourselves that (a) it's not an ABI change, and (b) it's a major win.



After reviewing performance testresults on x86, ppc, and x86_64, I think
it is a major win.


Can you say a bit more? Technically, what does this change do and how does it improve performance?

I don't see how this is an ABI change, linkage-wise: all the
instantiations for char and wchar_t instantiations remain, for all the
allocators. For other instantiations, there are no exports and thus
local implicit copies of required symbols are assumed.


What if you recompile half of the .o files in your program and not the other half? Do you known have containers in one half using one allocator and containers in the other using the other half? And if so, does that work?

Thanks,

--
Mark Mitchell
CodeSourcery, LLC
(916) 791-8304
mark@codesourcery.com


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