[Bug libstdc++/21609] array_allocator vs rebind & copy-constructor
pcarlini at suse dot de
gcc-bugzilla@gcc.gnu.org
Mon May 16 16:31:00 GMT 2005
------- Additional Comments From pcarlini at suse dot de 2005-05-16 16:30 -------
Forgot to say: probably the issue can be dealt with at the cost of increasing
its complexity. Logic could be added to the copy-constructor(s) to the effect
of keeping on using the existing allocated memory, i.e., not zeroing _M_array
in the templated copy-contructor. This would make sense only when the alignment
is still appropriate for the new type: this check could be either responsability
of the user or enforced by the allocator (more tricky).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21609
More information about the Gcc-bugs
mailing list