[Bug libstdc++/52745] GCC4.7 vector uses copy instead of move constructor

2012-03-27 Thread J.W.Rogers+gcc at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52745 Jonathan Rogers changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|

[Bug libstdc++/52745] GCC4.7 vector uses copy instead of move constructor

2012-03-27 Thread J.W.Rogers+gcc at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52745 --- Comment #4 from Jonathan Rogers 2012-03-27 23:25:45 UTC --- (In reply to comment #3) > Otherwise, if the move constructor by chance throws, the push_back cannot have > no effects, as required by 23.2.1/10. Actually the requirement holds for a

[Bug libstdc++/52745] GCC4.7 vector uses copy instead of move constructor

2012-03-27 Thread J.W.Rogers+gcc at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52745 --- Comment #2 from Jonathan Rogers 2012-03-27 23:13:29 UTC --- (In reply to comment #1) > But Stuff' move-constructor isn't known not to throw... Okay, so it is a new requirement for move constructors to be marked as nothrow in order for vector

[Bug libstdc++/52745] New: GCC4.7 vector uses copy instead of move constructor

2012-03-27 Thread J.W.Rogers+gcc at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52745 Bug #: 52745 Summary: GCC4.7 vector uses copy instead of move constructor Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal