Author: alexfh
Date: Fri Apr 1 22:44:23 2016
New Revision: 265210
URL: http://llvm.org/viewvc/llvm-project?rev=265210&view=rev
Log:
[clang-tidy] Update an example. NFC.
Modified:
clang-tools-extra/trunk/test/clang-tidy/check_clang_tidy.py
Modified: clang-tools-extra/trunk/test/clang-tidy/ch
alexfh added a comment.
In http://reviews.llvm.org/D17482#387457, @LegalizeAdulthood wrote:
> I'm sorry to be such a nag and I know you're busy, but
>
> This changeset has been held up for a month and a half. (6 weeks since
> originally posted in http://reviews.llvm.org/D16953)
>
> The chang
alexfh added a comment.
Sorry for the lng delay. I missed you patch among all other ones. Could you
rebase your patch on top of HEAD and clang-format the files you changed? I'll
come back with more substantial comments early next week.
http://reviews.llvm.org/D16183
alexfh added inline comments.
Comment at: clang-tidy/misc/SuspiciousStringCompareCheck.cpp:38
@@ +37,3 @@
+ callExpr(hasDeclaration(functionDecl(
+ hasAnyName("__builtin_memcmp",
+ "__builtin_strcasecmp",
Should we add a configura
etienneb added a comment.
I spent time thinking about Eugene.Zelenko@ comment and I start to believe that
given the difference between the errors ratio and the warnings ratio, maybe we
should gate the report 'explicitly comparing result' under a configurable
option.
There is an order of magnit
Author: gparker
Date: Sat Apr 2 00:29:00 2016
New Revision: 265218
URL: http://llvm.org/viewvc/llvm-project?rev=265218&view=rev
Log:
[test] Don't use "UNSUPPORTED" in FileCheck prefixes
lit uses "UNSUPPORTED:" for its own purposes and may be
confused if that text appears elsewhere in the test f
101 - 106 of 106 matches
Mail list logo
