search for: misrecalling

Yes, we should produce this warning in C++11 mode too. (I could be misrecalling, but I think the rationale for the current behaviour is based on historical GCC behaviour.) On Sun, 16 Sep 2018, 10:04 David Blaikie via cfe-dev, < cfe-dev at lists.llvm.org> wrote: > Fair point made on that thread - that this is a DR, so technically the > std::move is pessimizing eve...

...: > I'll look into the pessimizing move warning, then after that, the > deprecated copy warning. > > On Sun, Sep 16, 2018 at 10:41 AM Richard Smith <richard at metafoo.co.uk> > wrote: > >> Yes, we should produce this warning in C++11 mode too. (I could be >> misrecalling, but I think the rationale for the current behaviour is based >> on historical GCC behaviour.) >> >> On Sun, 16 Sep 2018, 10:04 David Blaikie via cfe-dev, < >> cfe-dev at lists.llvm.org> wrote: >> >>> Fair point made on that thread - that this is a DR, s...

There is a new discussion related to -Wredundant-move warning on GCC bugzilla. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87300 pi 14. 9. 2018 o 9:53 David Blaikie <dblaikie at gmail.com> napísal(a): > > > On Fri, Sep 14, 2018 at 12:48 AM Stephan Bergmann <sbergman at redhat.com> > wrote: > >> On 13/09/2018 18:22, David Blaikie via llvm-dev wrote: >>