https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59603
Tony E Lewis changed:
What|Removed |Added
CC||TonyELewis at hotmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59603
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59603
--- Comment #10 from Jonathan Wakely ---
Author: redi
Date: Sat Dec 6 20:38:07 2014
New Revision: 218454
URL: https://gcc.gnu.org/viewcvs?rev=218454&root=gcc&view=rev
Log:
PR libstdc++/59603
* include/bits/stl_algo.h (random_shuffle): P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59603
--- Comment #9 from Jonathan Wakely ---
Author: redi
Date: Wed Oct 1 12:34:04 2014
New Revision: 215754
URL: https://gcc.gnu.org/viewcvs?rev=215754&root=gcc&view=rev
Log:
PR libstdc++/59603
* include/bits/stl_algo.h (random_shuffle): Pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59603
--- Comment #8 from Jonathan Wakely ---
Fixed on trunk so far.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59603
--- Comment #7 from Jonathan Wakely ---
Author: redi
Date: Fri Sep 12 13:30:35 2014
New Revision: 215219
URL: https://gcc.gnu.org/viewcvs?rev=215219&root=gcc&view=rev
Log:
PR libstdc++/59603
* include/bits/stl_algo.h (random_shuffle): Pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59603
--- Comment #6 from Jonathan Wakely ---
(In reply to Jörg Richter from comment #2)
> Seems like we have hit this bug too. It happens not only in debug mode. We
> have a testcase that triggers valgrind errors in non-debug mode while
> calling ra
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59603
--- Comment #5 from Jonathan Wakely ---
Even if swapping an object with itself is well-defined it's a waste of time, so
we shouldn't do it.
There's a discussion happening now with the C++ library working group to
resolve whether self-move-assignm
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59603
--- Comment #4 from Jörg Richter ---
Are you sure that this is not a iter_swap problem? I have found nothing in the
standard that iter_swap( x, x ) is undefined.
I always thought types do not have to be prepared to handle self move
assignment.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59603
--- Comment #3 from Jonathan Wakely ---
This patch avoids the self-move:
index 4c6ca8a..6ce2d21 100644
--- a/libstdc++-v3/include/bits/stl_algo.h
+++ b/libstdc++-v3/include/bits/stl_algo.h
@@ -4430,7 +4430,12 @@ _GLIBCXX_BEGIN_NAMESPACE_ALGO
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59603
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59603
Jörg Richter changed:
What|Removed |Added
CC||joerg.rich...@pdv-fs.de
--- Comment #2 fro
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59603
--- Comment #1 from Fabian Emmes ---
Created attachment 31518
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31518&action=edit
program triggering the error
13 matches
Mail list logo