[Patch] libstdc++/23425

[Paolo Carlini]

chris jefferson wrote:

>Sorry, I meant when the loop isn't removed because _Destroy has to
>actually do something, then vector is slightly slower and deque is
>slightly faster (of course if that "doing something" isn't
>super-trivial, like just maintaining a reference count or something,
>then the extra tiny loop overhead gets quickly swamped away).
>  
>
Ok. No confusions, anyway, I was really asking whether the current
optimizers are basically able to deal perfectly with the
trivial_destructor case, eventually producing the same code that could
be obtained if we had a perfect type_traits to begin with. In case of
vector, to be sure, not deque.

Anyway, the attached will help further playing with the idea ;)

Paolo.

///////////////
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch_destroy
URL: <http://gcc.gnu.org/pipermail/libstdc++/attachments/20051102/32f8a6ff/attachment.ksh>