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] | |
Ok, ok, let's work on this assumption ;)Think about it this way. Suppose it wasn't, and I used: list<int>; list<string>; list<float>;
Then, under the current design, all would have their separate free-lists
per thread! Which is obviously insane!
Indeed.In any case, what about not splitting mt_allocator in a __gnu_internal::You mean a __gnu_internal and a __gnu_cxx part right?
part and a std:: part?
Yes, please. Always both 'make check' and 'make check-performance', thanks.Can't we put *all* the implementation detailsProbably? Would you want me to try and do that?
inside _Mt_alloc_base?
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |