[Bug c++/87300] -Wredundant-move gives false positives in C++11 mode

2018-09-17 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87300 --- Comment #5 from Jonathan Wakely --- Sorry you're right, I forgot we're talking about the converting case here. The move doesn't prevent elision (because elision isn't possible here).

[Bug c++/87300] -Wredundant-move gives false positives in C++11 mode

2018-09-14 Thread steinar+gcc at gunderson dot no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87300 --- Comment #4 from Steinar H. Gunderson --- Wait, can it elide the move even if it's a conversion? How could that work in the general case?

[Bug c++/87300] -Wredundant-move gives false positives in C++11 mode

2018-09-14 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87300 --- Comment #3 from Jonathan Wakely --- Yes The first published standard to include the change was C++14 but it's a DR against the previous standard. That means it's fixing a bug in the previous standard. The -std=c++11 flag is documented to m

[Bug c++/87300] -Wredundant-move gives false positives in C++11 mode

2018-09-14 Thread steinar+gcc at gunderson dot no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87300 --- Comment #2 from Steinar H. Gunderson --- Hm, am I misunderstanding it? It said “Status: C++14”. Even so, does it apply to C++11?

[Bug c++/87300] -Wredundant-move gives false positives in C++11 mode

2018-09-14 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87300 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---