1.5.36. Migration to 7.7.0¶
1.5.36.1. Compiler¶
The compiler option language_cxx.features.no_parse_templates (previously a boolean)
has been replaced by the option language_cxx.features.parse_templates, an enum
with four possible values:
automatic (new default)
standard (equivalent to old default behavior with
no_parse_templates=false)deferred
never (equivalent to old behavior with
no_parse_templates=true)
Existing JSON configurations are automatically migrated (no_parse_templates=true ->
“never”; no_parse_templates=false -> “automatic”).
If you are manually specifying --no_parse_templates on the command line,
we recommend switching to the new “deferred” mode.
It preserves more source code information in the IR than the “never” mode,
which helps avoid false negatives in various stylechecks.
Note that the default has switched from “standard” to “automatic”. This change only
impacts permissive Microsoft mode (without the /permissive- switch), as otherwise
“automatic” is equivalent to “standard”. This change better emulates the behavior
of the Microsoft compiler.
1.5.36.2. CMakeIntegration¶
The default generator has changed from Unix Makefiles to Ninja. If you
relied on the default settings but want to use Unix Makefiles, you must now
configure that explicitly.
1.5.36.3. IR¶
In the logical IR, the class Adjusted_Parameter was removed.
Such parameters now use the class Normal_Parameter instead.
The field Promoted_Type is now available in Normal_Parameter
and replaces the field Adjusted_Parameter.Link_Type.
1.5.36.4. Stylechecks¶
The option exclude_in_macro (which was available on most stylecheck rules)
has been removed.
If you were using this option, consider switching to the less aggressive
extend_exclude_to_macro_invocations instead.
Existing JSON configurations are automatically migrated: if exclude_in_macro was
enabled, "*" will be added to the exclude_in_macros option.
This maintains the previous behavior of ignoring any violations associated with macro expansion.
MisraC++2023¶
Previous MisraC++202x rules have been updated to the upcoming MisraC++2023 rules.
AutosarC++-A7.3.1¶
Rule AutosarC++-A7.3.1 is now stricter regarding hidden base methods that are not hidden via using. The rule now corresponds to the upcoming rule MisraC++2023-3.4.2.
AutosarC++-A3.3.2¶
The option allowed_effects_mask has been removed as it was difficult to use sensibly.
As a replacement, a new option allowed_effects is provided. Configurations using
allowed_effects_mask must be updated accordingly.
Out-of-bounds checks¶
Rules checking for out-of-bounds array access, or for pointer arithmetic on non-array types, now report multiple violations at the same location more consistently. This may result in added or removed findings where you already received at least one message from these checks; this primarily affects violations involving pointer arithmetic on non-array pointer targets.
1.5.36.5. StaticSemanticAnalysis¶
The option advanced.use_conditional_value_propagation has been removed as it is no
longer needed. If this option is present in
your configuration files, simply remove any occurrence of it.
1.5.36.6. Dashboard¶
The web user interface now uses the server time zone to display timestamps by default. Users who access a Dashboard server from a different time zone may wish to change their preferences to use their local time zone.
1.5.36.7. Python¶
Previously, it was possible to start the Python scripts inside the bin folder of
the Axivion Suite with a Python 2.7 interpreter, which then invoked the proper Python 3
interpreter. This was possible because the Python scripts in
bin maintained Python 2.7 syntax compatibility. This constraint has been
removed, and Python
scripts inside bin are no longer guaranteed to be
compatible with Python 2.7 syntax.
It is recommended not to run the Python scripts from the bin folder directly,
but to use their counterparts instead: the executable files (.exe suffix on
Windows) and the shell scripts (without any suffix on GNU/Linux and macOS). Since
binaries can be invoked on
Windows without the
.exe suffix, you can always
use axivion_ci instead of
axivion_ci.py or axivion_ci.exe.
1.5.36.8. convert_sln2proj¶
The script convert_sln2proj has been removed as it has not been required for
some time:
MSBuildIntegration supports solutions with ProjectDependencies (solution-level
build-order dependencies), eliminating the need for convert_sln2proj.