La traducción de esta página aún no se ha actualizado a la versión más reciente. Haga clic aquí para ver la última versión en inglés.

Opciones solo de línea de comandos

Opciones solo de línea de comandos, opciones avanzadas

Estos análisis se utilizan en la línea de comandos DOS o UNIX^® con la función polyspace-bug-finder. Si desea utilizar algunas de las configuraciones avanzadas con un proyecto en la interfaz de usuario, utilice la opción de configuración Other.

Opciones de Polyspace

expandir todo

Básica

`-author`	Specify project author
`-c`	Specify path of license file used by the product
`-consider-switch-as-single-decision`	Compute cyclomatic complexity assuming a switch-case statement to be a single decision point
`-checkers-activation-file`	Activate a custom combination of defects and coding rules for a Polyspace Bug Finder analysis (Desde R2021a)
`-date`	Specify date of analysis
`-doc \| -documentation`	Display Polyspace documentation in web browser
`-h \| -help`	Display list of possible options
`-I`	Specify include folder for compilation
`-import-comments`	Import review information from previous analysis
`-list-all-values`	Display valid option arguments for a given command-line option
`-options-file`	Run Polyspace using list of options
`-prog`	Specify name of project
`-report-output-name`	Specify name of report
`-results-dir`	Specify the results folder
`-scheduler`	Specify cluster or job scheduler
`-sources`	Specify source files
`-sources-list-file`	Specify file containing list of sources
`-start-level-from-one`	Start counting the call level or nesting level from one.
`-ver`	Display system information for Polyspace products
`-verif-version`	Assign a version identifier
`-v \| -version`	Display Polyspace version number

Avanzada

`-asm-begin -asm-end`	Exclude compiler-specific `asm` functions from analysis
`-classification`	Control precisely which files to include in Polyspace analysis and how to analyze them (Desde R2023a)
`-code-behavior-specifications`	Associate behaviors with code elements such as functions
`-consider-analysis-perimeter-as-trust-boundary`	Consider the analysis perimeter as trust boundary so that data coming from outside the current analysis perimeter is considered tainted
`-create-checkers`	Create new checkers for Polyspace Bug Finder analysis (Desde R2023b)
`-custom-target`	Create a custom target processor with specific data type sizes
`-disable-concurrency-detection`	Disable automatic detection of multitasking functions
`-detect-atomic-data-race`	Enable detecting data race with atomic operation
`-detect-bad-float-op-on-zero`	Detect floating point comparison with equality operator when one of the operand is `0.0`
`-dump-preprocessing-info`	Show all macros implicitly defined during a particular analysis
`-ignore-code-annotations`	Ignore C/C++ code annotations justifying Polyspace results and show all results as unreviewed (Desde R2022a)
`-incremental`	Enable incremental compilation during an analysis (Desde R2022a)
`-max-processes`	Specify maximum number of processors for analysis
`-non-preemptable-tasks`	Specify functions that represent nonpreemptable tasks
`-no-credentials-check`	Disable credential check when running Polyspace Bug Finder or Polyspace Code Prover analysis on a remote cluster
`-options-for-sources`	Specify analysis options specific to a source file
`-preemptable-interrupts`	Specify functions that represent preemptable interrupts
`-pstunit-test`	Option to specify a test the input of which is used for static analysis
`-regex-replace-rgx -regex-replace-fmt`	Make replacements in preprocessor directives
`-submit-job-from-previous-compilation-results`	Specify that the analysis job must be resubmitted without recompilation
`-termination-functions`	Specify process termination functions
`-tmp-dir-in-results-dir`	Keep temporary files in results folder
`-wchar-t-is`	Specify the nature of type specifier `wchar_t` for your compiler
`-xml-annotations-description`	Apply custom code annotations to Polyspace analysis results