[Bug libstdc++/17937] Critical ~__pool troubles
pcarlini at suse dot de
gcc-bugzilla@gcc.gnu.org
Mon Oct 11 23:50:00 GMT 2004
------- Additional Comments From pcarlini at suse dot de 2004-10-11 23:50 -------
> It would be list.... ugh. Damn that allocator rebinding! I'm developing severe
> issues with this particular container. Well, this kills off this QoI
> improvement. I've reverted this on mainline, and fixed up the testcases that
> test for this to be of the type that showed this, more advanced, problem.
Many thanks.
> I'm going to keep the infrastructure in __mt_alloc to do the actual
> deallocations, however. At least, for the time being.
Ok, but as long as we don't use that, let's avoid taking the lock a second
time in _M_reserve_block, the new calls and so on... I propose to protect
with macros or #if 0 or whatelse those snippets too.
Thanks again.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17937
More information about the Gcc-bugs
mailing list