summaryrefslogtreecommitdiffstats
path: root/clang/tools/scan-build-py
diff options
context:
space:
mode:
authorPetr Hosek <phosek@chromium.org>2017-07-19 00:29:41 +0000
committerPetr Hosek <phosek@chromium.org>2017-07-19 00:29:41 +0000
commit5518d189ee8c87f3cf24dd09b944eb286fd5c202 (patch)
treeb37f7ae8804ab5cf0c5f0f69888be3c6416b60a9 /clang/tools/scan-build-py
parent5649b0e8c934b2680ba353c748b996339671388d (diff)
downloadbcm5719-llvm-5518d189ee8c87f3cf24dd09b944eb286fd5c202.tar.gz
bcm5719-llvm-5518d189ee8c87f3cf24dd09b944eb286fd5c202.zip
[scan-build-py] Patch to fix "-analyzer-config" option
I noticed that when I use "-analyze-config" option in scan-build-py, it behaves differently from original perl based scan-build. For example, command: $ scan-build -analyzer-config ipa=basic-inlining make Will work without any issues on perl version of scan-build. But on scan-build-py it will throw an error message "error reading 'ipa=basic-inlining'". After debugging, it turns out that the scan-build-py does not put "-analyzer-config" flag in front of the analyzer config flags (in this case is the "ipa=basic-inlining") in the final clang command line. This patch fixes this issue. Patch by Haowei Wu Differential Revision: https://reviews.llvm.org/D34489 llvm-svn: 308401
Diffstat (limited to 'clang/tools/scan-build-py')
-rw-r--r--clang/tools/scan-build-py/libscanbuild/analyze.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/clang/tools/scan-build-py/libscanbuild/analyze.py b/clang/tools/scan-build-py/libscanbuild/analyze.py
index a09c72389d7..b5614b5b6da 100644
--- a/clang/tools/scan-build-py/libscanbuild/analyze.py
+++ b/clang/tools/scan-build-py/libscanbuild/analyze.py
@@ -249,7 +249,7 @@ def analyzer_params(args):
if args.output_format:
result.append('-analyzer-output={0}'.format(args.output_format))
if args.analyzer_config:
- result.append(args.analyzer_config)
+ result.extend(['-analyzer-config', args.analyzer_config])
if args.verbose >= 4:
result.append('-analyzer-display-progress')
if args.plugins:
OpenPOWER on IntegriCloud