4 TOOL OPTIONS

This chapter contains the following sections:

Compiler Options

Assembler Options

Linker Options

Control Program Options

Make Utility Options

Archiver Options

4.1 Compiler Options

This section lists all compiler options.

Options in EDE versus options on the command line

Most command line options have an equivalent option in EDE but some options are only available on the command line. If there is no equivalent option in EDE, you can specify a command line option in EDE as follows:

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Miscellaneous.

3. Enter one or more command line options in the Additional options field.

Be aware that some command line options are not useful in EDE or just do not have any effect. For example, the option -n sends output to stdout instead of a file and has no effect in EDE.

Short and long option names

Options have both short and long names. Short option names always begin with a single minus (-) character, long option names always begin with two minus (--) characters. You can abbreviate long option names as long as it forms a unique name. You can mix short and long option names on the command line.

Options can have flags or suboptions. To switch a flag 'on', use a lowercase letter or a +longflag. To switch a flag off, use an uppercase letter or a -longflag. Separate longflags with commas. The following two invocations are equivalent:

When you do not specify an option, a default value may become active.

-? (--help)

EDE

-

Command line syntax

Description

Displays an overview of all command line options.

Example

The following invocations all display a list of the available command line options:

Related information

-

-A (--language)

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Language.

3. Enable or disable the options Allow language extension keywords and Allow C++ style comments in ISO C90 mode.

Command line syntax

You can set the following flags:

Default

Description

With this option you control the language extensions the compiler can accept. Default the TriCore C compiler allows all language extensions.

-A is the equivalent of -AKP and disables all language extensions.

With -Ak you tell the compiler to allow language extension keywords, such as __fract. Use -AK to tell the compiler to generate a syntax error when it finds a language extension keyword in your C source.

