CodeSonar Release 4.0 patchlevel 1: Release Notes

JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.

If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.

If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.

If you access the manual through the hub's Web GUI, the functionality will not be suppressed because the hub is a web server.
Alternatively, your browser may allow you to explicitly disable the security setting that suppresses functionality. See the CodeSonar FAQ for more information.

CodeSonar Release 4.0, patchlevel 1: Release Notes

ABI keys	CodeSonar now supports associating ABI keys with compilation units
Configuration Parameters	Modifications to three existing parameters.
Configuration Files	Changes to naming scheme and creation mechanism for compiler-specific configuration files and naming scheme for compiler templates.
Front-end Options	New front-end options --cs_model_abi_key and --cs_user_abi_key, both associated with the new ABI key support.
Problems Fixed	Several problems are fixed in this release.

ABI keys

CodeSonar now supports associating ABI keys with compilation units

Configuration Parameters

Modifications to three existing parameters.

Configuration Files

Changes to naming scheme and creation mechanism for compiler-specific configuration files and naming scheme for compiler templates.

Front-end Options

New front-end options --cs_model_abi_key and --cs_user_abi_key, both associated with the new ABI key support.

Problems Fixed

Several problems are fixed in this release.

CodeSonar now supports associating ABI keys with compilation units.

There are three mechanisms for associating an ABI key with a compilation unit.

Using a COMPILER_MODELS rule that specifies an ABI key for all compilation units compiled with a particular compiler.
Specifying a key with front end option --cs_user_abi_key.
Using a compiler model that passes front end option --cs_model_abi_key.

When an ABI key is associated with a compilation unit using the COMPILER_MODELS approach (but not when using a front end option directly), the project-compiler configuration file loaded during the CodeSonar parse phase will include the ABI key in its name. This allows users to specify different configuration settings for different ABIs.

CodeSonar will prefer to link compilation units with the same ABI key when constructing the CodeSonar project.

Keys are user-specified, and will only be used within CodeSonar. We recommend using keys that do not conflict with the set of compiler model names.

When a single source file is compiled multiple times with different ABI keys, one instance will be kept for each key.

There are changes to three existing parameters. See Upgrading Configuration Files for upgrade instructions and patches.

Parameter	Changes
COMPILER_MODELS	Rules can now specify full or partial paths to compiler executables (previously they could only specify executable basenames). Rules can also additionally specify an ABI key to be associated with all compilation units compiled with the specified executable.
DISABLED_COMPILERS	Rules can now specify full or partial paths to compiler executables (previously they could only specify executable basenames).
FORCE_ENVIRONMENT	Factory setting is now Yes (previously it was No); environment forcing no longer takes environment variable CS_ENVIRON into account.

Parameter

Changes

COMPILER_MODELS

Rules can now specify full or partial paths to compiler executables (previously they could only specify executable basenames). Rules can also additionally specify an ABI key to be associated with all compilation units compiled with the specified executable.

DISABLED_COMPILERS

Rules can now specify full or partial paths to compiler executables (previously they could only specify executable basenames).

FORCE_ENVIRONMENT

Factory setting is now Yes (previously it was No); environment forcing no longer takes environment variable CS_ENVIRON into account.

Previously, all project-compiler configuration files had names of the form projname.C.L.S.conf.

The naming scheme now depends on whether there is a COMPILER_MODELS mapping that associates the compiler C with an ABI key A.

If so, CodeSonar will use a project-compiler configuration file with a name of the form projname.C.A.L.S.conf. If this file doesn't exist, CodeSonar will create it from a compiler template. The compiler template used will be the first of the following that is available in the $CSONAR/csurf/compiler_confs/ directory.

C.A.L.S.conf
C.L.S.conf
unknown.A.L.S.conf
unknown.L.S.conf

If none of these are available, no project-compiler configuration file is created or used.

If not, CodeSonar will use a project-compiler configuration file with a name of the form projname.C.L.S.conf, as previously.

The following problems are fixed in this release.

FIXED: Hubs would not start on Windows machines if running with Windows logins containing non-ascii characters.

FIXED: A failing SOURCE_REPLACE_COMMAND setting could cause source files to be deleted

FIXED: Crashes in incremental analysis.