Closed ymd8bit closed 5 years ago
Thanks for the report, I'll try to verify/address later today.
There was some discussion on this here: http://clang-developers.42468.n3.nabble.com/Re-llvm-dev-New-warnings-when-building-trunk-with-GCC-9-td4062064.html
GCC is using the move ctor for these, while Clang is using the copy ctor; so Clang emits a warning. Using std::move(..) here inverts things - GCC will emit a warning on a redundant std::move while it'd be warning free with Clang. :-(
I believe these have been addressed: I no longer see these in opt build using GCC 8.3 (in Release build and without specifying build type as above on both Ubuntu 18.04 and GCC docker image). If you can still reproduce, please open again with repro steps. Thanks!
The bug report says that these are with clang-8, not with GCC.
Misread, no wonder I couldn't reproduce (I was using the cmake configuration command given)
When I compile mlir with clang-8 I encountered many warnings seem relevant to move semantics like below. Is it ok keeping it?? (though they didn't appear when I compile it with gcc-8). I'm expecting just add
std::move
to suppress these by following the suggestions.My configuration and build command.