Abhishek Deshpande via llvm-dev
2017-Aug-14 10:34 UTC
[llvm-dev] clang-tidy : Modify cert-err60-cpp configuration
We want to modify the aforementioned check so that it does not flag the exceptions that aren't nothrow copy constructible/assignable. This page http://clang.llvm.org/extra/clang-tidy/#using-clang-tidy tells me to dump the configs of all the checks using %clang-tidy -checks=* -dump-config but it does not mention the cert-err60-cpp. How do I modify the configuration of this check so that it ignores exceptions that aren't nothrow copy constructible/assignable ? Or should I just disable the check altogether ? Thanks, AD -- Only thing that you have in your hands....is "Diligence".....For its results are always affirmative.... -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170814/0d4ef8d4/attachment.html>
Aaron Ballman via llvm-dev
2017-Aug-14 12:09 UTC
[llvm-dev] clang-tidy : Modify cert-err60-cpp configuration
On Mon, Aug 14, 2017 at 6:34 AM, Abhishek Deshpande via llvm-dev <llvm-dev at lists.llvm.org> wrote:> We want to modify the aforementioned check so that it does not flag the > exceptions that aren't nothrow copy constructible/assignable. > > This page > http://clang.llvm.org/extra/clang-tidy/#using-clang-tidy > tells me to dump the configs of all the checks using > > %clang-tidy -checks=* -dump-config > > but it does not mention the cert-err60-cpp. > > How do I modify the configuration of this check so that it ignores > exceptions that aren't nothrow copy constructible/assignable ? > > Or should I just disable the check altogether ?You should disable the check (or fix the offending code) -- the purpose to that check is specifically to diagnose exceptions that are not nothrow copy constructible, in conformance to https://www.securecoding.cert.org/confluence/display/cplusplus/ERR60-CPP.+Exception+objects+must+be+nothrow+copy+constructible. ~Aaron
Abhishek Deshpande via llvm-dev
2017-Aug-14 12:48 UTC
[llvm-dev] clang-tidy : Modify cert-err60-cpp configuration
Ok, I'll do that. Thanks, AD On Aug 14, 2017 5:39 PM, "Aaron Ballman" <aaron at aaronballman.com> wrote:> On Mon, Aug 14, 2017 at 6:34 AM, Abhishek Deshpande via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > We want to modify the aforementioned check so that it does not flag the > > exceptions that aren't nothrow copy constructible/assignable. > > > > This page > > http://clang.llvm.org/extra/clang-tidy/#using-clang-tidy > > tells me to dump the configs of all the checks using > > > > %clang-tidy -checks=* -dump-config > > > > but it does not mention the cert-err60-cpp. > > > > How do I modify the configuration of this check so that it ignores > > exceptions that aren't nothrow copy constructible/assignable ? > > > > Or should I just disable the check altogether ? > > You should disable the check (or fix the offending code) -- the > purpose to that check is specifically to diagnose exceptions that are > not nothrow copy constructible, in conformance to > https://www.securecoding.cert.org/confluence/display/cplusplus/ERR60-CPP.+ > Exception+objects+must+be+nothrow+copy+constructible. > > ~Aaron >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170814/65eb0ef5/attachment.html>
Maybe Matching Threads
- [LLVMdev] why we assume malloc() always returns a non-null pointer in instruction combing?
- [LLVMdev] why we assume malloc() always returns a non-null pointer in instruction combing?
- [LLVMdev] why we assume malloc() always returns a non-null pointer in instruction combing?
- [LLVMdev] why we assume malloc() always returns a non-null pointer in instruction combing?
- [LLVMdev] Clang Integration with MSVS 2013