xazax.hun added a comment. In https://reviews.llvm.org/D47671#1122994, @george.karpenkov wrote:
> > So having an analyzer-config option would be useful for those codebases > > that are expected to be compiled with less advanced compilers that do not > > elide copies or not doing it aggressively enough. > > I'm not sure it makes sense. From my understanding, that's just how c++17 is > defined, and that's unrelated to what compiler implementation is used. Yeah, this is guaranteed for C++17. My only concern are the projects that need to support platforms where no comforming C++17 compiler is available (I think this might be common in the embedded world). I do not have any numbers though how frequent those projects are. That is the reason why I was wondering if it is worth asking. It is also possible that the authors of those project do not care about the analyzer. But since this config would most probably be removed at some point, I am fine with not adding it. Repository: rC Clang https://reviews.llvm.org/D47671 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
