summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/anonymous-struct/main.cpp
diff options
context:
space:
mode:
authorGeorge Karpenkov <ekarpenkov@apple.com>2018-02-26 22:14:16 +0000
committerGeorge Karpenkov <ekarpenkov@apple.com>2018-02-26 22:14:16 +0000
commit1d3e49e781a38bf9e2efd5ed9e001f92602e5552 (patch)
tree54e785e981a6ec941051d6651a16ddbb7e8c91a6 /lldb/packages/Python/lldbsuite/test/expression_command/anonymous-struct/main.cpp
parent24f9794d78d54f659fd6760be6f8f0289e46ef3f (diff)
downloadbcm5719-llvm-1d3e49e781a38bf9e2efd5ed9e001f92602e5552.tar.gz
bcm5719-llvm-1d3e49e781a38bf9e2efd5ed9e001f92602e5552.zip
[analyzer] Do not analyze bison-generated files
Bison/YACC generated files result in a very large number of (presumably) false positives from the analyzer. These false positives are "true" in a sense of the information analyzer sees: assuming that the lexer can return any token at any point a number of uninitialized reads does occur. (naturally, the analyzer can not capture a complex invariant that certain tokens can only occur under certain conditions). Current fix simply stops analysis on those files. I have examined a very large number of such auto-generated files, and they do all start with such a comment. Conversely, user code is very unlikely to contain such a comment. rdar://33608161 Differential Revision: https://reviews.llvm.org/D43421 llvm-svn: 326135
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/anonymous-struct/main.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud