|
|
|
| R2012a Documentation → Polyspace | |
Learn more about Polyspace |
|
| Contents | Index |
This table summarizes what's new in V5.4 (R2009b):
| New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems |
|---|---|---|
| Yes Details below | Yes—Details labeled as Compatibility Considerations, below. See also Summary. | Includes fixes: Polyspace Client for Ada Bug Reports Polyspace Server for Ada Bug Reports Polyspace Model Link SL Bug Reports Polyspace Model Link TL Bug Reports Polyspace UML Link RH Bug Reports |
New features and changes introduced in this version are organized by product:
New Report Generator that presents Polyspace results in PDF, HTML, and other output formats.
The Polyspace Report Generator allows you to generate reports about your verification results, using the following predefined report templates:
Coding Rules Report – Provides information about compliance with MISRA-C Coding Rules, as well as Polyspace configuration settings for the verification.
Developer Report – Provides information useful to developers, including summary results, detailed lists of red, orange, and gray checks, and Polyspace configuration settings for the verification.
Developer with Green Checks Report – Provides the same content as the Developer Report, but also includes a detailed list of green checks.
Quality Report – Provides information useful to quality engineers, including summary results, statistics about the code, graphs showing distributions of checks per file, and Polyspace configuration settings for the verification.
The Polyspace Report Generator allows you to generate verification reports in the following formats:
HTML
RTF
Microsoft Word
XML
For more information, see Generating Reports of Verification Results in the Polyspace Products for Ada User's Guide .
Enhanced main generator that considers the scope of a procedure and variable, improving error detection at the package level.
This change may affect your results compared with previous releases, and how you interpret the new results. Specific changes include:
Uninitialized package body variables are considered uninitialized
Uncalled package-scope procedures/functions are considered unreachable
Functions/procedures declared at the spec level are called only once
Uninitialized spec level variables are considered possibly uninitialized
For more information on the main generator, see Main Generator Overview in the Polyspace Products for Ada User's Guide .
Uninitialized Package Body Variables are Considered Uninitialized. Uninitialized variables that are declared only in the package body are now considered uninitialized, and generate red NIV checks.
Previously, these variables were considered initialized (green NIV) with full-range values. This behaviour made interpretation of results easier and allowed verification to continue. However, the software now considers these variables uninitialized (red NIV) and stops verification at this point. This new behaviour is more accurate with respect to the actual initialization state of the variables. You must correct the code before verification can continue. Alternatively, you can use the option -continue-with-all-niv.
Uncalled Package-scope Procedures/Functions are Considered Unreachable. Procedures and functions that are declared in the package but not called by code within the package body provided for the verification will now be considered unreachable (gray).
Previously, all procedures and functions in a package were considered for verification and subsequently colored. The argument for this behavior was that these functions and procedures could be called by code inside the package that had not been provided for the verification. Now, the software considers this code unreachable (gray) unless there is a path of execution that leads to it.
Functions/Procedures Declared at the Spec Level are Called Only Once. Functions or procedures declared at the specification level are called only once.
Note This behavior changed in Release 2010a. In R2010a or later, the main generator can call a function several times. |
Uninitialized Spec Level Variables are Considered Possibly Uninitialized. Uninitialized variables declared in a package specification will now be considered possibly uninitialized (orange NIV). Previously, these variables were considered initialized (green NIV) with full-range values.
The software now considers uninitialized variables that are declared only in the package body as uninitialized (red NIV). However, for uninitialized variables declared in a package specification, it is possible that packages that use these variables may initialize these variables. The software now recognizes this possibility and generates orange NIV checks for uninitialized variables declared in a package specification.
This behavior is not changed if you use options -init-stubbing-vars-random or -init-stubbing-vars-zero-or-random to initialize uninitialized variables. Specification-level variables will still be considered possibly uninitialized (orange NIV), because the packages that use these variables can alter the variables, even to the extent of uninitializing the variables.
Compatibility Considerations. Changes to the main generator may result in differences in your verification results, when compared with earlier versions of the software. If you verified your code with previous versions of the software (for example, R2009a), be aware of these changes, how they affect your colored results and the way you interpret the results.
New Graphs (similar to concurrent access graphs) available for all global data.
You can display the access sequence for any variable that is read or written in the code. The access graph displays the read and write access for the variable.
For more information, see Displaying the Access Graph for Variables in the Polyspace Products for Ada User's Guide .
New option to create a separate verification job for each source file in the project.
When you run a unit-by-unit verification, each source file is compiled, sent to the Polyspace Server, and verified individually.
The queue manager displays a job for the full verification group, as well as jobs for each unit (using a tree structure).
When verification is complete, you can download and view results for the entire project, or for individual units. When downloading a verification group, all the unit results are downloaded and a summary of the download status for each unit is displayed.
For more information, see Running Verification Unit-by-Unit in the Polyspace Products for Ada Reference.
Added support for Windows Server 2008.
For more information, see the Polyspace Installation Guide.
Added support for Windows Server 2008.
For more information, see the Polyspace Installation Guide.
Added support for Simulink Version 7.4 (R2009b).
 | Version 7.1 (R2009b) Polyspace for C/C++ Products | Version 7.0 (R2009a) Polyspace for C/C++ Products |  |
| © 1984-2012- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |