[Bug libstdc++/41530] New: [c++0x] Cannot move-construct std::tuple from a different type of std::tuple

fferent type of std::tuple Product: gcc Version: 4.4.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jbytheway at gmail dot com GCC build triplet: x86_64-pc-linux-gnu GCC host triplet: x86_64-pc-linux-gnu GCC target triplet: x86_64-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41530

[Bug libstdc++/41530] [c++0x] Cannot move-construct std::tuple from a different type of std::tuple

--- Comment #4 from jbytheway at gmail dot com 2009-10-05 17:48 --- I've added my name to my account details. You should see it up there somewhere ^^. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41530

[Bug libstdc++/41622] New: [c++0x] std::hash::operator() copies its argument

unassigned at gcc dot gnu dot org ReportedBy: jbytheway at gmail dot com GCC build triplet: x86_64-pc-linux-gnu GCC host triplet: x86_64-pc-linux-gnu GCC target triplet: x86_64-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41622

[Bug libstdc++/41622] [c++0x] std::hash::operator() copies its argument

--- Comment #1 from jbytheway at gmail dot com 2009-10-07 15:45 --- Created an attachment (id=18741) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18741&action=view) Patch providing proof-of-concept implementation I attach a patch implementing this change on svn HEAD. It

[Bug libstdc++/41622] [c++0x] std::hash::operator() copies its argument

--- Comment #5 from jbytheway at gmail dot com 2009-10-08 19:40 --- Ah well. I'm not surprised. If you do wish to argue the point at Santa Cruz and I can be any help then let me know. I have no particular intention to contribute; I'm just working through my backlog of b

[Bug libstdc++/87872] New: debug list::splice should not call _M_transfer_from_if on self-splices

Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: jbytheway at gmail dot com Target Milestone: --- I encountered this issue when trying to understand the performance of a _GLIBCXX_DEBUG build of a least-recently-used cache

[Bug libstdc++/87872] debug list::splice should not call _M_transfer_from_if on self-splices

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87872 --- Comment #1 from John Bytheway --- On further reflection, it would make more sense to put this check inside _M_transfer_from_if, rather than in every splice function.

[Bug libstdc++/87872] debug list::splice should not call _M_transfer_from_if on self-splices

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87872 --- Comment #3 from John Bytheway --- Created attachment 44955 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44955&action=edit Proposed patch Sure, here's a proposed patch. Tested in the sense that I have compiled and run a program again