GNU Compiler Models

There are two GNU compiler models: gcc and gpp.

• Overview
• Availability
• Model-Specific ABI Key Format
• Command Arguments
• Predefined Macros and Include Paths

Overview

The following file extensions are supported:

Availability

For full details of all native compilers recognized by CodeSonar by default, see section Compilers Recognized by CodeSonar.

Model-Specific ABI Key Format

The model-specific ABI key format for the gcc and gpp compiler models is:

as

If an ABI key with this format is specified for a compilation that is modeled with the gcc or gpp compiler model, the following settings will be applied.

• The target pointer size will be initially set to <pointer_size>. Command arguments may cause subsequent changes from this setting.
• The GNU version will be set to <gcc_version>. This takes precedence over any other mechanism for determining GNU version.
• If <gnu_mode> is zero, 'GNU mode' is disabled:
  • front end options --gcc and --g++ are not automatically specified.
  • --gcc89_inlining is not specified even if -fgnu89-inline is specified.
• If <gcc_invoke> is zero, gcc will not be invoked to determine predefined macros and include paths.
• The project-compiler configuration file applied to the compilation will have a name based on the key (this is the only contribution of the optional .<user_string> component of the key).

Example

Suppose we are building a CodeSonar project where:

• The configuration file includes the following rule.

  COMPILER_MODELS += mycc -> gcc:32.30303.1.0
  

• The underlying software build command is
  mycc -c myfile.c

Then the mycc compilation will be modeled by the gcc compiler model, with the following settings.

• 32-bit target
• gcc version 3.3.3
• GNU mode enabled (--gcc will be specified; --g++ will be specified but ignored)
• gcc will not be invoked to determine predefined macros and include paths.

For more information, see Compiler Models: ABI Keys.

Command Arguments

The following command arguments are interpreted by the gcc and gpp compiler models. Arguments are passed to the gcc invocation that determines predefined macros and include paths unless otherwise noted.

Compilation Mode

The modeled compilation mode is determined as follows.

• If command argument -x lang is specified, the modeled compilation mode will depend on lang as follows.

  lang	Modeled compilation mode
  c cpp-output	C mode
  c++ c++-cpp-output	C++ mode
  none	The model will determine the mode from the source file extension.
  other lang	CodeSonar will ignore the compilation.

• Otherwise, the modeled compilation mode determination depends on the model:

  gcc	mode is determined from the source file extension.
  gpp	mode is always C++.

In some cases, the modeled effect of individual command arguments is mode-dependent. These cases are noted in the table above.

C and C++ Standards

The gcc and gpp models have some behaviors that depend on the determined C++ standard, but do not make use of the determined C standard. However, some compiler models based on the gcc model (in particular, the Clang compiler models) make use of both.

The applicable C or C++ standard for the modeled compilation is determined as follows.

• If -std arg is specified, the applicable C or C++ standard is determined by the value of arg.

  arg	Standard
  	C	C++
  c89	C89	-
  c90 iso9899:1990 iso9899:199409 gnu89 gnu90	C90	-
  c99 c9x gnu99 gnu9x iso9899:1999 iso9899:199x	C99	-
  c11 c1x gnu11 gnu1x	C11	-
  c17 c18 gnu17 gnu18 iso9899:2017 iso9899:2018 c2x	C18	-
  c++98 gnu++98	-	C++98
  c++03 gnu++03	-	C++03
  c++0x gnu++0x	-	C++0x
  c++11 gnu++11	-	C++11
  c++14 c++1y gnu++14 gnu++1y	-	C++14
  c++17 c++1z gnu++17 gnu++1z	-	C++17
  c++20 c++2a gnu++20 gnu++2a	-	C++20
  other arg	-	-

• Otherwise, the applicable standard is based on the GNU version determined by the model.

  C standard	C11 if GNU version is 5.1 or later,	C89 otherwise
  C++ standard	C++14 if GNU version is 6.0 or later,	C++98 otherwise

Note on -D, -U evaluation order

The evaluation order for -D and -U instances on the command line depends on the version being used.

No CodeSonar Build

If any of the following are specified, CodeSonar will ignore the compilation and will not generate any corresponding internal representation. If a CodeSonar project is based only on ignored compilations, it will have no contents and so will not be finalized.

Predefined Macros and Include Paths

By default, the gcc and gpp compiler models invoke the modeled native compiler to extract the location of its configuration files, and use this to set up the include path and predefined macros.

These native compiler invocations can be specifically disabled using a special-format ABI key.

Additional predefined macros and include paths are listed below.