diff options
Diffstat (limited to 'clang/tools/scan-build-py')
| -rw-r--r-- | clang/tools/scan-build-py/README.md | 6 | ||||
| -rw-r--r-- | clang/tools/scan-build-py/libscanbuild/analyze.py | 4 | ||||
| -rw-r--r-- | clang/tools/scan-build-py/libscanbuild/arguments.py | 2 |
3 files changed, 6 insertions, 6 deletions
diff --git a/clang/tools/scan-build-py/README.md b/clang/tools/scan-build-py/README.md index 1b6fc488fa2..720bde1cf3b 100644 --- a/clang/tools/scan-build-py/README.md +++ b/clang/tools/scan-build-py/README.md @@ -84,11 +84,11 @@ tool has three distinct model to run the analyzer: This is the default behaviour, can be enforced with `--override-compiler` flag. -2. Use special library to intercept compiler calls durring the build process. +2. Use special library to intercept compiler calls during the build process. The analyzer run against each modules after the build finished. Use `--intercept-first` flag to get this model. -3. Use compiler wrappers to intercept compiler calls durring the build process. +3. Use compiler wrappers to intercept compiler calls during the build process. The analyzer run against each modules after the build finished. Use `--intercept-first` and `--override-compiler` flags together to get this model. @@ -105,7 +105,7 @@ process removes removes intermediate modules (generated sources) the analyzer output still kept. The 2. and 3. generate the compilation database first, and filters out those -modules which are not exists. So, it's suitable for incremental analysis durring +modules which are not exists. So, it's suitable for incremental analysis during the development. The 2. mode is available only on FreeBSD and Linux. Where library preload diff --git a/clang/tools/scan-build-py/libscanbuild/analyze.py b/clang/tools/scan-build-py/libscanbuild/analyze.py index 3c93b114051..5a7cc20a517 100644 --- a/clang/tools/scan-build-py/libscanbuild/analyze.py +++ b/clang/tools/scan-build-py/libscanbuild/analyze.py @@ -94,7 +94,7 @@ def need_analyzer(args): When static analyzer run against project configure step, it should be silent and no need to run the analyzer or generate report. - To run `scan-build` against the configure step might be neccessary, + To run `scan-build` against the configure step might be necessary, when compiler wrappers are used. That's the moment when build setup check the compiler and capture the location for the build process. """ @@ -437,7 +437,7 @@ def run(opts): of the compilation database. This complex task is decomposed into smaller methods which are calling - each other in chain. If the analyzis is not possibe the given method + each other in chain. If the analyzis is not possible the given method just return and break the chain. The passed parameter is a python dictionary. Each method first check diff --git a/clang/tools/scan-build-py/libscanbuild/arguments.py b/clang/tools/scan-build-py/libscanbuild/arguments.py index 00679a45937..a5d0c6bda66 100644 --- a/clang/tools/scan-build-py/libscanbuild/arguments.py +++ b/clang/tools/scan-build-py/libscanbuild/arguments.py @@ -281,7 +281,7 @@ def create_analyze_parser(from_build_command): '-maxloop', metavar='<loop count>', type=int, - help="""Specifiy the number of times a block can be visited before + help="""Specify the number of times a block can be visited before giving up. Increase for more comprehensive coverage at a cost of speed.""") advanced.add_argument( |
