They might prevent copy-elision optimization and generate noisy warnings with gcc.
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
I'm not certain but I thought some of these moves had to be kept to appease old versions of gcc - but I can't remember any details.
llvm/include/llvm/Bitstream/BitstreamReader.h | ||
---|---|---|
429 | Any idea what clang-tidy is warning about here? |
I'm pretty sure the std::move I added in FileCheck were because of warning I had on my machine (Ubuntu 18.04). I'll try to give the patch a spin and report.
Also, sorry for hijacking but if you're looking at std::move cleanup, this scary static analysis warning has been around for a while: https://llvm.org/reports/scan-build/report-BitcodeReader.cpp-BitcodeReader-0-1.html#EndPath
clang-tidy: error: call to deleted constructor of 'llvm::Error' [clang-diagnostic-error]
not useful
clang-tidy: error: call to deleted constructor of 'llvm::Error' [clang-diagnostic-error]
not useful
clang-tidy: error: call to deleted constructor of 'llvm::Error' [clang-diagnostic-error]
not useful