Searched full:analysis (Results 1 – 25 of 82) sorted by relevance
1234
3 GCC static analysis support6 Static analysis was introduced in `GCC <https://gcc.gnu.org/>`__ 10 and it is enabled8 analysis of the code than traditional warnings.10 Run GCC static analysis13 To run GCC static analysis, :ref:`west build <west-building>` should be
6 `CodeChecker <https://codechecker.readthedocs.io/>`__ is a static analysis infrastructure.7 It executes analysis tools available on the build system, such as45 - The number of threads to use in analysis. (default: <CPU count>)59 during analysis.63 - Skip parsing the analysis, useful if you simply want to store the results.65 - Run the ``store`` command after analysis.72 - Trim the defined path from the analysis results, e.g. ``/home/user/zephyrproject``.
3 Static Code Analysis (SCA)6 Support for static code analysis tools in Zephyr is possible through CMake.13 to enable the static analysis tool ``sparse``.
7 is a static code analysis tool.8 Apart from performing common code analysis tasks it also supports an
7 static analysis tool and platform for software verification.30 This will only invoke the ECLAIR analysis with the predefined ruleset ``first_analysis``. If you
7 and static analysis tool for C and C++. It is a commercial software and you must acquire a
22 * thread analysis.54 * Callback function with thread analysis information.56 * @param info Thread analysis information.
3 * Stack usage analysis helpers
21 analysis:22 name: Scorecard analysis36 - name: "Run analysis"
33 "section": "Static Analysis",
28 prompt "Thread analysis print mode"56 bool "Run analysis with interrupts unlocked"59 The thread analysis takes quite a long time.75 bool "Run periodic thread analysis in a thread"79 Thread analysis would be called periodically.93 int "Thread analysis interval"100 int "Stack size for the periodic thread analysis thread"
4 # The aim of this file is to define the analysis configuration for <RULESET>.
131 * Responsibility to triage static analysis issues in their code area.180 Static Analysis Audit Team183 The Static Analysis Audit team works closely with the release engineering184 team to ensure that static analysis defects opened during a release188 * Right to revert any triage in a static analysis tool (e.g: Coverity)194 Joining the Static Analysis Audit team197 in static analysis.403 * Static Analysis (Coverity)
22 -eval_file=@ECLAIR_ECL_DIR@/analysis.ecl
117 # call which calls the compiler and to generate analysis files.124 # elf file was generated with this we cane make sure that the analysis is completed.
10 The analysis is performed on demand when the application calls80 The time for which the module sleeps between consecutive printing of thread analysis in automatic
37 '''Get the bugs to use for analysis, given command line arguments.'''
19 /* Static code analysis tool can raise a violation
15 # - SCA_ROOT: CMake list of SCA roots containing static code analysis integration code
17 * leak confidential data due to analysis of micro-architectural properties.
15 external system for analysis. The monitoring can be setup either manually48 for analysis.
