Re: [analyzer] Add support for __builtin_constant_p to BuiltinFunctionChecker

Hi Felix, If you would like to get the patch reviewed and committed the best way is to create a review in phabricator (http://reviews.llvm.org) and add Devin Coughlin, me, and Artem Dergachev as reviewers. > On Jan 16, 2018, at 7:30 PM, Vedant Kumar wrote: > > + Devin and George > >> On Jan

r323696 - [analyzer] [NFC] Remove unused method visitItemsInWorkList

Author: george.karpenkov Date: Mon Jan 29 13:44:49 2018 New Revision: 323696 URL: http://llvm.org/viewvc/llvm-project?rev=323696&view=rev Log: [analyzer] [NFC] Remove unused method visitItemsInWorkList Differential Revision: https://reviews.llvm.org/D42562 Modified: cfe/trunk/include/clang/S

r323697 - [analyzer] Use stable filenames in analyzer testing infrastructure

Author: george.karpenkov Date: Mon Jan 29 13:45:07 2018 New Revision: 323697 URL: http://llvm.org/viewvc/llvm-project?rev=323697&view=rev Log: [analyzer] Use stable filenames in analyzer testing infrastructure Makes finding the right file in test results easier. Differential Revision: https://re

r323827 - [analyzer] Extend SuppressInlineDefensiveChecksVisitor to all macros, including non-function-like ones

Author: george.karpenkov Date: Tue Jan 30 14:58:06 2018 New Revision: 323827 URL: http://llvm.org/viewvc/llvm-project?rev=323827&view=rev Log: [analyzer] Extend SuppressInlineDefensiveChecksVisitor to all macros, including non-function-like ones No reason to treat function-like macros differentl

r323941 - [analyzer] [tests] Show the number of removed/added bug reports

Author: george.karpenkov Date: Wed Jan 31 18:38:42 2018 New Revision: 323941 URL: http://llvm.org/viewvc/llvm-project?rev=323941&view=rev Log: [analyzer] [tests] Show the number of removed/added bug reports Differential Revision: https://reviews.llvm.org/D42718 Modified: cfe/trunk/utils/anal

r324021 - [analyzer] [tests] Add an option to show the histogram of path differences between the analyzer runs

Author: george.karpenkov Date: Thu Feb 1 14:25:18 2018 New Revision: 324021 URL: http://llvm.org/viewvc/llvm-project?rev=324021&view=rev Log: [analyzer] [tests] Add an option to show the histogram of path differences between the analyzer runs Differential Revision: https://reviews.llvm.org/D427

r324027 - [analyzer] [tests] [NFC] Remove dead code from CmpRuns

Author: george.karpenkov Date: Thu Feb 1 14:40:01 2018 New Revision: 324027 URL: http://llvm.org/viewvc/llvm-project?rev=324027&view=rev Log: [analyzer] [tests] [NFC] Remove dead code from CmpRuns Indeed, "CHANGE" is not a thing yet, and we should probably not carry around dead code which does n

r324046 - [analyzer] Fix yet-another-crash in body-farming std::call_once

Author: george.karpenkov Date: Thu Feb 1 17:44:07 2018 New Revision: 324046 URL: http://llvm.org/viewvc/llvm-project?rev=324046&view=rev Log: [analyzer] Fix yet-another-crash in body-farming std::call_once Crash occurs when parameters to the callback and to std::call_once mismatch, and C++ is su

r324049 - [analyzer] Expose exploration strategy through analyzer options.

Author: george.karpenkov Date: Thu Feb 1 18:01:55 2018 New Revision: 324049 URL: http://llvm.org/viewvc/llvm-project?rev=324049&view=rev Log: [analyzer] Expose exploration strategy through analyzer options. Differential Revision: https://reviews.llvm.org/D42774 Modified: cfe/trunk/include/c

r324050 - Remove the change which accidentally crept in into the cherry-pick

Author: george.karpenkov Date: Thu Feb 1 18:14:33 2018 New Revision: 324050 URL: http://llvm.org/viewvc/llvm-project?rev=324050&view=rev Log: Remove the change which accidentally crept in into the cherry-pick Modified: cfe/trunk/lib/StaticAnalyzer/Core/AnalyzerOptions.cpp Modified: cfe/trun

r324052 - [analyzer] Expose return statement from CallExit program point

Author: george.karpenkov Date: Thu Feb 1 18:19:43 2018 New Revision: 324052 URL: http://llvm.org/viewvc/llvm-project?rev=324052&view=rev Log: [analyzer] Expose return statement from CallExit program point If the return statement is stored, we might as well allow querying against it. Also fix the

r324114 - [analyzer] [tests] Fix crash in SATestBuild.py

Author: george.karpenkov Date: Fri Feb 2 10:27:14 2018 New Revision: 324114 URL: http://llvm.org/viewvc/llvm-project?rev=324114&view=rev Log: [analyzer] [tests] Fix crash in SATestBuild.py Modified: cfe/trunk/utils/analyzer/CmpRuns.py Modified: cfe/trunk/utils/analyzer/CmpRuns.py URL: http

r324161 - [analyzer] Do not infer nullability inside function-like macros, even when macro is explicitly returning NULL

Author: george.karpenkov Date: Fri Feb 2 16:55:21 2018 New Revision: 324161 URL: http://llvm.org/viewvc/llvm-project?rev=324161&view=rev Log: [analyzer] Do not infer nullability inside function-like macros, even when macro is explicitly returning NULL We already suppress such reports for inline

r301212 - Flag -fsanitize=fuzzer to enable libfuzzer

Author: george.karpenkov Date: Mon Apr 24 13:23:24 2017 New Revision: 301212 URL: http://llvm.org/viewvc/llvm-project?rev=301212&view=rev Log: Flag -fsanitize=fuzzer to enable libfuzzer Previously, adding libfuzzer to a project was a multi-step procedure, involving libfuzzer compilation, linking

r301216 - Remove erroneous driver test for -fsanitize=fuzzer flag

Author: george.karpenkov Date: Mon Apr 24 13:36:31 2017 New Revision: 301216 URL: http://llvm.org/viewvc/llvm-project?rev=301216&view=rev Log: Remove erroneous driver test for -fsanitize=fuzzer flag libfuzzer is not available on all platforms, and hence we can not always rely that it was compiled

r301246 - Specify a target explicitly in libfuzzer driver flag test

Author: george.karpenkov Date: Mon Apr 24 15:38:56 2017 New Revision: 301246 URL: http://llvm.org/viewvc/llvm-project?rev=301246&view=rev Log: Specify a target explicitly in libfuzzer driver flag test Modified: cfe/trunk/test/Driver/fuzzer.c Modified: cfe/trunk/test/Driver/fuzzer.c URL: htt

<    1   2   3   4   5