With -Ap you tell the compiler to allow C++ style comments (//) in ISO C90 mode (option -c90). In ISO C99 mode this style of comments is always accepted.

Example

The compiler compiles in ISO C90 mode, accepts keywords but ignores C++ style comments.

Related information

Compiler option -c (ISO C standard)

--align

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Miscellaneous.

3. Add the option --align to the Additional options field.

Command line syntax

Default

Description

By default the TriCore compiler aligns objects to the minimum alignment required by the architecture. With this option you can increase this alignment for objects of four bytes or larger. The value must be a power of two.

Example

To align all objects of four bytes or larger on a 4-byte boundary, enter:

Instead of this option you can also specify the following pragma in your C source:

With #pragma align restore you can return to the previous alignment setting.

Related information

Section 3.7 , Controlling the Compiler: Pragmas, in Chapter TriCore C Language of the TriCore User's Guide.

-C (--cpu)

EDE

1. From the Project menu, select Project Options...

2. Expand the Processor entry and select Processor Definition.

3. In the Target processor list select the target processor.

Command line syntax

Description

With this option you define the target processor for which you create your application.

Based on the target processor the compiler automatically detects whether a FPU-unit is present and whether the architecture is a TriCore2. This means you do not have to specify the compiler options --fpu-present and --is-tricore2 explicitly when one of the supported derivatives is selected.

The compiler automatically includes the register file regcpu.sfr, unless you specify compiler option --no-tasking-sfr.

Example

In EDE, the target CPU has the following settings:

To define this on the command line:

The compiler compiles test.c for the TC10GP processor and includes the register file regtc10gp.sfr.

To avoid conflicts, make sure you specify the same target processor to the assembler.

Related information

Compiler option --no-tasking-sfr (Do not include SFR file)

Assembler option -C (Select CPU)
Control program option -C (Use SFR definitions for CPU)

Section 5.5, Specifying a Target Processor, in Chapter Using the Compiler of the User's Guide.

-c (--iso)

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Language.

3. Select the ISO C standard C90 or C99.

Command line syntax

Default

Description

With this option you select the ISO C standard. C90 is also referred to as the "ANSI C standard". C99 refers to the newer ISO/IEC 9899:1999 (E) standard. C99 is the default.

Example

To select the ISO C90 standard on the command line:

Related information

Compiler option -A (Language extensions)

--cse-all-addresses

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Miscellaneous.

3. Add the option --cse-all-addresses to the Additional options field.

Command line syntax

Description

With this option you tell the compiler to make all addresses available for common subexpression evaluation.

Normally the compiler ignores __near and __ax addresses for common subexpressions. However, depending on the use of address registers and whether stack and/or addressed memory are internal or external, it might be wise to consider them for CSE.

Example

The compiler makes all addresses available for common subexpression evaluation.

Related information

Compiler option -Oc (Common subexpression elimination

-D (--define)

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Preprocessing.

3. Enter a macro name and/or definition in the Define user macros field.

Command line syntax

Description

With this option you can define a macro and specify it to the preprocessor. If you only specify a macro name (no macro definition), the macro expands as '1'.

You can specify as many macros as you like. In EDE, use commas to separate multiple macro definitions. On the command line, use the option -D multiple times. If the command line exceeds the limit of the operating system, you can define the macros in an option file which you then must specify to the compiler with the option -f file.

Defining macros with this option (instead of in the C source) is, for example, useful to compile conditional C source as shown in the example below.

Example

Consider the following C program with conditional code to compile a demo program and a real program:

You can now use a macro definition to set the DEMO flag:

Note that all four invocations have the same effect.

The next example shows how to define a macro with arguments. Note that the macro name and definition are placed between double quotes because otherwise the spaces would indicate a new option.

Related information

Compiler option -U (Undefine macro)
Compiler option -f (Specify an option file)

--diag

EDE

1. In the Help menu, enable the option Show Help on Tool Errors.

2. In the Build tab of the Output window, double-click on an error or warning message.

Command line syntax

Optionally, you can use one of the following display formats (format):

Description

With this option the compiler displays a description and explanation of the specified error message(s) on stdout (usually the screen). The compiler does not compile any files.

If you want the output in a file, you have to use output redirection.

Example

To display an explanation of message number 282, enter:

This results in the following message and explanation:

To write an explanation of all errors and warnings in HTML format to file cerrors.html, enter:

Related information

Section 5.9 , C Compiler Error Messages, in Chapter Using the Compiler of the User's Guide.

-E (--preprocess)

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Preprocessing.

3. Enable the option Store the C compiler preprocess output (<file>.pre).

4. Enable or disable the options Keep comments and Strip #line source position info.

Command line syntax

You can set the following flags (when you specify-E without flags, the default is -ECP):

Description

With this option you tell the compiler to preprocess the C source. EDE stores the preprocess output in the file name.pre (where name is the name of the C source file to compile). EDE also compiles the C source.

On the command line, the compiler sends the preprocessed file to stdout. To capture the information in a file, specify an output file with the option -o.

With -Ec you tell the preprocessor to keep the comments from the C source file in the preprocessed output.

With -Ep you tell the preprocessor to strip the #line source position information (lines starting with #line). These lines are normally processed by the assembler and not needed in the preprocessed output. When you leave these lines out, the output is more orderly to read.

Example

The compiler preprocesses the file test.c and sends the output to the file test.pre. Comments are included but the line source position information is not stripped from the output file.

Related information

-

--error-file

EDE

-

Command line syntax

Description

With this option the compiler redirects error messages to a file.

If you do not specify a filename, the error file will be named after the input file with extension .err.

Example

To write errors to errors.err instead of stderr, enter:

Related information

Compiler option --warnings-as-errors (Treat warnings as error)

-F (--no-double)

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Miscellaneous.

3. Enable the option Single precision floating point only.

Command line syntax

Description

With this option you tell the compiler to treat variables of the type double as float. Because the float type takes less space, execution speed increases and code size decreases, both at the cost of less precision.

Example

The file test.c is compiled where variables of the type double are treated as float.

Related information

-

-f (--option-file)

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Miscellaneous.

3. Add the option -f to the Addtional options field.


In EDE you can save your options in a file and restore them to call the compiler with those options:

1. From the Project menu, select Save Options... or Load Options...

Be aware that when you specify the option -f in the Additional options field, the options are added to the compiler options you have set in the Project Options dialog. Only in extraordinary cases you may want to use them in combination.

Command line syntax

Description

Instead of typing all options on the command line, you can create an option file which contains all options and files you want to specify. With this option you specify the option file to the compiler.

Use an option file when the length of the command line would exceed the limits of the operating system, or just to store options and save typing.

You can specify the option -f multiple times.

Format of an option file

     "This has a single quote ' embedded"
     'This has a double quote " embedded'
     'This has a double quote " and \
     a single quote '"' embedded"
     "This is a continuation \
     line"
          -> "This is a continuation line"

Example

Suppose the file myoptions contains the following lines:

Specify the option file to the compiler:

This is equivalent to the following command line:

Related information

-

--fpu-present

EDE

1. From the Project menu, select Project Options...

2. Expand the Processor entry and select Processor Definition.

3. In the Target processor list select a (user defined TriCore) option.

4. Enable the option FPU present (on user defined CPU).

5. Expand the C Compiler entry and select Miscellaneous.

6. Enable the option Use hardware single precision floating point instructions.

Command line syntax

Description

With this option the compiler can generate single precision floating point instructions in the assembly file. When you select this option, the macro _FPU is defined in the C source file.

Example

To allow the use of floating point unit (FPU) instructions in the assembly code, enter:

Related information

Compiler option -C (Use SFR definitions for CPU)

-g (--debug-info)

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Debug Information.

3. Enable the option Generate symbolic debug infomation

Command line syntax

Description

With this option you tell the compiler to add directives to the output file for including symbolic information. This facilitates high level debugging but increases code size. For the final application, compile your C files without debug information.

When you specify a high optimization level, the debug comfort may decrease. Therefore, the compiler issues warning W555 if the debug comfort would be decreased as a result of the chosen optimizations.

Example

To add symbolic debug information to the output file, enter:

Related information

-

-H (--include-file)

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Preprocessing.

3. Enter the name of the file in the Include this file before source field.

Command line syntax

Description

With this option you include one extra file at the beginning of each C source file, before other includes. This is the same as specifying #include "file" at the beginning of each of your C sources.

Example

The file stdio.h is included at the beginning of both test1.c and test2.c.

Related information

Compiler option -I (Add directory to include file search path)

Section 5.6, How the Compiler Searches Include Files, in Chapter Using the Compiler of the User's Guide.

-I (--include-directory)

EDE

1. From the Project menu, select Directories...

2. Enter one or more search paths in the Include Files Path field.

Command line syntax

Description

With this option you can specify the path where your include files are located. A relative path will be relative to the current directory.

The order in which the compiler searches for include files is:

1. The pathname in the C source file and the directory of the C source (only for #include files that are enclosed in "")

2. The path that is specified with this option.

3. The path that is specified in the environment variable CTCINC when the product was installed.

4. The default directory c:\ctc\include.

Example

Suppose that the C source file test.c contains the following lines:

You can call the compiler as follows:

First the compiler looks in the directory where test.c is located for the file myinc.h.

Then the compiler looks in the include subdirectory relative to the current directory for the stdio.h file and, if it was not found yet, also for the myinc.h file (this option).

If the file(s) are still not found, the compiler searches in the enviroenment variable and then in the default include directory.

Related information

Compiler option -H (Include this file at the start of a compilation)

Section 5.6, How the Compiler Searches Include Files, in Chapter Using the Compiler of the User's Guide.

Section 1.3.2, Configuring the Command Line Environment, in Chapter Software Installation of the User's Guide.

--indirect

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Miscellaneous.

3. Enable the option Call functions indirect.

Command line syntax

Description

With this option you tell the compiler to generate code for indirect function calling.

Example

The compiler generates far calls for all functions.

Related information

See also section 3.9.3 , Function Calling Modes: __indirect, in Chapter TriCore C Language of the User's Guide.

--inline-max-incr / --inline-max-size

EDE

-

Command line syntax

Default

Description

With these options you can control the function inlining optimization process of the compiler. These options have only effect when you have enabled the inlining optimization (option -Oi).

Regardless of the optimization process, the compiler always inlines all functions that have the function qualifier inline.

With the option --inline-max-size you can specify the maximum size of functions that the compiler inlines as part of the optimization process. The compiler always inlines all functions that are smaller than the specified threshold. The threshold is measured in compiler internal units and the compiler uses this measure to decide which functions are small enough to inline. The default threshold is 10.

After the compiler has inlined all functions that have the function qualifier inline and all functions that are smaller than the specified threshold, the compiler looks whether it can inline more functions without increasing the code size too much. With the option --inline-max-incr you can specify how much the code size is allowed to increase. Default, this is 25% which means that the compiler continues inlining functions until the resulting code size is 25% larger than the original size.

Example

The compiler first inlines all functions with the function qualifier inline and all functions that are smaller than the specified threshold of 15. If the code size has still not increased with 40%, the compiler decides which other functions it can inline.

Related information

Compiler option -O (Specify optimization level)

Section 3.9.1, Inlining Functions, in Chapter TriCore C Language of the User's Guide.

--integer-enumeration

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Miscellaneous.

3. Enable the option Use 32-bit integers for enumeration.

Command line syntax

Description

With this option you tell the compiler to use (32-bit) integers for enumerations. Without this option, the compiler uses the smallest suitable integer type.

Example

The compiler uses 32-bit integers for enumerations.

Related information

-

--is-tricore2

EDE

1. From the Project menu, select Project Options...

2. Expand the Processor entry and select Processor Definition.

3. In the Target processor list select (user defined TriCore-2).

Command line syntax

Description

With this option the compiler can generate TriCore 2 instructions in the assembly file. When you select this option, the macro _TC2 is defined in the C source file.

Example

To allow the use of TriCore 2 instructions in the assembly code, enter:

Related information

Compiler option -C (Use SFR definitions for CPU)

-k (--keep-output-files)

EDE

EDE always removes the .src file when errors occur during compilation.

Command line syntax

Description

If an error occurs during compilation, the resulting .src file may be incomplete or incorrect. With this option you keep the generated output file (.src) when an error occurs.

By default the compiler removes the generated output file (.src) when an error occurs. This is useful when you use the make utility mktc. If the erroneous files are not removed, the make utility may process corrupt files on a subsequent invocation.

Use this option when you still want to inspect the generated assembly source. Even if it is incomplete or incorrect.

Example

When an error occurs during compilation, the generated output file test.src will not be removed.

Related information

Compiler option --warnings-as-errors (Treat warnings as error)

--misrac

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select MISRA C.

3. Select a MISRA C configuration.

4. (Optional) In the MISRA C Rules entry, specify the individual rules.

Command line syntax

Description

With this option you specify to the compiler which MISRA C rules must be checked. With the option --misrac=all the compiler checks for all supported MISRA C rules.

Example

The compiler generates an error for each MISRA C rule 9, 10, 11, 12 or 13 violation in file test.c.

Related information

See Chapter 9 MISRA C Rules for a list of all supported MISRA C rules.

Linker option --misra-c-report .

-N (--default-near-size)

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Allocation.

3. Enter a threshold value in the Threshold for '__near' allocation field.

Command line syntax

Default

Description

With this option you can specify a threshold value for __near allocation. If you do not specify __near or __far in the declaration of an object, the compiler chooses where to place the object. The compiler allocates objects smaller or equal to the threshold in __near sections. Larger objects are allocated in __a0 if you specified

The default threshold is eight bytes.

If you specify -N without a threshold value, all objects will be allocated __near, including arrays an string constants.

Instead of this option you can also use #pragma default_near_size in the C source.

Example

Data elements smaller than or equal to 12 bytes are allocated in __near sections.

Related information

Compiler option -Z (maximum size in bytes for data elements that are default located in __a0 sections)

Section 3.3.1, Declare a Data Object in a Special Part of Memory, in Chapter TriCore C Language of the User's Guide.

-n (--stdout)

EDE

-

Command line syntax

Description

With this option you tell the compiler to send the output to stdout (usually your screen). No files are created.

This option is for example useful to quickly inspect the output or to redirect the output to other tools.

Example

The compiler sends the output (normally test.src) to stdout and does not create the file test.src.

Related information

-

--no-tasking-sfr

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Preprocessing.

3. Disable the option Automatic inclusion of '.sfr' file.

Command line syntax

Description

With this option the compiler does not include the register file regcpu.sfr as based on the compiler option -C.

Use this option if you want to use your own set of SFR files.

Example

The register file regtc11ib.sfr is not included.

Related information

Compiler option -C (Use SFR definitions for CPU)

-O (--optimize)

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Optimization.

3. Select an optimization level in the Optimization level box.

Command line syntax

You can set the following flags:

Use the following options for predefined sets of flags:

Default

Description

With this option you can control the level of optimization. If you do not use this option, the default optimization level is medium optimization (option -O2 or -O or -OacefgIklMopswy).

When you use this option to specify a set of optimizations, you can overrule these settings in your C source file with #pragma optimize flag and #pragma endoptimize.

In addition to the option -O, you can specify the option -t. With this option you specify whether the used optimizations should optimize for more speed (regardless of code size) or for smaller code size (regardless of speed).

Example

The following invocations are equivalent and result all in the default medium optimization set:

Related information

Compiler option -t (Trade off between speed (-t0) and size (-t4))

#pragma optimize flag
#pragma endoptimize

Section 5.3, Compiler Optimizations, in Chapter Using the Compiler of the User's Guide.

-o (--output)

EDE

-

Command line syntax

Description

With this option you can specify another filename for the output file of the compiler. Without this option the basename of the C source file is used with extension .src.

EDE names the output file always after the C source file.

Example

The compiler creates the file output.src for the compiled file test.c.

Without the option -o, like EDE, the compiler uses the names of the input file and creates test.src.

Related information

-

-R (--rename-sections)

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Miscellaneous.

3. Add the option -R to the Addtional options field.

Command line syntax

Description

The compiler defaults to a section naming convention, using a memory type abbreviation, the module name and a symbol name, for example .text.module_name.symbol_name for code sections. In case a module must be loaded at a fixed address or a data section needs a special place in memory, you can use the -R option to generate a different section name (section_type.name). You can now use this unique section name in the linker script file for locating.

When you use -R without a value, the compiler uses the default section naming.

Example

To generate the section name section_type.NEW instead of the default section name section_type.mod_name, enter:

To generate the section name section_type instead of the default section name section_type.mod_name, enter:

Related information

Section 3.10 , Compiler Generated Sections, in Chapter TriCore C Language of the User's Guide.

-s (--source)

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Miscellaneous.

3. Enable the option Merge C source code with assembly in output file (.src).

Command line syntax

Description

With this option you tell the compiler to merge C source code with generated assembly code in the output file. The C source lines are included as comments.

Example

The output file test.src contains the original C source lines as comments, besides the generated assembly code.

Related information

-

--silicon-bug

EDE

1. From the Project menu, select Project Options...

2. Expand the Processor entry and select Bypasses.

3. Select the bypasses you want to enable.

Command line syntax

You can give one or more of the following arguments:

Description

With this option you tell the compiler to use software workarounds for some CPU functional problems.

Example

The compiler uses workarounds for TC113 problems CPU5 and CPU9.

Related information

See Chapter 8 , CPU Functional Problems, for more information about the individual problems and workarounds.

--switch

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Miscellaneous.

3. Add the option --switch to the Addtional options field.

Command line syntax

You can give one of the following arguments:

Default

Description

With this option you tell the compiler which code must be generated for a switch statement: a jump chain (linear switch), a jump table or a lookup table. By default, the compiler will automatically choose the most efficient switch implementation based on code and data size and execution speed.

Example

The compiler uses a table filled with target addresses for each possible switch value.

Instead of this option you can also specify the following pragma in your C source:

Related information

See also section 3.11 , Switch Statement, in Chapter TriCore C Language of the User's Guide.

-t (--tradeoff)

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Optimization.

3. Select a trade-off level in the Size/speed trade-off box.

Command line syntax

Default

Description

If the compiler uses certain optimizations (option - O), you can use this option to specify whether the used optizations should opimize for more speed (regardless of code size) or for smaller code size (regardless of speed).

Default the compiler optimizes the selected optimizations for more speed (-t0).

If you have not used the option -O, the compiler uses default medium optimization, so you can still specify the option - t.

Example

To set the trade-off level for the used optimizations:

The compiler uses the default medium optimization level and optimizes for code size rather than for speed.

Related information

Compiler option -O (Specify optimization level)

-U (--undefine)

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Preprocessing.

3. Disable one or both predefined macros.

Command line syntax

Description

With this option you can undefine an earlier defined macro as with #undef. The TriCore compiler predefines the following macros:

This option is for example useful to undefine predefined macros.

The following predefined ISO C standard macros cannot be undefined:

Example

To undefine the predefined macro __TASKING__:

Related information

Compiler option -D (Define macro)

Section 3.8, Predefined Macros, in Chapter Using the Compiler of the Users Guide.

-u (--uchar)

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Miscellaneous.

3. Enable the option Treat 'char' variables as unsigned instead of signed.

Command line syntax

Description

Treat 'character' type variables as 'unsigned character' variables. By default char is the same as specifying signed char. With -u char is the same as unsigned char.

Example

With the following command char is treated as unsigned char:

Related information

-

-V (--version)

EDE

-

Command line syntax

Description

Display version information. The compiler ignores all other options or input files.

Example

The compiler does not compile any files but displays the following version information:

Related information

-

-w (--no-warnings)

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Warnings.

3. Enable one of the options Report all warnings, Suppress all warnings, or Suppress specific warnings.

4. Enter the numbers, separated by commas, of the warnings you want to suppress.

Command line syntax

Description

With this option you can suppresses all warning messages or specific warning messages.

Example

To suppress all warnings:

To suppress warnings 135 and 136:

Related information

Compiler option --warnings-as-errors (Treat warnings as error)

--warnings-as-errors

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Warnings.

3. Enable the option Treat warnings as errors.

Command line syntax

Description

With this option you tell the compiler to treat warnings as errors.

Example

When a warning occurs, the compiler considers it as an error.

Related information

Compiler option -w (suppress some or all warnings)

-Z (--default-a0-size)

EDE

1. From the Project menu, select Project Options...

2. Expand the C Compiler entry and select Allocation.

3. Enter a threshold value in the Threshold for '__a0' allocation field.

Command line syntax

Default

Description

With this option you can specify a threshold value for __a0 allocation. If you do not specify a memory qualifier such as __near or __far in the declaration of an object, the compiler chooses where to place the object based on the size of the object.

First, the size of the object is checked against the -N threshold, according to the description of the -N option. If the size is larger than the -N threshold, but lower or equal to the -Z threshold, the object is allocated in __a0 memory. Larger objects, arrays and strings will be allocated __far.

The default -Z threshold is zero, which means that the compiler will never use __a0 memory unless you specify the -Z option. When you use the -Z option without a threshold value, all objects not allocated __near, including arrays and string constants, will be allocated in __a0 memory.

Allocation in __a0 memory means that the object is addressed indirectly, using A0 as the base pointer. The total amount of memory that can be addressed this way is 64 Kbytes.

Instead of this option you can also use #pragma default_a0_size in the C source.

Example

Data elements smaller than or equal to 12 bytes are allocated in __a0 sections.

Related information

Compiler option -N (maximum size in bytes for data elements that are default located in __near sections)

Section 3.3.1, Declare a Data Object in a Special Part of Memory, in Chapter TriCore C Language of the User's Guide.


Copyright © 2003 Altium BV