RuleChecker release 15.10

This release was only available as an integral part of Astrée 15.10.

General improvements

• For easier configuration and better understanding, all rules and checks have been merged into a single view. For each rule, you can now see all the checks used by it. When enabling or disabling some aspect of a rule by toggling a check, you immediately see which other rules are affected.
• The list of pre-defined filters in the Configuration view has been extended by the rule categories of MISRA C and MISRA AC AGC (Mandatory, Advisory, Obligatory, Readability,…).
• Header files are now only checked in contexts in which they are actually included while preprocessing. This fixes unjustified warnings about preprocessing problems in rule checking.
• Fixed import of a partial list of rule checks from an options file so that already configured rules are no longer overwritten.
• Improved Settings view, with a uniform look and feel for all configuration items and a filtering mechanism for faster lookup of specific options, rules or settings.

MISRA-C:2004

• Added support for rule 16.10.
• Improved precision for rule 13.6 to eliminate false alarms.
• For violations of 19.15, the analyzer now reports the exact line where a file is included twice.
• The check for rule 13.3 has been refined and now also takes several patterns of indirect equality tests into account.
• Improved precision to eliminate false alarms about violations of rule 8.9.
• Fixed rare false alarms for rule 19.15.
• Improved coverage of rule 18.4 by adding a check that warns about union objects.

MISRA-C:2012

• Added partial support for rule 8.13.
• Corrected check for rule 2.5. Macros defined in the preprocessor settings are no longer subject to the rule check unused-macro.
• For violations of Dir. 4.10., the analyzer now reports the exact line where a file is included twice.
• Improved coverage of rule 19.2 by adding a check that warns about union objects.

DAX configuration

• Improved the rule checker configuration in DAX files. Instead of using the now-deprecated "rules" and "checks" options, they can now be specified in a new <rulechecks> section as shown in the example below:

  <dax version="1.1">
    <options>
      <rulechecks>yes</rulechecks>
    </options>
  
    <rulechecks>
        <checks enable="all">
            <array-index>no</array-index>
        </checks>
        <rules enable="none">
          <M04>yes</M04>
          <M04.12.1>no</M04.12>
        </rules>
      </rulechecks>
  </dax>

  Additional values can be passed where needed using the following syntax:

  <dax version="1.1">
    <rulechecks>
      <rules enable="none">
        <M2012.6.1 value="char;int">yes</M2012.6.1>
      </rules>
    </rulechecks>
  </dax>

• The different kinds of analysis settings (options, ABI, etc.) can now be imported from and exported to the DAX format. Files with analysis settings in old formats (.opt, .abi, etc) can still be imported but are no longer exported by the GUI. For options and rules, the new DAX export allows either a full export of all options and rules or alternatively the export of only those options and rules that have been explicitly modified, i.e. that deviate from the tool’s default settings.