MB060-024-00-00

Doc. ver.: 1.3

TriCore v2.1

C Compiler,
Assembler, Linker
Reference Manual
 A publication of

Altium BV

Documentation Department

Copyright  2002-2004 Altium BV

All rights reserved. Reproduction in whole or part is prohibited

without the written consent of the copyright owner.

TASKING is a brand name of Altium Limited.

The following trademarks are acknowledged:

FLEXlm is a registered trademark of Macrovision Corporation.

Intel is a trademark of Intel Corporation.
Motorola is a registered trademark of Motorola, Inc.
MS-DOS and Windows are registered trademarks of Microsoft Corporation.
SUN is a trademark of Sun Microsystems, Inc.
UNIX is a registered trademark of X/Open Company, Ltd.

All other trademarks are property of their respective owners.

Data subject to alteration without notice.

http://www.tasking.com
http://www.altium.com
The information in this document has been carefully reviewed and is
believed to be accurate and reliable. However, Altium assumes no liabilities
for inaccuracies in this document. Furthermore, the delivery of this
information does not convey to the recipient any license to use or copy the
software or documentation, except as provided in an executed license
agreement covering the software and documentation.

Altium reserves the right to change specifications embodied in this

document without prior notice.
CONTENTS
TABLE OF
CONTENTS
 IV TriCore Reference Manual

CONTENTS
CONTENTS
 Table of Contents V

TRICORE C LANGUAGE 1-1

1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.2 Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
1.3 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
1.4 Function Qualifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
1.5 Intrinsic Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
1.5.1 Minium and maximum of (Short) Integers . . . . . . . . . . . 1-13
1.5.2 Fractional Arithmetic Support . . . . . . . . . . . . . . . . . . . . . 1-14
1.5.3 Packed Data Type Support . . . . . . . . . . . . . . . . . . . . . . . . 1-15
1.5.4 Interrupt Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
1.5.5 Insert Single Assembly Instruction . . . . . . . . . . . . . . . . . 1-21
1.5.6 Register Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
1.5.7 Insert / Extract Bit-fields and Bits . . . . . . . . . . . . . . . . . . 1-23
1.5.8 Miscellaneous Intrinsic Functions . . . . . . . . . . . . . . . . . . 1-25
1.6 Pragmas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
1.7 Predefined Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31

LIBRARIES 2-1
2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2.2 Library Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2.2.1 assert.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2.2.2 complex.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2.2.3 ctype.h and wctype.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
2.2.4 errno.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
2.2.5 fcntl.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
2.2.6 fenv.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
2.2.7 float.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
2.2.8 fss.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
2.2.9 inttypes.h and stdint.h . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
2.2.10 iso646.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
2.2.11 limits.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
2.2.12 locale.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
2.2.13 math.h and tgmath.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
2.2.14 setjmp.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

• • • • • • • •
 VI TriCore Reference Manual

2.2.15 signal.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

2.2.16 stdarg.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
2.2.17 stdbool.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
2.2.18 stddef.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
2.2.19 stdint.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
2.2.20 stdio.h and wchar.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
2.2.21 stdlib.h and wchar.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
2.2.22 string.h and wchar.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
2.2.23 time.h and wchar.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41
2.2.24 Unistd.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44
2.2.25 wchar.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
2.2.26 wctype.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46
2.3 C Library Reentrancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48

TRICORE ASSEMBLY LANGUAGE 3-1

3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.2 Built-in Assembly Functions . . . . . . . . . . . . . . . . . . . . . . 3-3
3.2.1 Overview of Built-in Assembly Functions . . . . . . . . . . . 3-3
3.2.2 Detailed Description of Built-in Assembly Functions . . 3-6
3.3 Assembler Directives and Controls . . . . . . . . . . . . . . . . . 3-19
3.3.1 Overview of Assembler Directives . . . . . . . . . . . . . . . . . 3-19
3.3.2 Detailed Description of Assembler Directives . . . . . . . . 3-21
3.3.3 Overview of Assembler Controls . . . . . . . . . . . . . . . . . . . 3-64
3.3.4 Detailed Description of Assembler Controls . . . . . . . . . 3-65
CONTENTS

RUN-TIME ENVIRONMENT 4-1

4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.2 Startup Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.3 Stack Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
4.4 Heap Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
4.5 Floating-Point Arithmetic . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
4.5.1 Compliance with IEEE-754 . . . . . . . . . . . . . . . . . . . . . . . 4-11
4.5.2 Special Floating-Point Values . . . . . . . . . . . . . . . . . . . . . 4-13
 Table of Contents VII

4.5.3 Trapping Floating-Point Exceptions . . . . . . . . . . . . . . . . 4-13

4.5.4 Floating-Point Trap Handling API . . . . . . . . . . . . . . . . . . 4-15

TOOL OPTIONS 5-1

5.1 Compiler Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
5.2 Assembler Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67
5.3 Linker Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-106
5.4 Control Program Options . . . . . . . . . . . . . . . . . . . . . . . . . 5-152
5.5 Make Utility Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-214
5.6 Archiver Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-243

LIST FILE FORMATS 6-1

6.1 Assembler List File Format . . . . . . . . . . . . . . . . . . . . . . . . 6-3
6.2 Linker Map File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5

OBJECT FILE FORMATS 7-1

7.1 ELF/DWARF Object Format . . . . . . . . . . . . . . . . . . . . . . . 7-3
7.2 Motorola S-Record Format . . . . . . . . . . . . . . . . . . . . . . . . 7-4
7.3 Intel Hex Record Format . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

LINKER SCRIPT LANGUAGE 8-1

8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
8.2 Structure of a Linker Script File . . . . . . . . . . . . . . . . . . . . 8-3
8.3 Syntax of the Linker Script Language . . . . . . . . . . . . . . . 8-6
8.3.1 Preprocessing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
8.3.2 Lexical Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
8.3.3 Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
8.3.4 Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
8.3.5 Built-in Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
8.3.6 LSL Definitions in the Linker Script File . . . . . . . . . . . . . 8-11
8.3.7 Memory and Bus Definitions . . . . . . . . . . . . . . . . . . . . . . 8-11
8.3.8 Architecture Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13

• • • • • • • •
 VIII TriCore Reference Manual

8.3.9 Derivative Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15

8.3.10 Processor Definition and Board Specification . . . . . . . . 8-16
8.3.11 Section Placement Definition . . . . . . . . . . . . . . . . . . . . . . 8-16
8.4 Expression Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
8.5 Semantics of the Architecture Definition . . . . . . . . . . . . 8-21
8.5.1 Defining an Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
8.5.2 Defining Internal Buses . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
8.5.3 Defining Address Spaces . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
8.5.4 Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26
8.6 Semantics of the Derivative Definition . . . . . . . . . . . . . . 8-29
8.6.1 Defining a Derivative . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29
8.6.2 Instantiating Core Architectures . . . . . . . . . . . . . . . . . . . . 8-30
8.6.3 Defining Internal Memory and Buses . . . . . . . . . . . . . . . 8-31
8.7 Semantics of the Board Specification . . . . . . . . . . . . . . . 8-33
8.7.1 Defining a Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-33
8.7.2 Instantiating Derivatives . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34
8.7.3 Defining External Memory and Buses . . . . . . . . . . . . . . 8-35
8.8 Semantics of the Section Layout Definition . . . . . . . . . . 8-37
8.8.1 Defining a Section Layout . . . . . . . . . . . . . . . . . . . . . . . . 8-38
8.8.2 Creating and Locating Groups of Sections . . . . . . . . . . . 8-39
8.8.3 Creating or Modifying Special Sections . . . . . . . . . . . . . 8-45
8.8.4 Creating Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48
8.8.5 Conditional Group Statements . . . . . . . . . . . . . . . . . . . . . 8-49

CPU FUNCTIONAL PROBLEMS 9-1

CONTENTS

9.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

9.2 CPU Functional Problem bypasses . . . . . . . . . . . . . . . . . 9-4

MISRA C RULES 10-1

INDEX
 Manual Purpose and Structure IX

MANUAL PURPOSE AND STRUCTURE

Windows Users
The documentation explains and describes how to use the TriCore
toolchain to program a TriCore DSP. The documentation is primarily aimed
at Windows users. You can use the tools either with the graphical
Embedded Development Environment (EDE) or from the command line in
a command prompt window.

Unix Users
For UNIX the toolchain works the same as it works for the Windows
command line.

Directory paths are specified in the Windows way, with back slashes as in
\ctc\bin. Simply replace the back slashes by forward slashes for use
with UNIX: /ctc/bin.

Structure
The TriCore documentation consists of a User's Manual which includes a
Getting Started section and a separate Reference Manual (this manual).

First you need to install the software. This is described in Chapter 1,

Software Installation and Configuration, of the User's Manual.

After installation you are ready to follow the Getting Started in Chapter 2
of the User's Manual.

Next, move on with the other chapters in the User's Manual which explain
how to use the compiler, assembler, linker and the various utilities.

Once you are familiar with these tools, you can use the Reference Manual
to lookup specific options and details to make fully use of the TriCore
toolchain.

• • • • • • • •
 X TriCore Reference Manual

SHORT TABLE OF CONTENTS

Chapter 1: TriCore C Language

Contains overviews of all language extensions:
• Data types
• Keywords
• Function qualifiers
• Intrinsic functions
• Pragmas
• Predefined macros

Chapter 2: Libraries
Contains overviews of all library functions you can use in your C source.
The libraries are implemented according to the ISO/IEC 9899:1999(E)
standard.

Chapter 3: TriCore Assembly Language

Contains an overview of all assembly functions that you can use in your
assembly source code.
MANUAL STRUCTURE

Chapter 4: Run-time Environment

Contains a description of the C startup code and explains stack and heap
usage and floating-point arithmetic.

Chapter 5: Tool Options

Contains a description of all tool options:
• Compiler options
• Assembler options
• Linker options
• Control program options
• Make utility options
• Archiver options

Chapter 6: List File Formats

Contains a description of the following list file formats:
• Assembler List File Format
• Linker Map File Format
 Manual Purpose and Structure XI

Chapter 7: Object File Formats

Contains a description of the following object file formats:
• ELF/DWARF Object Formats
• Motorola S-Record Format
• Intel Hex Record Format

Chapter 8: Linker Script Language

Contains a description of the linker script language (LSL).

Chapter 9: CPU Functional Problems

Contains a description of the TASKING TriCore toolchain software
solutions for functional problems and deviations from the electrical
specifications and timing specifications for some TriCore derivatives.

Chapter 10: MISRA C Rules

Contains a description the supported and unsupported MISRA C code
checking rules.

• • • • • • • •
 XII TriCore Reference Manual

CONVENTIONS USED IN THIS MANUAL

Notation for syntax

The following notation is used to describe the syntax of command line
input:

bold Type this part of the syntax literally.

italics Substitute the italic word by an instance. For example:

filename

Type the name of a file in place of the word filename.

{} Encloses a list from which you must choose an item.

[] Encloses items that are optional. For example

ctc [ -? ]

Both ctc and ctc -? are valid commands.

| Separates items in a list. Read it as OR.

MANUAL STRUCTURE

... You can repeat the preceding item zero or more times.

,... You can repeat the preceding item zero or more times,
separating each item with a comma.

Example
ctc [option]... filename

You can read this line as follows: enter the command ctc with or without
an option, follow this by zero or more options and specify a filename. The
following input lines are all valid:
ctc test.c
ctc -g test.c
ctc -g -E test.c

Not valid is:

ctc -g

According to the syntax description, you have to specify a filename.

 Manual Purpose and Structure XIII

Icons
The following illustrations are used in this manual:

Note: notes give you extra information.

Warning: read the information carefully. It prevents you from making

serious mistakes or from loosing information.

This illustration indicates actions you can perform with the mouse. Such as
EDE menu entries and dialogs.

Command line: type your input on the command line.

Reference: follow this reference to find related topics.

• • • • • • • •
 XIV TriCore Reference Manual

RELATED PUBLICATIONS

C Standards
• C A Reference Manual (fifth edition) by Samual P. Harbison and Guy L.
Steele Jr. (2002, Prentice Hall)
• The C Programming Language (second edition) by B. Kernighan and D.
Ritchie (1988, Prentice Hall)
• ISO/IEC 9899:1999(E), Programming languages - C [ISO/IEC]
More information on the standards can be found at
http://www.ansi.org
• DSP-C, An Extension to ISO/IEC 9899:1999(E),
Programming languages - C [TASKING, TK0071-14]

MISRA C
• Guidelines for the Use of the C Language in Vehicle Based Software
[MISRA]
See also http://www.misra.org.uk

TASKING Tools
• TriCore C Compiler, Assembler, Linker User's Manual
[TASKING, MA060-024-00-00]
MANUAL STRUCTURE

• TriCore C++ Compiler User's Manual

[TASKING, MA060-012-00-00]
• TriCore CrossView Pro Debugger User's Manual
[TASKING, MA060-043-00-00]

TriCore
• TriCore 1 Unified Processor Core v1.3 Architecture Manual, Doc v1.3.3
[2002-09, Infineon]
• TriCore2 Architecture Overview Handbook [2002, Infineon]
• TriCore Embedded Application Binary Interface [2000, Infineon]
CHAPTER
TRICORE
C LANGUAGE

1
 1-2 TriCore Reference Manual

CHAPTER
1
C LANGUAGE
 TriCore C Language 1-3

1.1 INTRODUCTION
The TASKING TriCore C compiler fully supports the ANSI C standard but
adds possibilities to program the special functions of the TriCore.

This chapter contains complete overviews of the following C language

extensions of the TASKING TriCore C compiler:
• Data types
• Keywords
• Function qualifiers
• Intrinsic functions
• Pragmas
• Predefined macros

• • • • • • • •
 1-4 TriCore Reference Manual

1.2 DATA TYPES

The TASKING TriCore C compiler ctc supports the following data types:

Size Align
Type Keyword Ranges
(bit) (bit)
Bit __bit 8 8 0 or 1
Boolean _Bool 8 8 0 or 1
Character char
8 8 -27 .. 27-1
signed char

unsigned char 8 8 0 .. 28-1

Integral short
16 16 -215 .. 215-1
signed short

unsigned short 16 16 0 .. 216-1

int
signed int
long
32 16 -231 .. 231-1
signed long

unsigned int
32 16 0 .. 232-1
unsigned long

enum 8 -27 .. 27-1

8
16 -215 .. 215-1
16
32 -231 .. 231-1
long long
signed 64 32 -263 .. -263-1
C LANGUAGE

long long
unsigned
long long
64 32 0 .. 264-1

Pointer pointer to data

32 32 0 .. 232-1
pointer to func

Floating- -3.402e38 .. -1.175e-38

float 32 16
Point 1.175e-38 .. 3.402e38
double -1.797e308 .. -2.225e-308
64 32
long double 2.225e-308 .. 1.797e308
Fract __sfract 16 16 [-1, 1>
__fract 32 32 [-1, 1>
 TriCore C Language 1-5

Size Align
Type Keyword Ranges
(bit) (bit)
Accum __laccum 64 64 [-131072,131072>
Packed __packb
32 16 4x: -27 .. 27-1
signed __packb

unsigned __packb 32 16 4x: 0 .. 28-1

__packhw
32 16 2x: -215 .. 215-1
signed __packhw

unsigned
__packhw
32 16 2x: 0 .. 216-1

Table 1-1: Data Types

• • • • • • • •
 1-6 TriCore Reference Manual

1.3 KEYWORDS

__a0, __a1, __a8, __a9

The data object is located in a section that is addressable with a
sign-extended 16-bit offset from address register A0, A1, A8 or A9
respectively.

__asm()
With the __asm() keyword you can use assembly instructions in the C
source and pass C variables as operands to the assembly code.
__asm( "instruction_template"
[ : output_param_list
[ : input_param_list
[ : register_save_list]]] );

instruction_template Assembly instructions that may contain

parameters from the input list or output list in
the form: %parm_nr [.regnum]

%parm_nr[.regnum] Parameter number in the range 0 .. 9. With the

optional .regnum you can access an individual
register from a register pair or register quad. For
example, with register pair d0/d1, .0 selects
register d0.

output_param_list [[ "=[&]constraint_char"(C_expression)],...]

input_param_list [[ "constraint_char"(C_expression)],...]

& Says that an output operand is written to before

C LANGUAGE

the inputs are read, so this output must not be

the same register as any input.

constraint _char Constraint character: the type of register to be

used for the C_expression.

C_expression Any C expression. For output parameters it must

be an lvalue, that is, something that is legal to
have on the left side of an assignment.

register_save_list [["register_name"],...]

register_name Name of the register you want to reserve.

 TriCore C Language 1-7

Constraint Type Operand Remark

character
a Address register a0 .. a15
d Data register d0 .. d15
e Data register pair e0 .. e7
m Memory variable Stack or memory operand
number Type of operand it same as Indicates that %number and
is associated with %number number are the same register.

Table 1-2: Available input/output operand constraints

For more information on __asm, see section 3.6, Using Assembly in the C
Source, in Chapter TriCore C Language of the User's Manual.

__at()
With the attribute __at() you can place an object at an absolute address.
int myvar __at(0x100);

__atbit()
If you have defined a 32-bits base variable (int, long) you can declare a
single bit of that variable as a bit variable with the keyword __atbit().
The syntax is:

__atbit( name, offset )

name is the name of an integer variable in which the bit is located. offset
(range 0-31) is the bit-offset within the variable.

__circ
The TriCore C compiler supports the __circ keyword for circular buffers.

For more information see section 3.4.1, Circular Buffers, in Chapter

TriCore C Language of the User's Manual.

• • • • • • • •
 1-8 TriCore Reference Manual

__near
__far
With keyword __near the declared data object will be located in the first
16 kB of a 256 MB block. These parts of memory are directly addressable
with the absolute addressing mode.

With keyword __far the data object can be located anywhere in the
indirect addressable memory region.

__sfrbit16
__sfrbit32
With the data type qualifiers __sfrbit16 and __sfrbit32 you can
declare bit fields in special function registers. These keywords force 16-bit
or 32-bit access.

For more information see section 3.4.2, Declare an SFR Bit Field: __sfrbit16
and __sfrbit32, in Chapter TriCore C Language of the User's Manual.
C LANGUAGE
 TriCore C Language 1-9

1.4 FUNCTION QUALIFIERS

__enable_
__bisr_()
During the execution of an interrupt service routine or trap service routine,
the system blocks the CPU from taking further interrupt requests. You can
immediately re-enable the system to accept interrupt requests:
__interrupt(vector) __enable_ isr( void )
__trap(class) __enable_ tsr( void )

The function qualifier __bisr_() also re-enables the system to accept

interrupt requests. In addition, the current CPU priority number (CCPN) in
the interrupt control register is set:
__interrupt(vector) __bisr_(CCPN) isr( void )
__trap(class) __bisr_(CCPN) tsr( void )

For more information see section 3.9.2, Interrupt and Trap Functions, in
Chapter TriCore C Language of the User's Manual.

__indirect
Functions are default called with a single word direct call. However, when
you link the application and the target address appears to be out of reach
(+/- 16 MB from the callg or jg instruction), the linker generates an
error. In this case you can use the __indirect keyword to force the less
efficient, two and a half word indirect call to the function:
int __indirect foo( void )
{
...
}

inline
__noinline
You can use the inline qualifier to tell the compiler to inline the function
body instead of calling the function. Use the __noinline qualifier to tell
the compiler not to inline the function body.

• • • • • • • •
 1-10 TriCore Reference Manual

inline int func1( void )

{
// inline this function
}

__noinline int func2( void )

{
// do not inline this function
}

For more information see section 3.9.1, Inlining Functions: inline, in

Chapter TriCore C Language of the User's Manual.

__interrupt()
__interrupt_fast()
You can use the qualifier __interrupt() to declare a function as an
interrupt service routine.
void __interrupt(vector_number) isr(void)
{
...
}

The vector_number identifies the entry into the interrupt vector table
(0..255). Unlike other interrupt systems, the priority number (PIPN) of the
interrupt now being serviced by the CPU identifies the entry into the
vector table.

When you define an interrupt service routine with the

__interrupt_fast() qualifier, the interrupt handler is directly placed in
the interrupt vector table, thereby eliminating the jump code.
C LANGUAGE

For more information see section 3.9.2, Interrupt and Trap Functions, in
Chapter TriCore C Language of the User's Manual.

__trap()
__trap_fast()
__syscallfunc()
The definition of a trap service routine is similar to the definition of an
interrupt service routine. Trap functions cannot accept arguments and do
not return anything:
 TriCore C Language 1-11

void __trap( class ) tsr( void )

{
...
}

The argument class identifies the entry into the trap vector table. TriCore
defines eight classes of trap functions. Each class has its own trap handler.

When you define a trap service routine with the __trap_fast()

qualifier, the trap handler is directly placed in the trap vector table,
thereby eliminating the jump code.

A special kind of trap service routine is the system call trap. With a system
call the trap service routine of class 6 is called. For the system call trap, the
trap identification number (TIN) is taken from the immediate constant
specified with the function qualifier __syscallfunc() :
__syscallfunc(TIN)

The TIN is a value in the range 0 and 255. You can only use
__syscallfunc() in the function declaration. A function body is useless,
because when you call the function declared with __syscallfunc() , a
trap class 6 occurs which calls the corresponding trap service routine.

For more information see section 3.9.2, Interrupt and Trap Functions, in
Chapter TriCore C Language of the User's Manual.

__stackparm
The function qualifier __stackparm changes the standard calling
convention of a function into a convention where all function arguments
are passed via the stack, conforming a so called stack model. This qualifier
is only needed for situations where you need to use an indirect call to a
function for which you do not have a valid prototype.
void __stackparm stack_func ( int );

• • • • • • • •
 1-12 TriCore Reference Manual

1.5 INTRINSIC FUNCTIONS

The TASKING TriCore C compiler recognizes intrinsic functions that serve
the following purposes:
• Minimum and maximum of (short) integers
• Fractional data type support
• Packed data type support
• Interrupt handling
• Insert single assembly instruction
• Register handling
• Insert / extract bit-fields and bits
• Miscellaneous
All intrinsic functions begin with a double underscore character (__). You
can use intrinsic functions as if they were ordinary C functions.
C LANGUAGE
 TriCore C Language 1-13

1.5.1 MINIUM AND MAXIMUM OF (SHORT) INTEGERS

The next table provides an overview of the intrinsic functions that return
the minium or maximum of a signed integer, unsigned integer or short
integer.

Intrinsic Function Description

int __min( int,int ) Return minimum of two
integers
short __mins( short,short ) Return minimum of two
short integers
unsigned int Return minimum of two
__minu( unsigned int, unsigned int ) unsigned integers
int __max( int,int ) Return maximum of two
integers
short __maxs( short,short ) Return maximum of two
short integers
unsigned int Return maximum of two
__maxu( unsigned int, unsigned int ) unsigned integers

Table 1-3: Intrinsic Functions for obtaining min/max values

• • • • • • • •
 1-14 TriCore Reference Manual

1.5.2 FRACTIONAL ARITHMETIC SUPPORT

The next table provides an overview of intrinsic functions to convert
fractional values. Note that the TASKING TriCore C compiler fully supports
the fractional type so normally you should not need these intrinsic
functions (except for __mulfractlong ). For compatibility reasons the
TASKING TriCore C compiler does support these functions.

Conversion of Fractional Values

Intrinsic Function Description

long Integer part of __fract x long
__mulfractlong( __fract,long )
__sfract Convert __fract to __sfract
__round16( __fract )
__fract Convert __accum to __fract
__getfract( __accum )
short Count the consecutive
__clssf( __sfract ) number of bits that have the
same value as bit 15 of an
__sfract
__sfract Left/right shift of an __sfract
__shasfracts( __sfract,int )
__fract Left/right shift of an __fract
__shafracts( __fract,int )
__laccum Left/right shift of an __laccum
__shaaccum( __laccum,int )

Table 1-4: Intrinsic Functions for Conversion of Fractional Values

C LANGUAGE
 TriCore C Language 1-15

1.5.3 PACKED DATA TYPE SUPPORT

The next table provides an overview of the intrinsic functions for
initialization of packed data type.

Initialize Packed Data Types

Intrinsic Function Description

Initalize __packb with a
__packb __initpackbl( long )
long integer
Initalize __packb with four
__packb __initpackb( int,int,int,int )
integers
unsigned __packb __initupackb(
unsigned,unsigned,unsigned,unsigned)
Idem, but unsigned

Initalize __packhw with a

__packhw __initpackhwl( long )
long integer
Initalize __packhw with two
__packhw __initpackhw( short,short )
integers
unsigned __packhw __initupackhw(
unsigned short,unsigned short)
Idem, but unsigned

Table 1-5: Intrinsic Functions to Initialize Packed Data Types

Extract Values from Packed Data Types

The next table provides an overview of the intrinsic functions to extract a
single byte or halfword from a __packb or __packhw data type.

Intrinsic Function Description

char __extractbyte1( __packb ) Extract first byte from a __packb
unsigned char __extractubyte1(
__unsigned packb )
Idem, but unsigned

char __extractbyte2( __packb ) Extract second byte from a __packb

unsigned char __extractubyte2(
__unsigned packb )
Idem, but unsigned

char __extractbyte3( __packb ) Extract third byte from a __packb

unsigned char __extractubyte3(
__unsigned packb )
Idem, but unsigned

char __extractbyte4( __packb ) Extract fourth byte from a __packb

unsigned char __extractubyte4(
__unsigned packb )
Idem, but unsigned

• • • • • • • •
 1-16 TriCore Reference Manual

Intrinsic Function Description

short __extracthw1( __packhw ) Extract first short from a __packhw
unsigned short __extractuhw1(
unsigned __packhw ) Idem, but unsigned

short __extracthw2( __packhw ) Extract second short from a __packhw

unsigned short __extractuhw2(
unsigned __packhw ) Idem, but unsigned

char __getbyte1( __packb * ) Extract first byte from a __packb

unsigned char __getubyte1(
unsigned __packb * ) Idem, but unsigned

char __getbyte2( __packb * ) Extract second byte from a __packb

unsigned char __getubyte2(
unsigned __packb * ) Idem, but unsigned

char __getbyte3( __packb * ) Extract third byte from a __packb

unsigned char __getubyte3(
unsigned __packb * ) Idem, but unsigned

char __getbyte4( __packb * ) Extract fourth byte from a __packb

unsigned char __getubyte4(
unsigned __packb * ) Idem, but unsigned

short __gethw1( __packhw * ) Extract first integer from a __packhw

unsigned short __getuhw1(
unsigned __packhw * ) Idem, but unsigned

short __gethw2( __packhw * ) Extract short integer from a __packhw

unsigned short __getuhw2(
unsigned __packhw * ) Idem, but unsigned

Table 1-6: Intrinsic Functions to Extract Values from Packed Data Types
C LANGUAGE
 TriCore C Language 1-17

Insert Values into Packed Data Types

The next table provides an overview of the intrinsic functions to insert a
single byte or halfword into a __packb or __packhw data type.

Intrinsic Function Description

Insert char into first byte of
__packb __insertbyte1( __packb, char )
a __packb
unsigned __packb __insertubyte1(
unsigned __packb, unsigned char ) Idem, but unsigned

Insert char into second byte

__packb __insertbyte2( __packb, char )
of a __packb
unsigned __packb __insertubyte2(
unsigned __packb, unsigned char ) Idem, but unsigned

Insert char into third byte of

__packb __insertbyte3( __packb, char )
a __packb
unsigned __packb __insertubyte3(
unsigned __packb, unsigned char ) Idem, but unsigned

Insert char into fourth byte

__packb __insertbyte4( __packb, char )
of a __packb
unsigned __packb __insertubyte4(
unsigned __packb, unsigned char ) Idem, but unsigned

Insert short into first

__packhw __inserthw1( __packhw, short )
halfword of a __packhw
unsigned __packhw __insertuhw1(
unsigned __packhw, unsigned short ) Idem, but unsigned

Insert short into second

__packhw __inserthw2( __packhw, short )
halfword of a __packhw
unsigned __packhw __insertuhw2(
unsigned __packhw, unsigned short ) Idem, but unsigned

Insert first byte into a

void __setbyte1( __packb *, char )
__packb
void __setubyte1( unsigned __packb *,
unsigned char ) Idem, but unsigned

Insert second byte into a

void __setbyte2( __packb *, char )
__packb
void __setubyte2( unsigned __packb *,
unsigned char ) Idem, but unsigned

• • • • • • • •
 1-18 TriCore Reference Manual

Intrinsic Function Description

Insert third byte into a
void __setbyte3( __packb *, char )
__packb
void __setubyte3( unsigned __packb *,
unsigned char ) Idem, but unsigned

Insert fourth byte into a

void __setbyte4( __packb *, char )
__packb
void __setubyte4( unsigned __packb *,
unsigned char ) Idem, but unsigned

Insert first integer into a

void __sethw1( __packhw *, short )
__packhw
void __setuhw1( unsigned __packhw *,
unsigned short ) Idem, but unsigned

Insert short integer into a

void __sethw2( __packhw *, short )
__packhw
void __setuhw2( unsigned __packhw *,
unsigned short ) Idem, but unsigned

Table 1-7: Intrinsic Functions to Insert Values into Packed Data Types

Combine Packed Data Types into a Packed Word

The next table provides an overview of the intrinsic functions to combine
the value of packed data types into a packed word. You can combine two
__packb (2 x 4 bytes) into a long long or two __packhw (2 x 2
halfwords) into a long long.

The packed word is a double register that is represented by the additional

datatype __packw. To access the values in a _packw variable, you can use
C LANGUAGE

a union data type: typedef double __packw.

These intrinsics are only supported for the TriCore2 (--is-tricore2).

Intrinsic Function Description

unsigned long long Combine two __packb
__transpose_byte( __packb,__packb )
unsigned long long Combine two __packhw
__transpose_hword( __packhw,__packhw )

Table 1-8: Intrinsic Functions to Combine Packed Data Types

 TriCore C Language 1-19

Calculate Absolute Values of Packed Data Type Values

The next table provides an overview of the intrinsic functions to calculate
the absolute value of packed data type values.

Intrinsic Function Description

__packb __absb( __packb ) Absolute value of __packb
__packhw __absh( __packhw ) Absolute value of __packhw
__sat __packhw Absolute value of __packhw
__abssh( __sat __packhw ) using saturation

Table 1-9: Intrinsic Functions to Calculate Absolute Values

Calculate Minimum Packed Data Type Values

The next table provides an overview of the intrinsic functions to calculate
the minimum from two packed data type values.

Intrinsic Function Description

__packb __minb( __packb,__packb ) Minimum of two __packb
values
unsigned __packb __minbu( unsigned Minimum of two unsigned
__packb, unsigned __packb ) __packb values
__packhw __minh( __packhw,__packhw ) Minimum of two __packhw
values
unsigned __packhw __minhu( unsigned Minimum of two unsigned
__packhw, unsigned __packhw ) __packhw values

Table 1-10: Intrinsic Functions to Calculate Absolute Values

1.5.4 INTERRUPT HANDLING

The next table provides an overview of the intrinsic functions to read or
set interrupt handling:.

• • • • • • • •
 1-20 TriCore Reference Manual

Intrinsic Function Description

void __enable ( void ) Enable interrupts immediately at
function entry
void __disable ( void ) Disable interrupts Only supported
for TriCore1.
int __disable_and_save ( void ) Disable interrupts and return
previous interrupt state (enabled or
disabled). Only supported for
TriCore2 (--is-tricore2).
void __restore ( int ) Restore interrupt state. Only
supported for TriCore2
(--is-tricore2).
void __bisr ( int ) Set CPU priority number [0..512]
and enable interrupts immediately
at function entry
void __sysc ( int ) Call a system call function number

Table 1-11: Intrinsic Functions for Interrupt Handling

C LANGUAGE
 TriCore C Language 1-21

1.5.5 INSERT SINGLE ASSEMBLY INSTRUCTION

The next table provides an overview of the intrinsic functions that you can
use to insert a single assembly instruction.

You can also use inline assembly but these intrinsics provide a shorthand
for frequently used assembly instructions.

See section 3.6, Using Assembly in the C Source: __asm() of the

User's Manual

Intrinsic Function Description

void __debug( void ) Insert DEBUG instruction
void __dsync( void ) Insert DSYNC instruction
void __isync( void ) Insert ISYNC instruction
void __svlcx( void ) Insert SVLCX instruction
void __rslcx( void ) Insert RSLCX instruction
void __nop( void ) Insert NOP instruction

Table 1-12: Intrinsic Functions for Inserting Assembly Instructions

• • • • • • • •
 1-22 TriCore Reference Manual

1.5.6 REGISTER HANDLING

Access Control Registers

The next table provides an overview of the intrinsic functions that you can
use to acces control registers.

Intrinsic Function Description

int __mfcr( int ) move contents of the addressed core SFR
into a data register
void __mtcr ( int,int ) move contents of a data register (second int)
to the addressed core SFR (first int)

Table 1-13: Intrinsic Functions for Accessing Control Registers

Perform Register Value Operations

The next table provides an overview of the intrinsic functions that operate
on a register and return a value in another register.

Intrinsic Function Description

int __clz ( int ) Count leading zeros in int
int __clo ( int ) Count leading ones in int
int __cls ( int ) Count number of redundant sign bits (all
consecutive bits with the same value as bit 31)
int __satb ( int ) Return saturated byte
int __satbu ( int ) Return saturated unsigned byte
int __sath ( int ) Return saturated halfword
C LANGUAGE

int __sathu ( int ) Return saturated unsigned halfword

int __abs ( int ) Return absolute value
int __abss ( int ) Return absolute value with saturation
int __parity ( int ) Return parity

Table 1-14: Intrinsic Functions for Performing Register Value Operations

 TriCore C Language 1-23

1.5.7 INSERT / EXTRACT BIT-FIELDS AND BITS

Insert / Extract Bit-fields

The next table provides an overview of the intrinsic functions to insert or
extract a bit-field.

Intrinsic Function Description

int __extr ( int value, Extract a bit-field (bit pos to bit
int pos,int width ) pos+width) from value
unsigned int __extru ( int Same as __extr() but return bit-field
value,int pos,int width ) as unsigned integer
int __insert ( int src,int Extract bit-field (bit pos to bit
trg, int pos,int width ) pos+width) from src and insert it in trg.
int _ins( int trg, int trgbit, Return trg but replace trgbit by srcbit
int src, int srcbit ) in src.
int _insn(int trg, int trgbit, Return trg but replace trgbit by inverse
int src, int srcbit ) of srcbit in src.

Table 1-15: Intrinsic Functions to Insert / Extract Bit-fields

Atomic Load-Modify-Store
With the next intrinsic function you can peform atomic Load-Modify-Store
of a bit-field from an integer value. This function uses the IMASK and
LDMST instruction. The intrinsic writes the number of bits of an integer
value at a certain address location in memory with a bitoffset. The number
of bits must be a constant value.

Intrinsic Function
void __imaskldmst(int* address,int value,int bitoffset,int bits)

Store a single bit

With the intrinsic macro __putbit() you can store a single bit atomicly
in memory at a specified bit offset. The bit at offset 0 in value is stored at
an address location in memory with a bitoffset.

This intrinsic is implemented as a macro definition which uses the

_imaskldmst() intrinsic:
#define __putbit ( value, address, bitoffset ) __imaskldmst
( address, value, bitoffset, 1 )

• • • • • • • •
 1-24 TriCore Reference Manual

Intrinsic Macro
void __putbit( int value, int* address, int bitoffset )

Load a single bit

With the intrinsic macro __getbit() you can load a single bit from
memory at a specified bit offset. A bit value is loaded from an address
location in memory with a bitoffset and returned as an unsigned integer
value.

This intrinsic is implemented as a macro definition which uses the

__extru() intrinsic function:
#define _getbit ( address, bitoffset ) _extru ( *(address),
bitoffset, 1 )

Intrinsic Macro
unsigned integer __getbit( int* address, int bitoffset )
C LANGUAGE
 TriCore C Language 1-25

1.5.8 MISCELLANEOUS INTRINSIC FUNCTIONS

Multiply and Scale Back

The next intrinsic multiplies two 32-bit numbers to an intermediate 64-bit
result, and scales back the result to 32 bits. To scale back the result, 32 bits
are extracted from the intermediate 64-bit result: bit 63-offset to bit
31-offset.

Intrinsic Function
int __mulsc( int a, int b, int offset )

Swap Mask
The next intrinsic exchanges the values of value and memory, but only
those bits that are allowed by mask. Before the __swapmsk instruction is
generated, the parameters value and mask are moved into a double
register.

This intrinsic is only supported for the TriCore2 (--is-tricore2).

Intrinsic Function
void __swapmsk ( int value, int mask, int * memory )

Initialize Circular Pointer

With the next intrinsic you can initialize a circular pointer with a
dynamically allocated buffer at run-time.

Intrinsic Function
__circ void * __initcirc( void * buf, unsigned short bufsize,
unsigned short byteindex )

See also Section 3.4.1, Circular Buffers, in Chapter TriCore C Language of

the User's Manual.

• • • • • • • •
 1-26 TriCore Reference Manual

1.6 PRAGMAS
Pragmas are keywords in the C source that control the behavior of the
compiler. Pragmas overrule compiler options and keywords.

For general information on pragmas see section 3.7, Pragmas to Control

the Compiler, in Chapter TriCore C Language of the User's Manual.

The syntax is:

#pragma name-of-pragma

The compiler recognizes the following pragmas, other pragmas are

ignored. Sometimes the resemblence of a pragma and a compiler option is
so strong, that no explanation is given but instead is referred to the
description of the corresponding compiler option.

#pragma CPU_functiona_problem
#pragma TC112_functional_problem
#pragma TC113_functional_problem
Use software work arounds for the specified functional problem.

See compiler option --silicon-bug in section Compiler Options in

Chapter Tool Options.

#pragma alias symbol=defined_symbol

Define symbol as an alias for defined_symbol. It corresponds to an equate
directive (.EQU) at assembly level. The symbol should not be defined
elsewhere, and defined_symbol should be defined with static storage
duration (not extern or automatic).
C LANGUAGE

See also the .EQU directive directive in Section 3.3, Assembler Directives
and Controls, in Chapter Assembly Language.

#pragma align n
#pragma align restore
See compiler option --align in section Compiler Options in Chapter Tool
Options.

#pragma clear
#pragma noclear
Performs 'clearing' or no 'clearing' of non-initialized static/public variables.
 TriCore C Language 1-27

#pragma default_a0_size [value]

See compiler option -Z in section Compiler Options in Chapter Tool
Options.

#pragma default_a1_size [value]

See compiler option -Y in section Compiler Options in Chapter Tool
Options.

#pragma default_near_size [value]

See compiler option -N in section Compiler Options in Chapter Tool
Options.

#pragma extension isuffix

Enables a language extension to specify imaginary floating-point
constants. With this extension, you can use an "i" suffix on a floating-point
constant, to make the type _Imaginary:
float 0.5i

#pragma extern symbol

Normally, when you use the C keyword extern, the compiler generates
an .EXTERN directive in the generated assembly source. However, if the
compiler does not find any references to the extern symbol in the C
module, it optimizes the assembly source by leaving the .EXTERN
directive out.

With this pragma you force the compiler to generate the .EXTERN
directive, creating an external symbol in the generated assembly source,
even when the symbol is not used in the C module.

See the EXTERN directive directive in Section 3.3, Assembler Directives

and Controls, in Chapter Assembly Language.

• • • • • • • •
 1-28 TriCore Reference Manual

#pragma for_constant_data_use_memory memory

#pragma for_extern_data_use_memory memory
#pragma for_initialized_data_use_memory memory
#pragma for_uninitialized_data_use_memory memory
Use the specified memory for the type of data mentioned in the pragma
name. You can specify the following memories:

near, far, a0, a8 or a9.

For #pragma for_constant_data_use_memory you can also specify the

a1 memory.

This pragma overrules the pragmas #pragma default_a0_size, #pragma

default_a1_size, #pragma default_near_size, and the memory qualifiers
near and far.

#pragma indirect
Generates code for indirect function calling.

See compiler option --indirect in section Compiler Options in Chapter

Tool Options.

#pragma indirect_runtime
Generates code for indirect calls to run-time functions.

See compiler option --indirect_runtime in section Compiler Options in

Chapter Tool Options.

#pragma inline
#pragma noinline
C LANGUAGE

#pragma smartinline
See section 3.9.1, Inlining Functions of the User's Manual.

#pragma macro
#pragma nomacro
Turns macro expansion on or off. Default, macro expansion is turned on.

#pragma message "string" ...

Print the message string(s) on standard output.
 TriCore C Language 1-29

#pragma object_comment "string" ...

This pragma generates a .comment section in the assembly file with the
specified string. After assembling, this string appears in the generated .o
or .elf object file. If you specify this pragma more than once in the same
module, only the last pragma has effect.

See compiler option --object-comment in section Compiler Options in

Chapter Tool Options.

#pragma optimize flags

#pragma endoptimize
#pragma optimize restore
See section 5.3, Compiler Optimizations in Chapter Using the Compiler of
the User's Manual.

#pragma pack 2
#pragma pack 0
See section 3.2.4, Packed Data Types of the User's Manual.

#pragma section all "section_name"

#pragma section section_type "section_name"
#pragma section code_init
#pragma section const_init
#pragma section vector_init
#pragma section data_overlay
See section 3.10, Compiler Generated Sections and
compiler option -R in section Compiler Options in Chapter Tool Options.

#pragma source
#pragma nosource
See compiler option -s in section Compiler Options in Chapter Tool
Options.

• • • • • • • •
 1-30 TriCore Reference Manual

#pragma switch auto

#pragma switch jumptab
#pragma switch linear
#pragma switch lookup
#pragma switch restore
See section 3.11, Switch Statement of the User's Manual and
compiler option --switch in section Compiler Options in Chapter Tool
Options.

#pragma tradeoff level

Specify whether the used optizations should opimize for more speed (0),
regardless of code size or for smaller code size (4), regardless of speed).

See also compiler option -t (--tradeoff) in section Compiler Options in

Chapter Tool Options.

#pragma warning [number,...]

With this pragma you can disable warning messages. If you do not specify
a warning number, all warnings will be suppressed.

See also compiler option -w (--no-warnings) in section Compiler

Options in Chapter Tool Options.

#pragma weak symbol

Mark a symbol as "weak" (WEAK assembler directive). The symbol must
have external linkage, which means a global or external object or function.
A static symbol cannot be declared weak.
C LANGUAGE

A weak external reference is resolved by the linker when a global (or

weak) definition is found in one of the object files. However, a weak
reference will not cause the extraction of a module from a library to
resolve the reference. When a weak external reference cannot be resolved,
the null pointer is substituted.

A weak definition can be overruled by a normal global definition. The

linker will not complain about the duplicate definition, and ignore the
weak definition.

See the .WEAK directive directive in Section 3.3, Assembler Directives and
Controls, in Chapter Assembly Language.
 TriCore C Language 1-31

1.7 PREDEFINED MACROS

In addition to the predefined macros required by the ISO C standard, the
TASKING TriCore C compiler supports the predefined macros as defined in
Table 1-16. The macros are useful to make conditional C code.

Macro Description
__DOUBLE_FP__ Defined when you do not use compiler option -F
(Treat double as float)
__SINGLE_FP__ Defined when you use compiler option -F (Treat
double as float)
__FPU__ Defined when you use compiler option
--fpu-present (Use hardware floating-point
instructions)
__CTC__ Identifies the compiler. You can use this symbol to flag
parts of the source which must be recognized by the
ctc compiler only. It expands to the version number of
the compiler.
__TASKING__ Identifies the compiler as the TASKING TriCore
compiler. It expands to 1.
__DSPC__ Indicates conformation to the DSP-C standard. It
expands to 1.
__DSPC_VERSION__ Expands to the decimal constant 200001L.
__VERSION__ Identifies the version number of the compiler. For
example, if you use version 2.1r1 of the compiler,
__VERSION__ expands to 2001 (dot and revision
number are omitted, minor version number in 3 digits).
__REVISION__ Identifies the revision number of the compiler. For
example, if you use version 2.1r1 of the compiler,
__REVISION__ expands to 1.
__BUILD__ Identifies the build number of the compiler, composed
of decimal digits for the build number, three digits for
the major branch number and three digits for the
minor branch number. For example, if you use build
1.22.1 of the compiler, __BUILD__ expands to
1022001. If there is no branch number, the branch
digits expand to zero. For example, build 127 results
in 127000000.

Table 1-16: Predefined macros

• • • • • • • •
 1-32 TriCore Reference Manual
C LANGUAGE
CHAPTER

LIBRARIES

2
 2-2 TriCore Reference Manual

CHAPTER
2
LIBRARIES
 Libraries 2-3

2.1 INTRODUCTION
This chapter contains an overview of all library functions that you can call
in your C source. This includes all functions of the standard C library
(libc.a) and some functions of the floating-point library (libfp.a or
libfpt.a).

Section 2.2, Library Functions, gives an overview of all library functions

you can use, grouped per header file. A number of functions declared in
wchar.h are parallel to functions in other header files. These are
discussed together.

Section 2.3, C Library Reentrancy, gives an overview of which functions

are reentrant and which are not.

The following libraries are included in the TriCore (ctc) toolchain. Both
EDE and the control program cctc automatically select the appropriate
libraries depending on the specified TriCore derivative.

Library to link Description

libc.a C library
(Some functions require the floating-point library. Also
includes the startup code.)
libcs.a C library single precision (compiler option -F)
(Some functions require the floating-point library. Also
includes the startup code.)
libcs_fpu.a C library single precision with FPU instructions (compiler
option -F and --fpu-present)
libfp.a Floating-point library (non-trapping)
libfpt.a Floating-point library (trapping)
(Control program option --fp-trap)
libfp_fpu.a Floating-point library (non-trapping, with FPU instructions)
(Compiler option --fpu-present)
libfpt_fpu.a Floating-point library (trapping, with FPU instructions)
(Control program option --fp-trap, compiler option
--fpu-present)
librt.a Run-time library

Table 2-1: Overview of libraries

• • • • • • • •
 2-4 TriCore Reference Manual

2.2 LIBRARY FUNCTIONS

The tables in the sections below list all library functions, grouped per
header file in which they are declared. Some functions are not completely
implemented because their implementaion depends on the context where
your application will run. These functions are for example all I/O related
functions. Where possible, these functions are implemented using file
system simulation (FSS). This system can be used by CrossView Pro to
simulate an I/O environment which enables you to debug your
application.

2.2.1 ASSERT.H

assert(expr) Prints a diagnostic message if NDEBUG is not defined.

(Implemented as macro)

2.2.2 COMPLEX.H
The complex number z is also written as x+yi where x (the real part) and
y (the imaginary part) are real numbers of types float, double or long
double. The real and imaginary part can be stored in structs or in arrays.
This implementation uses arrays because structs may have different
alignments.

The header file complex.h also defines the following macros for
backward compatibility:

complex _Complex /* C99 keyword */

imaginary _Imaginary /* C99 keyword */

Parallel sets of functions are defined for double, float and long double.
LIBRARIES

They are respectively named function, functionf, functionl. All long

type functions, though declared in complex.h, are implemented as the
double type variant which nearly always meets the requirement in
embedded applications.

This implementation uses the obvious implementation for complex

multiplication; and a more sophisticated implementation for divison and
absolute value calculations which handles underflow, overflow and
infinities with more care. The ISO/IEC 9899 #pragma
CX_LIMITED_RANGE therefore has no effect.
 Libraries 2-5

Trigonometric functions
csin csinf csinl Returns the complex sine of z.
ccos ccosf ccosl Returns the complex cosine of z.
ctan ctanf ctanl Returns the complex tangent of z.
casin casinf casinl Returns the complex arc sine sin-1(z).
cacos cacosf cacosl Returns the complex arc cosine cos-1(z).
catan catanf catanl Returns the complex arc tangent tan-1(z).
csinh csinhf csinhl Returns the complex hyperbolic sine of z.
ccosh ccoshf ccoshl Returns the complex hyperbolic cosine of z.
ctanh ctanhf ctanhl Returns the complex hyperbolic tangent of z.
casinh casinh cfasinhl Returns the complex arc hyperbolic sinus of z.
cacosh cacosh cfacoshl Returns the complex arc hyperbolic cosinus of z.
catanh catanhfcatanhl Returns the complex arc hyperbolic tangent of z.

Exponential and logarithmic functions

cexp cexpf cexpl Returns the result of the complex exponential
function ez.
clog clogf clogl Returns the complex natural logarithm.

Power and absolute-value functions

cabs cabsf cabsl Returns the complex absolute value of z (also
known as norm, modulus or magnitude).
cpow cpowf cpowl Returns the complex value of z raised to the
power w (z w) where both z and w are complex
numbers.
csqrt csqrtf csqrtl Returns the complex square root of z.

Manipulation functions
carg cargf cargl Returns the argument of z (also known as phase
angle).
cimag cimagf cimagl Returns the imaginary part of z as a real (re
spectively as a double, float, long double)
conj conjf conjl Returns the complex conjugate value (the sign
of its imaginary part is reversed).

• • • • • • • •
 2-6 TriCore Reference Manual

cproj cprojf cprojl Returns the value of the projection of z onto the
Riemann sphere.
creal crealf creall Returns the real part of z (respectively as a
double, float, long double)

2.2.3 CTYPE.H AND WCTYPE.H

The header file ctype.h declares the following functions which take a
character c as an integer type argument. The header file wctype.h
declares parallel wide-character functions which take a character c of the
wchar_t type as argument.

Ctype.h Wctype.h Description

isalnum iswalnum Returns a non-zero value when c is an alpha-
betic character or a number ([A-Z][a-z][0-9]).
isalpha iswalpha Returns a non-zero value when c is an alphabetic
character ([A-Z][a-z]).
isblank iswblank Returns a non-zero value when c is a blank
character (tab, space...)
iscntrl iswcntrl Returns a non-zero value when c is a control
character.
isdigit iswditit Returns a non-zero value when c is a numeric
character ([0-9]).
isgraph iswgraph Returns a non-zero value when c is printable, but
not a space.
islower iswlower Returns a non-zero value when c is a lowercase
character ([a-z]).
isprint iswprint Returns a non-zero value when c is printable,
including spaces.
LIBRARIES

ispunct iswpunct Returns a non-zero value when c is a punctuation

character (such as '.', ',', '!').
isspace iswspace Returns a non-zero value when c is a space type
character (space, tab, vertical tab, formfeed,
linefeed, carriage return).
isupper iswupper Returns a non-zero value when c is an uppercase
character ([A-Z]).
isxdigit iswxdigit Returns a non-zero value when c is a
hexadecimal digit ([0-9][A-F][a-f]).
 Libraries 2-7

Ctype.h Wctype.h Description

tolower towlower Returns c converted to a lowercase character if it
is an uppercase character, otherwise c is returned.
toupper towupper Returns c converted to an uppercase character if it
is a lowercase character, otherwise c is returned.
_tolower - Converts c to a lowercase character, does not
check if c really is an uppercase character.
Implemented as macro. This macro function is not
defined in ISO/IEC 9899.
_toupper - Converts c to an uppercase character, does not
check if c really is a lowercase character.
Implemented as macro. This macro function is not
defined in ISO/IEC 9899.
isascii Returns a non-zero value when c is in the range
of 0 and 127.
This function is not defined in ISO/IEC 9899.
toascii Converts c to an ASCII value (strip highest bit).
This function is not defined in ISO/IEC 9899.

2.2.4 ERRNO.H

int errno External variable that holds implementation defined error codes.

The following error codes are defined as macros in errno.h:

• • • • • • • •
 2-8 TriCore Reference Manual

EZERO 0 No error
EPERM 1 Not owner
ENOENT 2 No such file or directory
EINTR 3 Interrupted system call
EIO 4 I/O error
EBADF 5 Bad file number
EAGAIN 6 No more processes
ENOMEM 7 Not enough core
EACCES 8 Permission denied
EFAULT 9 Bad address
EEXIST 10 File exists
ENOTDIR 11 Not a directory
EISDIR 12 Is a directory
EINVAL 13 Invalid argument
ENFILE 14 File table overflow
EMFILE 15 Too many open files
ETXTBSY 16 Text file busy
ENOSPC 17 No space left on device
ESPIPE 18 Illegal seek
EROFS 19 Read-only file system
EPIPE 20 Broken pipe
ELOOP 21 Too many levels of symbolic links
ENAMETOOLONG 22 File name too long

Floating-point errors

EDOM 23 Argument too large

ERANGE 24 Result too large

Errors returned by prinff/scanf

ERR_FORMAT 25 Illegal format string for printf/scanf

ERR_NOFLOAT 26 Floating-point not supported
LIBRARIES

ERR_NOLONG 27 Long not supported

ERR_NOPOINT 28 Pointers not supported

Error returned by file positioning routines

ERR_POS 29 Positioning failure

Encoding error stored in errno by functions like fgetwc, getwc,

mbrtowc, etc ...

EILSEQ 30 Illegal byte sequence (including too few bytes)

 Libraries 2-9

2.2.5 FCNTL.H
The header file fcntl.h contains the function open(), which calls the
low level function _open(), and definitions of flags used by the low level
function _open(). This header file is not defined in ISO/IEC9899.

open Opens a file a file for reading or writing. Calls _open.

(FSS implementation)

2.2.6 FENV.H
Contains mechanisms to control the floating-point environment. The
functions in this header file are not implemented.

fegetenv Stores the current floating-point environment.

(Not implemented)
feholdexept Saves the current floating-point environment and installs
an environment that ignores all floating-point exceptions.
(Not implemented)
fesetenv Restores a previously saved (fegetenv or feholdexcept)
floating-point environment. (Not implemented)
feupdateenv Saves the currently raised floating-point exceptions,
restores a previousely saved floating-point environment
and finally raises the saved exceptions.
(Not implemented)

feclearexcept Clears the current exception status flags corresponding to

the flags specified in the argument. (Not implemented)
fegetexceptflag Stores the current setting of the floating-point status
flags. (Not implemented)
feraiseexcept Raises the exceptions represented in the argument. As a
result, other exceptions may be raised as well.
(Not implemented)
fesetexceptflag Sets the current floating-point status flags.
(Not implemented)
fetestexcept Returns the bitwise-OR of the exception macros corre
sponding to the exception flags which are currently set
and are specified in the argument. (Not implemented)

For each supported exception, a macro is defined. The following

exceptions are defined:

• • • • • • • •
 2-10 TriCore Reference Manual

FE_DIVBYZERO FE_INEXACT FE_INVALID

FE_OVERFLOW FE_UNDERFLOW FE_ALL_EXCEPT

fegetround Returns the current rounding direction, represented as

one of the values of the rounding direction macros.
(Not implemented)
fesetround Sets the current rounding directions. (Not implemented)

Currently no rounding mode macros are implemented.

2.2.7 FLOAT.H
The header file float.h defines the characteristics of the real
floating-point types float, double and long double.

Float.h used to contain prototypes for the functions copysign(f),

isinf(f), isfinite(f), isnan(f) and scalb(f). These functions have
accordingly to the ISO/IEC9899 standard been moved to the header file
math.h. See also section 2.2.13, Math.h and Tgmath.h.

2.2.8 FSS.H
The header file fss.h contains definitions and prototypes for low level
I/O functions used for CrossView Pro's file system simulation (FSS). The
low level functions are also declared in stdio.h; they are all
implemented as FSS functions. This header file is not defined in
ISO/IEC9899.

Stdio.h Description
Buffer and breakpoint functions for
LIBRARIES

_fss_break(void)
CrossView Pro.
Opens file descriptors 0 (stdin), 1 (stdout)
_fss_init(fd,is_close) and 2 (stderr) and associates them with
terminal window FSS 0 of CrossView Pro.
_close(fd)
_lseek(fd,offset,whence)
_open(fd,flags) See Low Level File Access Functions in
_read(fd,*buff,cnt) section 2.2.20, Stdio.h.
_unlink(*name)
_write(fd,*buffer,cnt)
 Libraries 2-11

2.2.9 INTTYPES.H AND STDINT.H

The header files stdint.h and inttypes.h provide additional
declarations for integer types and have various characteristics. The
stdint.h header file contains basic definitions of integer types of certain
sizes, and corresponding sets of macros. This header file clearly refers to
the corresponding sections in the ISO/IEC 9899 standard.
The inttypes.h header file incldues stdint.h and adds portable
formatting and conversion functions. Below the conversion functions from
inttypes.h are listed.

intmax_t imaxabs(intmax_t j); Returns the absolute value of j

imaxdiv_t imaxdiv(intmax_t numer, Computes numer/denom and
intmax_t denom); numer % denom. The result is
stored in the quot and rem
components of the imaxdiv_t
structure type.
intmax_t strtoimax(const char * Convert string to maximum sized
restrict nptr, char ** restrict integer. (Compare strtoll)
endptr, int base);
uintmax_t strtoumax(const char * Convert string to maximum sized
restrict nptr, char ** restrict unsigned integer. (Compare
endptr, int base); strtoull)
intmax_t wcstoimax(const wchar_t Convert wide string to maximum
* restrict nptr, wchar_t ** sized integer. (Compare wcstoll)
restrict endptr, int base);
uintmax_t wcstoumax(const wchar_t Convert wide string to maximem
* restrict nptr, wchar_t ** sized unsigned integer. (Compare
restrict endptr, int base); wcstoull)

• • • • • • • •
 2-12 TriCore Reference Manual

2.2.10 ISO646.H
The header file iso646.h adds tokens that can be used instead of regular
operator tokens.

#define and &&

#define and_eq &=
#define bitand &
#define bitor |
#define compl ~
#define not !
#define not_eq !=
#define or ||
#define or_eq |=
#define xor ^
#define xor_eq ^=

2.2.11 LIMITS.H
Contains the sizes of integral types, defined as macros.

2.2.12 LOCALE.H
To keep C code reasonable portable accross different languages and
cultures, a number of facilities are provided in the header file local.h.

char *setlocale( int category, const char *locale )

The function above changes locale-specific features of the run-time

library as specified by the category to change and the name of the
locale.
LIBRARIES

The following categories are defined and can be used as input for this
function:

LC_ALL 0 LC_NUMERIC 3
LC_COLLATE 1 LC_TIME 4
LC_CTYPE 2 LC_MONETARY 5
 Libraries 2-13

struct lconv *localeconv( void )

Returns a pointer to type stuct lconv with values appropriate for

the formatting of numeric quantities according to the rules of the
current locale. The struct lconv in this header file is conforming the
ISO standard.

2.2.13 MATH.H AND TGMATH.H

The header file math.h contains the prototypes for many mathematical
functions. Before C99, all functions were computed using the double type
(the float was automatically converted to double, prior to calculation). In
this C99 version, parallel sets of functions are defined for double, float and
long double. They are respectively named function, functionf, functionl.
All long type functions, though declared in math.h, are implemented as
the double type variant which nearly always meets the requirement in
embedded applications.

The header file tgmath.h contains parallel type generic math macros
whose expansion depends on the used type. tgmath.h includes math.h
and the effect of expansion is that the correct math.h functions are called.
The type generic macro, if available, is listed in the second column of the
tables below.

Trigonometric functions
Math.h Tgmath.h Description
sin sinf sinl sin Returns the sine of x.
cos cosf cosl cos Returns the cosine of x.
tan tanf tanl tan Returns the tangent of x.
asin asinf asinl asin Returns the arc sine sin-1(x) of x.
acos acosf acosl acos Returns the arc cosine cos-1(x) of x.
atan atanf atanl atan Returns the arc tangent tan-1(x) of x.
atan2 atan2f atan2l atan2 Returns the result of: tan-1(y/x).
sinh sinhf sinhl sinh Returns the hyperbolic sine of x.
cosh coshf coshl cosh Returns the hyperbolic cosine of x.
tanh tanhf tanhl tanh Returns the hyperbolic tangent of x.
asinh asinhf asinhl asinh Returns the arc hyperbolic sinus of x.

• • • • • • • •
 2-14 TriCore Reference Manual

Math.h Tgmath.h Description

acosh acoshf acoshl acosh Returns the non-negative arc hyper
bolic cosinus of x.
atanh atanhf atanhl atanh Returns the arc hyperbolic tangent of
x.

Exponential and logarithmic functions

All of these functions are new in C99, except for exp, log and log10.

Math.h Tgmath.h Description

exp expf expl exp Returns the result of the exponential
function ex.
exp2 exp2f exp2l exp2 Returns the result of the exponential
function 2x. (Not implemented)
expm1 expm1f expm1l expm1 Returns the result of the exponential
function ex-1. (Not implemented)
log logf logl log Returns the natural logarithm ln(x),
x>0.
log10 log10f log10l log10 Returns the base-10 logarithm of x,
x>0.
log1p log1pf log1pl log1p Returns the base-e logarithm of
(1+x). x <> -1. (Not implemented)
log2 log2f log2l log2 Returns the base-2 logarithm of x.
x>0. (Not implemented)
ilogb ilogbf ilogbl ilogb Returns the signed exponent of x as
an integer. x>0. (Not implemented)
logb logbf logbl logb Returns the exponent of x as a signed
integer in value in floating-point
notation. x > 0. (Not implemented)
LIBRARIES
 Libraries 2-15

Rounding functions
Math.h Tgmath.h Description
ceil ceilf ceill ceil Returns the smallest integer not
less than x, as a double.
floor floorf floorl floor Returns the largest integer not
greater than x, as a double.
rint rintl rintf rint Returns the rounded integer
value as an int according to the
current rounding direction. See
fenv.h. (Not implemented)
lrint lrintf lrintl lrint Returns the rounded integer
value as a long int according
to the current rounding direction.
See fenv.h. (Not implemented)
llrint lrintf lrintl llrint Returns the rounded integer
value as a long long int
according to the current rounding
direction. See fenv.h.
(Not implemented)
nearbyint nearbyintf nearbyint Returns the rounded integer
nearbyintl value as a floating-point
according to the current rounding
direction. See fenv.h.
(Not implemented)
round roundl roundf round Returns the nearest integer
value of x as int.
(Not implemented)
lround lroundl lroundf lround Returns the nearest integer
value of x as long int.
(Not implemented)
llround llroundl llroundf llround Returns the nearest integer
value of x as long long int.
(Not implemented)
trunc truncl truncf trunc Returns the truncated integer
value x. (Not implemented)

• • • • • • • •
 2-16 TriCore Reference Manual

Remainder after devision

Math.h Tgmath.h Description
fmod fmodl fmodf fmod Returns the remainder r of
x-ny. n is chosen as
trunc(x/y). r has the same
sign as x.
remainder remainderl remainder Returns the remainder r of
remainderf x-ny. n is chosen as
trunc(x/y). r may not have the
same sign as x. (Not implement
ed)
remquo remquol remquof remquo Same as remainder. In addition,
the argument *quo is given a
specific value (see ISO).
(Not implemented)

frexp, ldexp, modf, scalbn, scalbln

Math.h Tgmath.h Description
frexp frexpl frexpf frexp Splits a float x into fraction f and
exponent n, so that:
f = 0.0 or 0.5 ≤ | f | ≤ 1.0 and
f*2 n = x. Returns f, stores n.
ldexp ldexpl ldexpf ldexp Inverse of frexp. Returns the
result of x*2n.
(x and n are both arguments).
modf modfl modff - Splits a float x into fraction f and
integer n, so that:
| f | < 1.0 and f+n=x. Returns f,
stores n.
scalbn scalbnl scalbnf scalbn Computes the result of
x*FLT_RADIXn. efficiently, not
LIBRARIES

normally by computing
FLT_RADIXn explicitly.
scalbln scalblnl scalblnf scalbln Same as scalbn but with
argument n as long int.
 Libraries 2-17

Power and absolute-value functions

Math.h Tgmath.h Description
cbrt cbrtl cbrtf cbrt Returns the real cube root of x
(=x1/3). (Not implemented)
fabs fabsl fabsf fabs Returns the absolute value of x
(|x|). (abs, labs, llabs, div,
ldiv, lldiv are defined in
stdlib.h)
fma fmal fmaf fma Floating-point multiply add. Re
turns x*y+z. (Not implemented)
hypot hypotl hypotf hypot Returns the square root of
x2+y2.
pow powl powf power Returns x raised to the power y
(xy).
sqrt sqrtl sqrtf sqrt Returns the non-negative
square root of x. x00.

Manipulation functions: copysign, nan, nextafter, nexttoward

Math.h Tgmath.h Description
copysign copysignl copysign Returns the value of x with the
copysignf sign of y.
nan nanl nanf - Returns a quiet NaN, if
available, with content indcated
through tagp.
(Not implemented)
nextafter nextafterl nextafter Returns the next representable
nextafterf value in the specified format
after x in the direction of y.
Returns y is x=y.
(Not implemented)
nexttoward nexttowardl nexttoward Same as nextafter, except
nexttowardf that the second argument in all
three variants is of type long
double. Returns y if x=y.
(Not implemented)

• • • • • • • •
 2-18 TriCore Reference Manual

Positive difference, maximum, minimum

Math.h Tgmath.h Description
fdim fdiml fdimf fdim Returns the positive difference
between: |x-y|.
(Not implemented)
fmax fmaxl fmaxf fmax Returns the maximum value of
their arguments.
(Not implemented)
fmin fminl fminf fmin Returns the minimum value of
their arguments.
(Not implemented)

Error and gamma (Not implemented)

Math.h Tgmath.h Description
erf erfl erff erf Computes the error function of x.
(Not implemented)
erfc erfcl erfcf erc Computes the complementary
error function of x.
(Not implemented)
lgamma lgammal lgammaf lgamma Computes the *loge|Γ(x)|
(Not implemented)
tgamma tgammal tgammaf tgamma Computes Γ(x)
(Not implemented)
LIBRARIES
 Libraries 2-19

Comparison macros
The next are implemented as macros. For any ordered pair of numeric
values exactly one of the relationships - less, greater, and equal - is true.
These macros are type generic and therefor do not have a parallel function
in tgmath.h. All arguments must be expressions of real-floating type.

Math.h Tgmath.h Description

isgreater - Returns the value of (x) > (y)
isgreaterequal - Returns the value of (x) >= (y)
isless - Returns the value of (x) < (y)
islessequal - Returns the value of (x) <= (y)
islessgreater - Returns the value of (x) < (y) ||
(x) > (y)
isunordered - Returns 1 if its arguments are
unordered, 0 otherwise.

Classification macros
The next are implemented as macros. These macros are type generic and
therefor do not have a parallel function in tgmath.h. All arguments must
be expressions of real-floating type.

Math.h Tgmath.h Description

fpclassify - Returns the class of its argument:
FP_INFINITE, FP_NAN, FP_NORMAL,
FP_SUBNORMAL or FP_ZERO
isfinite - Returns a nonzero value if and only if
its argument has a finite value
isinf - Returns a nonzero value if and only if
its argument has an infinit value
isnan - Returns a nonzero value if and only if
its argument has NaN value.
isnormal - Returns a nonzero value if an only if
its argument has a normal value.
signbit - Returns a nonzero value if and only if
its argument value is negative.

• • • • • • • •
 2-20 TriCore Reference Manual

2.2.14 SETJMP.H
The setjmp and longjmp in this header file implement a primitive form
of nonlocal jumps, which may be used to handle exceptional situations.
This facility is traditionally considered more portable than signal.h.

int setjmp(jmp_buf env) Records its caller's environment in env and

returns 0.
void longjmp(jmp_buf env, Restores the environment previously saved
int status) with a call to setjmp().

2.2.15 SIGNAL.H
Signals are possible asynchronous events that may require special
processing. Each signal is named by a number. The following signals are
defined:

SIGINT 1 Receipt of an interactive attention signal

SIGILL 2 Detection of an invalid function message
SIGFPE 3 An errouneous arithmetic operation (for example, zero
devide, overflow)
SIGSEGV 4 An invalid access to storage
SIGTERM 5 A termination request sent to the program
SIGABRT 6 Abnormal terminiation, such as is initiated by the
abort function.

The next function sends the signal sig to the program:

int raise(int sig)

The next function determines how subsequent signals will be handled:

signalfunction *signal (int, signalfunction *);

LIBRARIES

The first argument specifies the signal, the second argument points to the
signal-handler function or has one of the following values:

SIG_DFL Default behaviour is used

SIG_IGN The signal is ignored

The function returns the previous value of signalfunction for the

specific signal, or SIG_ERR if an error occurs.
 Libraries 2-21

2.2.16 STDARG.H
The facilities in this header file gives you a portable way to access variable
arguments lists, such as needed for as fprintf and vfprintf. This
header file contains the following macros:

va_arg(ap,type) Returns the value of the next argument in the

variable argument list. It's return type has the
type of the given argument type. A next call to
this macro will return the value of the next
argument.
va_end(va_list ap) This macro must be called after the arguments
have been processed. It should be called before
the function using the macro 'va_start' is
terminated (ANSI specification).
va_start( va_list ap, This macro initializes ap. After this call, each call
lastarg ); to va_arg() will return the value of the next
argument. In our implementation, va_list
cannot contain any bit type variables. Also the
given argument lastarg must be the last
non-bit type argument in the list.

2.2.17 STDBOOL.H
This header file contains the following macro definitions. These names for
boolean type and values are consisten with C++. You are allowed to
#undefine or redefine the macros below.

#define bool _Bool

#define true 1
#define false 0
#define __bool_true_false_are_defined 1

• • • • • • • •
 2-22 TriCore Reference Manual

2.2.18 STDDEF.H
This header file defines the types for common use:

ptrdiff_t signed integer type of the result of subtracting two pointers.

size_t unsigned integral type of the result of the sizeof operator.
wchar_t integer type to represent character codes in large character sets.

Besides these types, the following macros are defined:

NULL expands to the null pointer constant

offsetof(_type,_member) expands to an integer constant expression with
type size_t that is the offset in bytes of _mem
ber within structure type _type.

2.2.19 STDINT.H

See section 2.2.9, inttypes.h and stdint.h

2.2.20 STDIO.H AND WCHAR.H

Types
The header file stdio.h contains for performing input and output. A
number of also have a parallel wide character function or macro, defined
in wchar.h. The header file wchar.h also stdio.h.

In the C language, many I/O facilities are based on the concept of streams.
The stdio.h header file defines the data type FILE which holds the
information about a stream. An FILE object is created with the function
LIBRARIES

fopen. The pointer to this object is used as an argument in many of the in

this header file. The FILE object can contain the following information:
• the current position within the stream
• pointers to any associated buffers
• indications of for read/write errors
• end of file indication
The header file also defines type fpos_t as an unsigned long.
 Libraries 2-23

Macros
Stdio.h Description
BUFSIZ 512 Size of the buffer used by the setbuf/setvbuf function:
512
EOF -1 End of file indicator.
WEOF UINTMAX End of file indicator.
NOTE: WEOF need not to be a negative number as long
as its value does not correspond to a member of the
wide character set. (Defined in wchar.h).
FOPEN_MAX Number of files that can be opened simultaneously: 4
NOTE: According to ISO/IEC 9899 this value must be at
least 8.
FILENAME_MAX 100 Maximum length of a filename: 100
_IOFBF Expand to an integer expression, suitable for use as
_IOLBF argument to the setvbuf function.
_IONBF
L_tmpnam Size of the string used to hold temporary file names: 8
(tmpxxxxx)
TMP_MAX 0x8000 Maximum number of unique temporary filenames that
can be generated: 0x8000
stderr Expressions of type "pointer to FILE" that point to the
stdin FILE objects associated with standard error, input and
stdout output streams.

• • • • • • • •
 2-24 TriCore Reference Manual

Low level file access functions

Stdio.h Description
_close(fd) Used by the functions close and fclose.
(FSS implementation)
_lseek(fd,offset,whence) Used by all file positioning functions: fgetpos,
fseek, fsetpos, ftell, rewind.
(FSS implementation)
_open(fd,flags) Used by the functions fopen and freopen.
(FSS implementation)
_read(fd,*buff,cnt) Reads a sequence of characters from a file.
(FSS implementation)
_unlink(*name) Used by the function remove.
(FSS implementation)
_write(fd,*buffer,cnt) Writes a sequence of characters to a file.
(FSS implementation)

File access
Stdio.h Description
fopen(name,mode) Opens a file for a given mode. Available
modes are:
"r" read; open text file for reading
"w" write; create text file for writing;
if the file already exists its contents is
discarded
"a" append; open existing text file or create
new text file for writing at end of file
"r+" open text file for update; reading and
writing
"w+" create text file for update; previous
contents if any is discarded
LIBRARIES

"a+" append; open or create text file for

update, writes at end of file
(FSS implementation)
fclose(name) Flushes the data stream and closes the
specified file that was previously opened with
fopen. (FSS implementation)
fflush(name) If stream is an output stream, any buffered
but unwritten date is written. Else, the effect
is undefined. (FSS implementation)
 Libraries 2-25

Stdio.h Description
freopen(name,mode,stream) Similar to fopen, but rather then generating a
new value of type FILE *, the existing value
is associated with a new stream.
(FSS implementation)
setbuf(stream,buffer) If buffer is NULL, buffering is turned off for
the stream. Otherwise, setbuf is equivalent
to:
(void)setvbuf(stream,buf,_IOFBF,
BUFSIZ).
setvbuf(stream,buffer, Controls buffering for the stream; this
mode,size) function must be called before reading or
writing. Mode can have the following values:
_IOFBF causes full buffering
_IOLBF causes line buffering of text files
_IONBF causes no buffering
If buffer is not NULL, it will be used as a
buffer; otherwise a buffer will be allocated.
size determines the buffer size.

Character input/output
The format string of printf related functions can contain plain text
mixed with conversion specifiers. Each conversion specifier should be
preceded by a '%' character. The conversion specifier should be build in
order:
- Flags (in any order):
- specifies left adjustment of the converted argument.
+ a number is always preceded with a sign character.
+ has higher precedence than space.
space a negative number is preceded with a sign, positive
numbers with a space.
0 specifies padding to the field width with zeros (only for
numbers).
# specifies an alternate output form. For o, the first digit will
be zero. For x or X, "0x" and "0X" will be prefixed to the
number. For e, E, f, g, G, the output always contains a
decimal point, trailing zeros are not removed.

• • • • • • • •
 2-26 TriCore Reference Manual

- A number specifying a minimum field width. The converted

argument is printed in a field with at least the length specified here.
If the converted argument has fewer characters than specified, it will
be padded at the left side (or at the right when the flag '-' was
specified) with spaces. Padding to numeric fields will be done with
zeros when the flag '0' is also specified (only when padding left).
Instead of a numeric value, also '*' may be specified, the value is
then taken from the next argument, which is assumed to be of type
int.
- A period. This separates the minimum field width from the
precision.
- A number specifying the maximum length of a string to be printed.
Or the number of digits printed after the decimal point (only for
floating-point conversions). Or the minimum number of digits to be
printed for an integer conversion. Instead of a numeric value, also
'*' may be specified, the value is then taken from the next
argument, which is assumed to be of type int.
- A length modifier 'h', 'l' or 'L'. 'h' indicates that the argument is to
be treated as a short or unsigned short number. 'l' should be used if
the argument is a long integer. 'L' indicates that the argument is a
long double.
Flags, length specifier, period, precision and length modifier are optional,
the conversion character is not. The conversion character must be one of
the following, if a character following '%' is not in the list, the behavior is
undefined:

Character Printed as
d, i int, signed decimal
o int, unsigned octal
x, X int, unsigned hexadecimal in lowercase or uppercase
LIBRARIES

respectively
u int, unsigned decimal
c int, single character (converted to unsigned char)
s char *, the characters from the string are printed until a NULL
character is found. When the given precision is met before,
printing will also stop
f double
e, E double
g, G double
 Libraries 2-27

Character Printed as
n int *, the number of characters written so far is written into the
argument. This should be a pointer to an integer in default
memory. No value is printed.
p pointer (hexadecimal 24-bit value)
% No argument is converted, a '%' is printed.

Table 2-2: Printf conversion characters

All arguments to the scanf related functions should be pointers to

variables (in default memory) of the type which is specified in the format
string.

The format string can contain :

- Blanks or tabs, which are skipped.
- Normal characters (not '%'), which should be matched exactly in the
input stream.
- Conversion specifications, starting with a '%' character.
Conversion specifications should be built as follows (in order) :
- A '*', meaning that no assignment is done for this field.
- A number specifying the maximum field width.
- The conversion characters d, i, n, o, u and x may be preceede by
'h' if the argument is a pointer to short rather than int, or by 'l'
(letter ell) if the argument is a pointer to long. The conversion
characters e, f, and g may be preceede by 'l' if a pointer double
rather than float is in the argument list, and by 'L' if a pointer to a
long double.
- A conversion specifier. '*', maximum field width and length modifier
are optional, the conversion character is not. The conversion
character must be one of the following, if a character following '%'
is not in the list, the behavior is undefined.
Length specifier and length modifier are optional, the conversion character
is not. The conversion character must be one of the following, if a
character following '%' is not in the list, the behavior is undefined.

• • • • • • • •
 2-28 TriCore Reference Manual

Character Scanned as
d int, signed decimal.
i int, the integer may be given octal (i.e. a leading 0 is entered)
or hexadecimal (leading "0x" or "0X"), or just decimal.
o int, unsigned octal.
u int, unsigned decimal.
x int, unsigned hexadecimal in lowercase or uppercase.
c single character (converted to unsigned char).
s char *, a string of non white space characters. The argument
should point to an array of characters, large enough to hold the
string and a terminating NULL character.
f float
e, E float
g, G float
n int *, the number of characters written so far is written into the
argument. No scanning is done.
p pointer; hexadecimal 24-bit value which must be entered
without 0x- prefix.
[...] Matches a string of input characters from the set between the
brackets. A NULL character is added to terminate the string.
Specifying []...] includes the ']' character in the set of scanning
characters.
[^...] Matches a string of input characters not in the set between the
brackets. A NULL character is added to terminate the string.
Specifying [^]...] includes the ']' character in the set.
% Literal '%', no assignment is done.

Table 2-3: Scanf conversion characters

LIBRARIES
 Libraries 2-29

Stdio.h Wchar.h Description

fgetc(stream) fgetwc(stream) Reads one character from
stream. Returns the read
character, or EOF/WEOF on
error. (FSS implementation)
getc(stream) getwc(stream) Same as fgetc/fgetwc
except that is implemented
as a macro.
(FSS implementation)
NOTE: Currently #defined
as getchar()/getwchar()
because FILE I/O is not
supported. Returns the read
character, or EOF/WEOF on
error.
getchar(stdin) getwchar(stdin) Reads one character from
the stdin stream. Returns
the character read or
EOF/WEOF on error.
Implemented as macro.
(FSS implementation)
fgets(*s,n, fgetws(*s,n, Reads at most the next n-1
stream) stream) characters from the stream
into array s until a newline is
found. Returns s or NULL or
EOF/WEOF on error.
(FSS implementation)
gets(*s,n,stdin) - Reads at most the next n-1
characters from the stdin
stream into array s. A
newline is ignored. Returns
s or NULL or EOF/WEOF on
error. (FSS implementation)
ungetc(c,stream) ungetwc(c,stream) Pushes character c back
onto the input stream.
Returns EOF/WEOF on
error.
fscanf(stream, fwscanf(stream, Performs a formatted read
format,...) format,...) from the given stream.
Returns the number of items
converted succesfully.
(FSS implementation)

• • • • • • • •
 2-30 TriCore Reference Manual

Stdio.h Wchar.h Description

scanf(format,...) wscanf(format,...) Performs a formatted read
from stdin. Returns the
number of items converted
succesfully.
(FSS implementation)
sscanf(*s, swscanf(*s, Performs a formatted read
format,...) format,...) from the string s. Returns
the number of items
converted succesfully.
vfscanf(stream, vfwscanf(stream, Same as fscanf/fwscanf,
format,arg) but extra arguments are
format,arg) given as variable argument
list arg. (See section 2.2.16,
stdarg.h)
vscanf(format,arg) vwscanf(format, Same as sscanf/swscanf,
arg) but extra arguments are
given as variable argument
list arg. (See section 2.2.16,
stdarg.h)
vsscanf(*s, vswscanf(*s, Same as scanf/wscanf, but
format,arg) format,arg) extra arguments are given
as variable argument list
arg. (See section 2.2.16,
stdarg.h)
fputc(c,stream) fputwc(c,stream) Put character c onto the
given stream. Returns
EOF/WEOF on error.
(FSS implementation)
putc(c,stream) putwc(c,stream) Same as fpuc/fputwc
except that is implemented
as a macro.
(FSS implementation)
LIBRARIES

putchar(c,stdout) putwchar(c,stdout) Put character c onto the

stdout stream. Returns
EOF/WEOF on error.
Implemented as macro.
(FSS implementation)
fputs(*s,stream) fputws(*s,stream) Writes string s to the given
stream. Returns EOF/WEOF
on error.
(FSS implementation)
 Libraries 2-31

Stdio.h Wchar.h Description

puts(*s) - Writes string s to the stdout
stream. Returns EOF/WEOF
on error.
(FSS implementation)
fprintf(stream, fwprintf(stream, Performs a formatted write
format,...) format,...) to the given stream. Returns
EOF/WEOF on error.
(FSS implementation)
printf(format,...) wprintf(format,...) Performs a formatted write
to the stream stdout.
Returns EOF/WEOF on
error. (FSS implementation)
sprintf(*s, - Performs a formatted write
format,...) to string s. Returns
EOF/WEOF on error.
snprintf(*s,n swprintf(*s,n Same as sprintf, but n
format,...) format,...) specifies the maximum
number of characters
(including the terminating
null character) to be written.
vfprintf(stream, vfwprintf(stream, Same as
format,arg) format,arg) fprintf/fwprintf, but
extra arguments are given
as variable argument list
arg. (See section 2.2.16,
stdarg.h)
(FSS implementation)
vprintf(format, vwprintf(format, Same as printf/wprintf,
arg) arg) but extra arguments are
given as variable argument
list arg. (See section 2.2.16,
stdarg.h)
(FSS implementation)
vsprintf(*s, vswprintf(*s, Same as
format,arg) format,arg) sprintf/swprintf, but
extra arguments are given
as variable argument list
arg. (See section 2.2.16,
stdarg.h)

• • • • • • • •
 2-32 TriCore Reference Manual

Direct input/output
Stdio.h Description
fread(ptr,size,nobj,stream) Reads nobj members of size bytes
from the given stream into the array
pointed to by ptr. Returns the number of
elements succesfully read.
(FSS implementation)
fwrite((ptr,size,nobj,stream) Writes nobj members of size bytes from
to the array pointed to by ptr to the
given stream. Returns the number of
elements succesfully written.
(FSS implementation)

Random access
Stdio.h Description
fseek(stream,offset, Sets the position indicator for stream.
origin) (FSS implementation)

When repositioning a binary file, the new position origin is given by the following
macros:
SEEK_SET 0 offset characters from the beginning of the file
SEEK_CUR 1 offset characters from the current position in the file
SEEK_END 2 offset characters from the end of the file

ftell(stream) Returns the current file position for stream, or -1L

on error. (FSS implementation)
rewind(stream) Sets the file position indicator for the stream to the
beginning of the file. This function is equivalent to:
(void) fseek( stream, 0L, SEEK_SET );
clearerr( stream );
(FSS implementation)
LIBRARIES

fgetpos(stream,pos) Stores the current value of the file position

indicator for stream in the object pointed to by pos.
(FSS implementation)
fsetpos(stream,pos) Positions stream at the position recorded by
fgetpos in *pos. (FSS implementation)
 Libraries 2-33

Operations on files
Stdio.h Description
remove(file) Removes the named file, so that a subsequent
attempt to open it fails. Returns a non-zero value if
not succesful.
rename(old,new) Changes the name of the file from old name to new
name. Returns a non-zero value if not succesful.
tmpfile() Creates a temporary file of the mode "wb+" that will be
automatically removed when closed or when the
program terminates normally. Returns a file pointer.
tmpnam(buffer) Creates new file names that do not conflict with other
file names currently in use. The new file name is
stored in a buffer which must have room for
L_tmpnam characters. Returns a pointer to the
temporary name. The file names are created in the
current directory and all start with "tmp". At most
TMP_MAX unique file names can be generated.

Error handling
Stdio.h Description
clearerr(stream) Clears the end of file and error indicators for stream.
ferror(stream) Returns a non-zero value if the error indicator for
stream is set.
feof(stream) Returns a non-zero value if the end of file indicator for
stream is set.
perror(*s) Prints s and the error message belonging to the inte
ger errno. (See section 2.2.4, errno.h)

2.2.21 STDLIB.H AND WCHAR.H

The header file stdlib.h contains general utility functions which fall into
the following categories (Some have parallel wide-character, declared in
wchar.h)
• Numeric conversions
• Random number generation
• Memory management
• Envirnoment communication
• Searching and sorting

• • • • • • • •
 2-34 TriCore Reference Manual

• Integer arithmetic
• Multibyte/wide character and string conversions.

Macros
RAND_MAX 32767 Highest number that can be returned by the
rand/srand function.
EXIT_SUCCES 0 Predefined exit codes that can be used in the exit
EXIT_FAILURE 1 function.
MB_CUR_MAX 1 Maximum number of bytes in a multibyte character
for the extended character set specified by the
current locale (category LC_CTYPE, see section
2.2.12, locale.h).

Numeric conversions
Next functions convert the intial portion of a string *s to a double, int,
long int and long long int value respectively.

double atof(*s)
int atoi(*s)
long atol(*s)
long long atoll(*s)

Next functions convert the initial portion of the string *s to a float, double
and long double value respectively. *endp will point to the first character
not used by the conversion.

Stdlib.h Wchar.h
float strtof(*s,**endp) float wcstof(*s,**endp)
double strtod(*s,**endp) double wcstod(*s,**endp)
long double strtold(*s,**endp) long double wcstold(*s,**endp)
LIBRARIES
 Libraries 2-35

Next functions convert the initial portion of the string *s to a long, long
long, unsigned long and unsigned long long respectively. Base
specifies the radix. *endp will point to the first character not used by the
conversion.

Stdlib.h Wchar.h
long strtol (*s,**endp,base) long wcstol (*s,**endp,base)
long long strtoll long long wcstoll
(*s,**endp,base) (*s,**endp,base)
unsigned long strtoul unsigned long wcstoul
(*s,**endp,base) (*s,**endp,base)
unsigned long long strtoull unsigned long long wcstoull
(*s,**endp,base) (*s,**endp,base)

Random number generation

rand Returns a pseudo random integer in the range 0 to
RAND_MAX.
srand(seed) Same as rand but uses seed for a new sequence of
pseudo random numbers.

Memory management
malloc(size) Allocates space for an object with size size.
The allocated space is not initialized. Returns a
pointer to the allocated space.
calloc(nobj,size) Allocates space for n objects with size size.
The allocated space is initialized with zeros. Returns
a pointer to the allocated space.
free(*ptr) Deallocates the memory space pointed to by ptr
which should be a pointer earlier returned by the
malloc or calloc function.
realloc(*ptr,size) Deallocates the old object pointed to by ptr and
returns a pointer to a niew object with size size.
The new object cannot have a size larger than the
previous object.

• • • • • • • •
 2-36 TriCore Reference Manual

Environment communication
abort() Causes abnormal program termination. If the signal
SIGABRTis caught, the signal handler may take over
control. (See section 2.2.15, signal.h).
atexit(*func) Func points to a function that is called (without
arguments) when the program normally terminates.
exit(status) Causes normal program termination. Acts as if
main() returns with status as the return value.
Status can also be specified with the predefined
macros EXIT_SUCCES or EXIT_FAILURE.
_Exit(status) Same as exit, but not registered by the atexit
function or signal handlers registerd by the signal
function are called.
getenv(*s) Searches an environment list for a string s. Returns a
pointer to the contents of s.
NOTE: this function is not implemented because
there is no OS.
system(*s) Passes the string s to the environment for execution.
NOTE: this function is not implemented because
there is no OS.

Searching and sorting

bsearch(*key,*base, This function searches in an array of n members,
n,size,*cmp) for the object pointed to by key. The initial base of
the array is given by base. The size of each
member is specified by size. The given array must
be sorted in ascending order, according to the
results of the function pointed to by cmp. Returns a
pointer to the matching member in the array, or
NULL when not found.
qsort(*base,n, This function sorts an array of n members using the
size,*cmp) quick sort algorithm. The initial base of the array is
LIBRARIES

given by base. The size of each member is

specified by size. The array is sorted in ascending
order, according to the results of the function
pointed to by cmp.
 Libraries 2-37

Integer arithmetic
int abs(j) Compute the absolute value of an int, long int,
long labs(j) and long long int j resepectively.
long long llabs(j)
div_t div(x,y) Compute x/y and x%y in a single operation. X and
ldiv_t ldiv(x,y) y have respectively type int, long int and
lldiv_t lldiv(x,y) long long int. The result is stored in the
members quot and rem of struct div_t,
ldiv_t and lldiv_t which have the same types.

Multibyte/wide character and string conversions

mblen(*s,n) Determines the number of bytes in the multi-byte
character pointed to by s. At most n characters will
be examined. (See also mbrlen in section 2.2.25,
wchar.h)
mbtowc(*pwc,*s,n) Converts the multi-byte character in s to a
wide-character code and stores it in pwc. At most
n characters will be examined.
wctomb(*s,wc) Converts the wide-character wc into a multi-byte
representation and stores it in the string pointed to
by s. At most MB_CUR_MAX characters are
stored.
mbstowcs(*pwcs,*s,n) Converts a sequence of multi-byte characters in
the string pointed to by s into a sequence of wide
characters and stores at most n wide characters
into the array pointed to by pwcs. (See also
mbsrtowcs in section 2.2.25, wchar.h)
wcstombs(*s,*pwcs,n) Converts a sequence of wide characters in the
array pointed to by pwcs into multi-byte characters
and stores at most n multi-byte characters into the
string pointed to by s. (See also wcsrtowmb in
section 2.2.25, wchar.h)

2.2.22 STRING.H AND WCHAR.H

This header file provides numerous functions for manipulating strings. By
convention, strings in C are arrays of characters with a terminating null
character. Most functions therefore take arguments of type *char.
However, many functions have also parallel wide-character functions
which take arguments of type *wchar_t. These functions are declared in
wchar.h.

• • • • • • • •
 2-38 TriCore Reference Manual

Copying and concatenation functions

Stdio.h Wchar.h Description
memcpy(*s1,*s2,n) wmemcpy(*s1,*s2,n) Copies n characters from
*s2 into *s1 and returns *s1.
If *s1 and *s2 overlap the
result is undefined.
memmove(*s1,*s2,n) wmemmove(*s1,*s2,n) Same as memcpy, but
overlapping strings are
handled correctly. Returns
*s1.
strcpy(*s1,*s2) wcscpy(*s1,*s2) Copies *s2 into *s1 and
returns *s1. If *s1 and *s2
overlap the result is
undefined.
strncpy(*s1,*s2,n) wcsncpy(*s1,*s2,n) Copies not more than n
characters from *s2 into *s1
and returns *s1. If *s1 and
*s2 overlap the result is
undefined.
strcat(*s1,*s2) wcscat(*s1,*s2) Appends a copy of *s2 to
*s1 and returns *s1. If *s1
and *s2 overlap the result is
undefined.
strncat(*s1,*s2,n) wcsncat(*s1,*s2,n) Appends not more than n
characters from *s2 to *s1
and returns *s1. If *s1 and
*s2 overlap the result is
undefined.
LIBRARIES
 Libraries 2-39

Comparison functions
Stdio.h Wchar.h Description
memcmp(*s1,*s2,n) wmemcmp(*s1,*s2,n) Compares the first n
characters of *s1 to the first n
characters of *s2. Returns
< 0 if *s1 < *s2, 0 if *s1 = =
*s2, or > 0 if *s1 > *s2.
strcmp(*s1,*s2) wcscmp(*s1,*s2) Compares string *s1 to *s2.
Returns < 0 if *s1 < *s2, 0 if
*s1 = = *s2, or > 0 if *s1 >
*s2.
strncmp(*s1,*s2,n) wcsncmp(*s1,*s2,n) Compares the first n
characters of *s1 to the first n
characters of *s2. Returns <
0 if *s1 < *s2, 0 if *s1 = = *s2,
or > 0 if *s1 > *s2.
strcoll(*s1,*s2) wcscoll(*s1,*s2) Performs a local-specific
comparison between string
*s1 and string *s2 according
to the LC_COLLATE
category of the current
locale. Returns < 0 if *s1 <
*s2, 0 if *s1 = = *s2, or > 0 if
*s1 > *s2. (See section
2.2.12, locale.h)
strxfrm(*s1,*s2,n) wcsxfrm(*s1,*s2,n) Transforms (a local) string
*s2 so that a comparison
between transformed strings
with strcmp gives the same
result as a comparison
between non-transformed
strings with strcoll.
Returns the transformed
string *s1.

• • • • • • • •
 2-40 TriCore Reference Manual

Search functions
Stdio.h Wchar.h Description
memchr(*s,c,n) wmemchr(*s,c,n) Checks the first n characters of
*s on the occurence of character
c. Returns a pointer to the found
character.
strchr(*s,c) wcschr(*s,c) Returns a pointer to the first
occurence of character c in *s or
the null pointer if not found.
strrchr(*s,c) wcsrchr(*s,c) Returns a pointer to the last
occurence of character c in *s or
the null pointer if not found.
strspn(*s,*set) wcsspn(*s,*set) Searches *s for a sequence of
characters specified in *set.
Returns the length of the first
sequence found.
strcspn(*s,*set) wcscspn(*s,*set) Searches *s for a sequence of
characters not specified in *set.
Returns the length of the first
sequence found.
strpbrk(*s,*set) wcspbrk(*s,*set) Same as strspn/wcsspn but
returns a pointer to the first
character in *s that also is
specified in *set.
strstr(*s,*sub) wcsstr(*s,*sub) Searches for a substring *sub in
*s. Returns a pointer to the first
occurence of *sub in *s.
strtok(*s,*dlm) wcstok(*s,*dlm) A sequence of calls to this
function breaks the string *s into
a sequence of tokens delimited
by a character specified in *dlm.
The token found in *s is
LIBRARIES

terminated with a null character.

Returns a pointer to the first
position in *s of the token.
 Libraries 2-41

Miscellaneous functions
Stdio.h Wchar.h Description
memset(*s,c,n) wmemset(*s,c,n) Fills the first n bytes of *s with
character c and returns *s.
strerror(errno) - Typically, the values for errno
come from int errno. This
function returns a pointer to the
associated error message.
(See also section 2.2.4, errno.h)
strlen(*s) wcslen(*s) Returns the length of string *s.

2.2.23 TIME.H AND WCHAR.H

The header file time.h provides facilities to retrieve and use the
(calendar) date and time, and the process time. Time can be represented
as an integer value, or can be broken-down in components. Two
arithmetic data types are defined which are capable of holding the integer
representation of times:

clock_t unsigned long long

time_t unsigned long

The type struct tm below is defined according to ISO/IEC9899 with one

exception: this implementation does not support leap seconds. The
struct tm type is defines as follows:
struct tm
{
int tm_sec; /* seconds after the minute - [0, 59] */
int tm_min; /* minutes after the hour - [0, 59] */
int tm_hour; /* hours since midnight - [0, 23] */
int tm_mday; /* day of the month - [1, 31] */
int tm_mon; /* months since January - [0, 11] */
int tm_year; /* year since 1900 */
int tm_wday; /* days since Sunday - [0, 6] */
int tm_yday; /* days since January 1 - [0, 365] */
int tm_isdst; /* Daylight Saving Time flag */
};

• • • • • • • •
 2-42 TriCore Reference Manual

Time manipulation
clock Returns the application's best approximation to the
processor time used by the program since it was
started. This low-level routine is not implemented
because it strongly depends on the hardware. To
determine the time in seconds, the result of clock
should be divided by the value defined as
CLOCKS_PER_SEC 12000000
difftime(t1,t0) Returns the difference t1-t0 in seconds.
mktime(tm *tp) Converts the broken-down time in the structure
pointed to by tp, to a value of type time_t. The
return value has the same encoding as the return
value of the time function.
time(*timer) Returns the current calendar time. This value is also
assigned to *timer.

Time conversion
asctime(tm *tp) Converts the broken-down time in the structure
pointed to by tp into a string in the form Mon Jan 21
16:15:14 2004\n\0. Returns a pointer to this
string.
ctime(*timer) Converts the calender time pointed to by timer to
local time in the form of a string. This is equivalent to:
asctime(localtime(timer))
gmtime(*timer) Converts the calender time pointed to by timer to the
broken-down time, expressed as UTC. Returns a
pointer to the broken-down time.
localtime(*timer) Converts the calendar time pointed to by timer to the
broken-down time, expressed as local time. Returns
a pointer to the broken-down time.
LIBRARIES
 Libraries 2-43

Formatted time
The next function has a parallel function defined in wchar.h:

Stdio.h Wchar.h
strftime(*s,smax,*fmt,tm *tp) wstrftime(*s,smax,*fmt,tm *tp)

Formats date and time information from struct tm *tp into *s according
to the specified format *fmt. No more than smax characters are placed into
*s. The formatting of strftime is locale-specific using the LC_TIME
category (see section 2.2.12, locale.h). You can use the next conversion
specifiers:

%a abbreviated weekday name

%A full weekday name
%b abbreviated month name
%B full month name
%c local date and time representation
%d day of the month (01-31)
%H hour, 24-hour clock (00-23)
%I hour, 12-hour clock (01-12)
%j day of the year (001-366)
%m month (01-12)
%M minute (00-59)
%p local equivalent of AM or PM
%S second (00-59)
%U week number of the year, Sunday as first day of the week (00-53)
%w weekday (0-6, Sunday is 0)
%W week number of the year, Monday as first day of the week (00-53)
%x local date representation
%X local time representation
%y year without century (00-99)
%Y year with century
%Z time zone name, if any
%% %

• • • • • • • •
 2-44 TriCore Reference Manual

2.2.24 UNISTD.H
The file unistd.h contains standard UNIX I/O functions. These functions
are all implemented using CrossView Pro's file system simulation. This
header file is not defined in ISO/IEC9899.

access(*name,mode) Use the file system simulation of CrossView Pro to

check the permissions of a file on the host. mode
specifies the type of access and is a bit pattern
constructed by a logical OR of the following values:
R_OK Checks read permission.
W_OK Checks write permission.
X_OK Checks execute (search) permission.
F_OK Checks to see if the file exists.
(FSS implementation)
chdir(*path) Use the file system simulation feature of CrossView
Pro to change the current directory on the host to
the directory indicated by path.
(FSS implementation)
close(fd) File close function. The given file descriptor should
be properly closed. This function calls _close().
(FSS implementation)
getcwd(*buf,size) Use the file system simulation feature of CrossView
Pro to retrieve the current directory on the host.
Returns the directory name. (FSS implementation)
lseek(fd,offset, Moves read-write file offset. Calls _lseek().
whence) (FSS implementation)
read(fd,*buff,cnt) Reads a sequence of characters from a file. This
function calls _read(). (FSS implementation)
stat(*name,*buff) Use the file system simulation feature of
CrossView Pro to stat() a file on the host platform.
(FSS implementation)
LIBRARIES

unlink(*name) Removes the named file, so that a subsequent

attempt to open it fails. Calls _unlink().
(FSS implementation)
write(fd,*buff,cnt) Write a sequence of characters to a file.
Calls _write(). (FSS implementation)
 Libraries 2-45

2.2.25 WCHAR.H
Many functions in wchar.h represent the wide-character variant of other
functions so these are discussed together. (See sections 2.2.20, stdio.h,
2.2.21, stdlib.h, 2.2.22, strings.h and 2.2.23, time.h).

The remaining functions are described below. They perform conversions

between multi-byte characters and wide characters. In these functions, ps
points to struct mbstate_t which holds the conversion state information
necessary to convert between sequences of multibyte characters and wide
characters:
typedef struct
{
wchar_t wc_value; /* wide character value solved
so far */
unsigned short n_bytes; /* number of bytes of solved
multibyte */
unsigned short encoding; /* encoding rule for wide
character <=> multibyte
conversion */
} mbstate_t;

When multibyte characters larger than 1 byte are used, this struct will be
used to store the conversion information when not all the bytes of a
particular multibyte character have been read from the source. In this
implementation, multi-byte characters are 1 byte long (MB_CUR_MAX and
MB_LEN_MAX are defined as 1) and this will never occur.

mbsinit(*ps) Determines whether the object pointed to

by ps, is an initial conversion state.
Returns a non-zero value if so.
mbsrtowcs(*pwcs,**src,n,*ps) Restartable version of mbstowcs. See
section 2.2.21, stdlib.h. The initial
conversion state is specified by ps. The
input sequence of multibyte charactersis
specified indirectly by src.
wcsrtombs(*s,**src,n,*ps) Restartable version of wcstombs. See
section 2.2.21, stdlib.h. The initial
conversion state is specified by ps. The
input wide string is specified indirectly by
src.
mbrtowc(*pwc,*s,n,*ps) Converts a multibyte character *s to a wide
character *pwc according to conversion
state ps. See also mbtowc in section
2.2.21, stdlib.

• • • • • • • •
 2-46 TriCore Reference Manual

wcrtomb(*s,wc,*ps) Converts a wide character wc to a

multi-byte character according to
conversion state ps and stores the
multi-byte character in *s.
btowc(c) Returns the wide character
corresponding to character c. Returns
WEOF on error.
wctob(c) Returns the multi-byte character
corresponding to the wide character c.
The returned multi-byte character is
represented as one byte. Returns EOF
on error.
mbrlen(*s,n,*ps) Inspects up to n bytes from the string *s
to see if those characters represent valid
multibyte characters, relative to the
conversion state held in *ps.

2.2.26 WCTYPE.H
Most functions in wctype.h represent the wide-character variant of
functions declared in ctype.h and are discussed in section 2.2.3, ctype.h.
In addition, this header file provides extensible, locale specific functions
and wide character classification.

wctype(*property) Constructs a value of type wctype_t that describes

a class of wide characters identified by the string
*property. If property identifies a valid class of wide
characters according to the LC_TYPE category (see
2.2.12, locale.h) of the current locale, a non-zero
value is returned that can be used as an argument
in the iswctype function.
iswctype(wc,desc) Tests whether the wide character wc is a member of
LIBRARIES

the class represented by wctype_t desc. Returns a

non-zero value if tested true.

Function Equivalent to locale specific test

iswalnum(wc) iswctype(wc,wctype("alnum"))
iswalpha(wc) iswctype(wc,wctype("alpha"))
iswcntrl(wc) iswctype(wc,wctype("cntrl"))
iswdigit(wc) iswctype(wc,wctype("digit"))
iswgraph(wc) iswctype(wc,wctype("graph"))
 Libraries 2-47

Function Equivalent to locale specific test

iswlower(wc) iswctype(wc,wctype("lower"))
iswprint(wc) iswctype(wc,wctype("print"))
iswpunct(wc) iswctype(wc,wctype("punct"))
iswspace(wc) iswctype(wc,wctype("space"))
iswupper(wc) iswctype(wc,wctype("upper"))
iswxditig(wc) iswctype(wc,wctype("xdigit"))

wctrans(*property) Constructs a value of type wctype_t that describes

a mapping between wide characters identified by the
string *property. If property identifies a valid mapping
of wide characters according to the LC_TYPE
category (see 2.2.12, locale.h) of the current locale,
a non-zero value is returned that can be used as an
argument in the towctrans function.
towctrans(wc,desc) Transforms wide character wc into another
wide-character, described by desc.

Function Equivalent to locale specific transformation

towlower(wc) towctrans(wc,wctrans("tolower")
towupper(wc) towctrans(wc,wctrans("toupper")

• • • • • • • •
 2-48 TriCore Reference Manual

2.3 C LIBRARY REENTRANCY

Some of the functions in the C library are reentrant, others are not. The
table below shows the functions in the C library, and whether they are
reentrant or not. A dash means that the function is reentrant. Note that
some of the functions are not reentrant because they set the global
variable 'errno' (or call other functions that eventually set 'errno'). If your
program does not check this variable and errno is the only reason for the
function not being reentrant, these functions can be assumed reentrant as
well.

The explanation of the cause why a function is not reentrant sometimes

refers to a footnote because the explanation is to lengthy for the table.

Function Not reentrant because

_close Uses global File System Simulation buffer,
fss_buffer
_doflt Uses I/O functions which modify iob[].
See (1).
_doprint Uses indirect access to static iob[] array.
See (1).
_doscan Uses indirect access to iob[] and calls un
getc (access to local static ungetc[] buffer).
See (1).
_Exit See exit.
_filbuf Uses iob[]. See (1).
_flsbuf Uses iob[]. See (1).
_getflt Uses iob[ ]. See (1).
_iob Defines static iob[]. See (1).
_ioread Depends on low level I/O implementation.
LIBRARIES

Uses iob[]. See (1).

_iowrite Depends on low level I/O implementation.
Uses iob[ ]. See (1).
_lseek Uses global File System Simulation buffer,
_fss_buffer
_open Uses global File System Simulation buffer,
_fss_buffer
_read Uses global File System Simulation buffer,
_fss_buffer
 Libraries 2-49

Function Not reentrant because

_unlink Uses global File System Simulation buffer,
_fss_buffer
_write Uses global File System Simulation buffer,
_fss_buffer
abort Calls exit
abs labs llabs -
access Uses global File System Simulation buffer,
_fss_buffer
acos acosf acosl Sets errno.
acosh acoshf acoshl Sets errno via calls to other functions.
asctime asctime defines static array for broken-
down time string.
asin asinf asinl Sets errno.
asinh asinhf asinhl Sets errno via calls to other functions.
atan atanf atanl -
atan2 atan2f atan2l -
atanh atanhf atanhl Sets errno via calls to other functions.
atexit atexit defines static array with function
pointers to execute at exit of program.
atof -
atoi -
atol -
bsearch -
btowc -
cabs cabsf cabsl Sets errno via calls to other functions.
cacos cacosf cacosl Sets errno via calls to other functions.
cacosh cacosh cfacoshl Sets errno via calls to other functions.
calloc calloc uses static buffer management
structures. See malloc (5).
carg cargf cargl -
casin casinf casinl Sets errno via calls to other functions.
casinh casinh cfasinhl Sets errno via calls to other functions.
catan catanf catanl Sets errno via calls to other functions.

• • • • • • • •
 2-50 TriCore Reference Manual

Function Not reentrant because

catanh catanhfcatanhl Sets errno via calls to other functions.
cbrt cbrtl cbrtf (Not implemented)
ccos ccosf ccosl Sets errno via calls to other functions.
ccosh ccoshf ccoshl Sets errno via calls to other functions.
ceil ceilf ceill -
cexp cexpf cexpl Sets errno via calls to other functions.
chdir Uses global File System Simulation buffer,
fss_buffer
cimag cimagf cimagl -
cleanup Calls fclose. See (1)
clearerr Modifies iob[]. See (1)
clock -
clog clogf clogl Sets errno via calls to other functions.
close Calls _close
conj conjf conjl -
copysign copysignl -
copysignf
cos cosf cosl -
cosh coshf coshl cosh calls exp(), which sets errno. If errno
is discarded, cosh is reentrant.
cpow cpowf cpowl Sets errno via calls to other functions.
cproj cprojf cprojl -
creal crealf creall -
csin csinf csinl Sets errno via calls to other functions.
csinh csinhf csinhl Sets errno via calls to other functions.
LIBRARIES

csqrt csqrtf csqrtl Sets errno via calls to other functions.

ctan ctanf ctanl Sets errno via calls to other functions.
ctanh ctanhf ctanhl Sets errno via calls to other functions.
ctime Calls asctime
difftime -
div ldiv lldiv -
erf erfl erff (Not implemented)
 Libraries 2-51

Function Not reentrant because

erfc erfcl erfcf (Not implemented)
exit Calls fclose indirectly which uses iob[]
calls functions in _atexit array. See (1).
To make exit reentrant kernel support is
required.
exp expf expl Sets errno.
exp2 exp2f exp2l (Not implemented)
expm1 expm1f expm1l (Not implemented)
fabs fabsf fabsl -
fclose Uses values in iob[]. See (1).
fdim fdiml fdimf (Not implemented)
feclearexcept (Not implemented)
fegetenv (Not implemented)
fegetexceptflag (Not implemented)
fegetround (Not implemented)
feholdexept (Not implemented)
feof Uses values in iob[]. See (1).
feraiseexcept (Not implemented)
ferror Uses values in iob[]. See (1).
fesetenv (Not implemented)
fesetexceptflag (Not implemented)
fesetround (Not implemented)
fetestexcept (Not implemented)
feupdateenv (Not implemented)
fflush Modifies iob[]. See (1).
fgetc fgetwc Uses pointer to iob[]. See (1).
fgetpos Sets the variable errno and uses pointer to
iob[]. See (1) / (2).
fgets fgetws Uses iob[]. See (1).
floor floorf floorl -
fma fmal fmaf (Not implemented)
fmax fmaxl fmaxf (Not implemented)
fmin fminl fminf (Not implemented)

• • • • • • • •
 2-52 TriCore Reference Manual

Function Not reentrant because

fmod fmodl fmodf -
fopen Uses iob[] and calls malloc when file open
for buffered IO. See (1)
fpclassify -
fprintffwprintf Uses iob[]. See (1).
fputc fputwc Uses iob[]. See (1).
fputs fputws Uses iob[]. See (1).
fread Calls fgetc. See (1).
free free uses static buffer management struc
tures. See malloc (5).
freopen Modifies iob[]. See (1).
frexp frexpl frexpf -
fscanf fwscanf Uses iob[]. See (1)
fseek Uses iob[] and calls _doscan.
Acesses ungetc[] array. See (1).
fsetpos Uses iob[] and sets errno. See (1) / (2).
ftell Uses iob[] and sets errno. Calls _lseek.
See (1) / (2).
fwrite Uses iob[]. See (1).
getc getwc Uses iob[]. See (1).
getchar`getwchar Uses iob[]. See (1).
getcwd Uses global File System Simulation buffer,
_fss_buffer
getenv Skeleton only.
gets getws Uses iob[ ]. See (1).
LIBRARIES

gmtime gmtime defines static structure

hypot hypotl hypotf Sets errno via calls to other functions.
ilogb ilogbf ilogbl (Not implemented)
imaxabs -
imaxdiv -
isalnum iswalnum -
isalpha iswalpha -
isascii iswascii -
 Libraries 2-53

Function Not reentrant because

iscntrl iswcntrl -
isdigit iswdigit -
isfinite -
isgraph iswgraph -
isgreater -
isgreaterequal -
isinf -
isless -
islessequal -
islessgreater -
islower iswlower -
isnan -
isnormal -
isprint iswprint -
ispunct iswpunct -
isspace iswspace -
isunordered -
isupper iswupper -
iswalnum -
iswalpha -
iswcntrl -
iswctype -
iswdigit -
iswgraph -
iswlower -
iswprint -
iswpunct -
iswspace -
iswupper -
iswxditig -
isxdigit iswxdigit -

• • • • • • • •
 2-54 TriCore Reference Manual

Function Not reentrant because

ldexp ldexpl ldexpf Sets errno. See (2).
lgamma lgammal lgammaf (Not implemented)
llrint lrintf lrintl (Not implemented)
llround llroundl llroundf (Not implemented)
localeconv N.A.; skeleton function
localtime
log logl logf Sets errno. See (2).
log10 log10l log10f Sets errno via calls to other functions.
log1p log1pf log1pl (Not implemented)
log2 log2f log2l (Not implemented)
logb logbf logbl (Not implemented)
longjmp -
lrint lrintf lrintl (Not implemented)
lround lroundl lroundf (Not implemented)
lseek Calls _lseek
malloc Needs kernel support. See (5).
mblen N.A., skeleton function
mbrlen Sets errno.
mbrtowc Sets errno.
mbsinit -
mbsrtowcs Sets errno.
mbstowcs N.A., skeleton function
mbtowc N.A., skeleton function
memchr wmemchr -
LIBRARIES

memcmp wmemcmp -
memcpy wmemcpy -
memmovewmemmove -
memset wmemset -
mktime -
modf modfl modff -
nan nanl nanf (Not implemented)
 Libraries 2-55

Function Not reentrant because

nearbyint nearbyintf (Not implemented)
nearbyintl
nextafter nextafterl (Not implemented)
nextafterf
nexttoward nexttowardl (Not implemented)
nexttowardf
offsetof -
open Calls _open
perror Uses errno. See (2)
pow powl powf Sets errno. See (2)
printf wprintf Uses iob[ ]. See (1)
putc putwc Uses iob[ ]. See (1)
putcharputwchar Uses iob[ ]. See (1)
puts Uses iob[ ]. See (1)
qsort -
raise Updates the signal handler table
rand Uses static variable to remember latest
random number. Must diverge from ANSI
standard to define reentrant rand. See (4).
read Calls _read
realloc See malloc (5).
remainder remainderl (Not implemented)
remainderf
remove N.A; skeleton only.
remquo remquol remquof (Not implemented)
rename N.A; skeleton only.
rewind N.A; skeleton only.
rint rintl rintf (Not implemented)
round roundl roundf (Not implemented)
scalbln scalblnl scalblnf -
scalbn scalbnl scalbnf -
scanf wscanf Uses iob[ ], calls _doscan. See (1).
setbuf Sets iob[ ]. See (1).
setjmp -

• • • • • • • •
 2-56 TriCore Reference Manual

Function Not reentrant because

setlocale N.A.; skeleton function
setvbuf Sets iob and calls malloc. See (1) / (5).
signal Updates the signal handler table
signbit -
sin sinf sinl -
sinh sinhf sinhl Sets errno via calls to other functions.
snprintf swprintf Sets errno. See (2).
sprintf Sets errno. See (2).
sqrt sqrtf sqrtl Sets errno. See (2).
srand See rand
sscanf swscanf Sets errno via calls to other functions.
stat Uses global File System Simulation buffer,
_fss_buffer
strcat wcscat -
strchr wcschr -
strcmp wcscmp -
strcoll wcscoll -
strcpy wcscpy -
strcspn wcscspn -
strerror -
strftime wstrftime -
strlen wcslen -
strncat wcsncat -
strncmp wcsncmp -
LIBRARIES

strncpy wcsncpy -
strpbrk wcspbrk -
strrchr wcsrchr -
strspn wcsspn -
strstr wcsstr -
strtod wcstod -
strtof wcstof -
strtoimax Sets errno via calls to other functions.
 Libraries 2-57

Function Not reentrant because

strtok wcstok Strtok saves last position in string in local
static variable. This function is not
reentrant by design. See (4).
strtol wcstol Sets errno. See (2).
strtold wcstold -
strtoul wcstoul Sets errno. See (2).
strtoull wcstoull Sets errno. See (2).
strtoumax Sets errno via calls to other functions.
strxfrm wcsxfrm -
system N.A; skeleton function
tan tanf tanl Sets errno. See (2).
tanh tanhf tanhl Sets errno via call to other functions.
tgamma tgammal tgammaf (Not implemented)
time Uses static variable which defines initial
start time
tmpfile Uses iob[ ]. See (1).
tmpnam Uses local buffer to build filename.
Function can be adapted to use user buff
er. This makes the function non ANSI. See
(4).
toascii -
tolower -
toupper -
towctrans -
towlower -
towupper -
trunc truncl truncf (Not implemented)
ungetc ungetwc Uses static buffer to hold ungetted charac
ters for each file. Can be moved into iob
structure. See (1).
unlink Calls _unlink
vfprintf vfwprintf Uses iob[ ]. See (1).
vfscanf vfwscanf Calls doscan
vprintf vwprintf Uses iob[ ]. See (1).

• • • • • • • •
 2-58 TriCore Reference Manual

Function Not reentrant because

vscanf vwscanf Calls doscan
vsprintf vswprintf Sets errno.
vsscanf vswscanf Sets errno.
wcrtomb Sets errno.
wcsrtombs Sets errno.
wcstoimax Sets errno via calls to other functions.
wcstombs N.A.; skeleton function
wcstoumax Sets errno via calls to other functions.
wctob -
wctomb N.A.; skeleton function
wctrans -
wctype -
write Calls _write

Table 2-4: C library reentrancy

Several functions in the C library are not reentrant due to the following
reasons:
- The iob[] structure is static. This influences all I/O functions.
- The ungetc[] array is static. This array holds the characters (one
for each stream) when ungetc() is called.
- The variable errno is globally defined. Numerous functions read or
modify errno
- _doprint and _doscan use static variables for e.g. character
counting in strings.
- Some string functions use locally defined (static) buffers. This is
LIBRARIES

prescribed by ANSI.
- malloc uses a static heap space.
The following description discusses these items into more detail. The
numbers at the begin of each paragraph relate to the number references in
the table above.
 Libraries 2-59

(1) iob structures

The I/O part of the C library is not reentrant by design. This is mainly
caused by the static declaration of the iob[] array. The functions which use
elements of this array access these elements via pointers ( FILE * ).

Building a multi-process system that is created in one link-run is hard to

do. The C language scoping rules for external variables make it difficult to
create a private copy of the iob[] array. Currently, the iob[] array has
external scope. Thus it is visible in every module involved in one link
phase. If these modules comprise several tasks (processes) in a system
each of which should have its private copy of iob[], it is apparent that
the iob[] declaration should be changed. This requires adaption of the
library to the multi-tasking environment. The library modules must use a
process identification as an index for determining which iob[] array to
use. Thus the library is suitable for interfacing to that kernel only.

Another approach for the iob[] declaration problem is to declare the

array static in one of the modules which create a task. Thus there can be
more than one iob[] array is the system without having conflicts at link
time. This brings several restrictions: Only the module that holds the
declaration of the static iob[] can use the standard file handles stdin,
stdout and stderr (which are the first three entries in iob[]). Thus all
I/O for these three file handles should be located in one module.

(2) errno declaration

Several functions in the C library set the global variable errno. After
completion of the function the user program may consult this variable to
see if some error occurred. Since most of the functions that set errno
already have a return type (this is the reason for using errno) it is not
possible to check successful completion via the return type.

The library routines can set errno to the values defined in errno.h. See
the file errno.h for more information.

errno can be set to ERR_FORMAT by the print and scan functions in the
C library if you specify illegal format strings.

errno will never be set to ERR_NOLONG or ERR_NOPOINT since the

Tricore C library supports long and pointer conversion routines for input
and output.

• • • • • • • •
 2-60 TriCore Reference Manual

errno can be set to ERANGE by the following functions: exp(),

strtol(), strtoul() and tan(). These functions may produce results
that are out of the valid range for the return type. If so, the result of the
function will be the largest representable value for that type and errno is
set to ERANGE.

errno is set to EDOM by the following functions: acos(), asin(),

log(), pow() and sqrt(). If the arguments for these functions are out of
their valid range ( e.g. sqrt( -1 ) ), errno is set to EDOM.

errno can be set to ERR_POS by the file positioning functions ftell(),

fsetpos() and fgetpos().

(3) ungetc
Currently the ungetc buffer is static. For each file entry in the iob[]
structure array, there is one character available in the buffer to unget a
character.

(4) local buffers

tmpnam() creates a temporary filename and returns a pointer to a local
static buffer. This is according to the ANSI definition. Changing this
function such that it creates the name in a user specified buffer requires
another calling interface. Thus the function would be no longer portable.

strtok() scans through a string and remembers that the string and the
position in the string for subsequent calls. This function is not reentrant by
design. Making it reentrant requires support of a kernel to store the
information on a per process basis.

rand() generates a sequence of random numbers. The function uses the

value returned by a previous call to generate the next value in the
sequence. This function can be made reentrant by specifying the previous
random value as one of the arguments. However, then it is no longer a
LIBRARIES

standard function.

(5) malloc
Malloc uses a heap space which is assigned at locate time. Thus this
implementation is not reentrant. Making a reentrant malloc requires some
sort of system call to obtain free memory space on a per process basis.
This is not easy to solve within the current context of the library. This
requires adaption to a kernel.
 Libraries 2-61

This paragraph on reentrancy applies to multi-process environments only.

If reentrancy is required for calling library functions from an exception
handler, another approach is required. For such a situation it is of no use
to allocate e.g. multiple iob[] structures. In such a situation several
pieces of code in the library have to be declared 'atomic': this means that
interrupts have to be disabled while executing an atomic piece of code.

• • • • • • • •
 2-62 TriCore Reference Manual
LIBRARIES
CHAPTER
TRICORE ASSEMBLY
LANGUAGE

3
 3-2 TriCore Reference Manual

CHAPTER
ASSEMBLY LANGUAGE

3
 TriCore Assembly Language 3-3

3.1 INTRODUCTION
This chapter contains a detailed description of all built-in assembly
functions directives and controls. For a description of the TriCore
instruction set, refer to the TriCore Architecture v1.3 Manual [2000,
Infineon].

3.2 BUILT-IN ASSEMBLY FUNCTIONS

3.2.1 OVERVIEW OF BUILT-IN ASSEMBLY FUNCTIONS

The built-in assembler functions are grouped into the following types:
• Mathematical functions comprise, among others, transcendental,
random value, and min/max functions.
• Conversion functions provide conversion between integer,
floating-point, and fixed point fractional values.
• String functions compare strings, return the length of a string, and
return the position of a substring within a string.
• Macro functions return information about macros.
• Address calculation functions return the high or low part of an
address.
• Assembler mode functions relating assembler operation.
The following tables provide an overview of all built-in assembler
functions. expr can be any assembly expression resulting in an integer
value. Expressions are explained in section 4.6, Assembly Expressions, in
chapter Assembly Language of the User's Manual.

• • • • • • • •
 3-4 TriCore Reference Manual

Overview of mathematical functions

Function Description
@ABS(expr) Absolute value
@ACS(expr) Arc cosine
@ASN(expr) Arc sine
@AT2(expr1,expr2) Arc tangent
@ATN(expr) Arc tangent
@CEL(expr) Ceiling function
@COH(expr) Hyperbolic cosine
@COS(expr) Cosine
@FLR(expr) Floor function
@L10(expr) Log base 10
@LOG(expr) Natural logarithm
@MAX(expr,[,...,exprN]) Maximum value
@MIN(expr,[,...,exprN]) Minimum value
ASSEMBLY LANGUAGE

@POW(expr1,expr2) Raise to a power

@RND() Random value
@SGN(expr) Returns the sign of an expression as -1, 0 or 1
@SIN(expr) Sine
@SNH(expr) Hyperbolic sine
@SQT(expr) Square root
@TAN(expr) Tangent
@TNH(expr) Hyperbolic tangent
@XPN(expr) Exponential function (raise e to a power)
 TriCore Assembly Language 3-5

Overview of conversion functions

Function Description
@CVF(expr) Convert integer to floating-point
@CVI(expr) Convert floating-point to integer
@FLD(base,value, Shift and mask operation
width[,start])
@FRACT(expr) Convert floating-point to 32-bit fractional
@SFRACT(expr) Convert floating-point to 16-bit fractional
@LNG(expr) Concatenate to double word
@LUN(expr) Convert long fractional to floating-point
@RVB(expr1[,expr2]) Reverse order of bits in field
@UNF(expr) Convert fractional to floating-point

Overview of string functions

Function Description
@CAT(str1,str2) Concatenate strings
@LEN(string) Length of string
@POS(str1,str2[,start]) Position of substring in string
@SCP(str1,str2) Returns 1 if two strings are equal
@SUB(string,expr,expr) Returns a substring

Overview of macro functions

Function Description
@ARG('symbol'|expr) Test if macro argument is present
@CNT() Return number of macro arguments
@MAC(symbol) Test if macro is defined
@MXP() Test if macro expansion is active

• • • • • • • •
 3-6 TriCore Reference Manual

Overview of address calculation functions

Function Description
@HI(expr) Returns upper 16 bits of expression value
@HIS(expr) Returns upper 16 bits of expression value,
adjusted for signed addition
@LO(expr) Returns lower 16 bits of expression value
@LOS(expr) Returns lower 16 bits of expression value,
adjusted for signed addition
@LSB(expr) Get least significant byte of a word
@MSB(expr) Get most significant byte of a word

Overview of assembler mode functions

Function Description
@ASPCP() Returns the name of the PCP assembler
executable
ASSEMBLY LANGUAGE

@ASTC() Returns the name of the assembler executable

@CPU(string) Test if CPU type is selected
@DEF('symbol'|symbol) Returns 1 if symbol has been defined
@EXP(expr) Expression check
@INT(expr) Integer check
@LST() LIST control flag value

3.2.2 DETAILED DESCRIPTION OF BUILT-IN

ASSEMBLY FUNCTIONS

@ABS(expression)
Returns the absolute value of expression as an integer value.

Example:
AVAL .SET @ABS(-2.1) ; AVAL = 2
 TriCore Assembly Language 3-7

@ACS(expression)
Returns the arc cosine of expression as a floating-point value in the range
zero to pi. The result of expression must be between -1 and 1.

Example:
ACOS .SET @ACS(-1.0) ;ACOS = 3.1415926535897931

@ARG('symbol' | expression)
Returns an integer 1 if the macro argument represented by symbol or
expression is present, 0 otherwise. If the argument is a symbol it must be
single-quoted and refer to a formal argument name. If the argument is an
expression it refers to the ordinal position of the argument in the macro
formal argument list. The assembler issues a warning if this function is
used when no macro expansion is active.

Example:
.IF @ARG('TWIDDLE') ;twiddle factor provided?
.IF @ARG(1) ;is first argument present?

@ASN(expression)
Returns the arc sine of expression as a floating-point value in the range
-pi/2 to pi/2. The result of expression must be between -1 and 1.

Example:
ARCSINE .SET @ASN(-1.0) ;ARCSINE = -1.570796

@ASPCP()
Returns the name of the PCP assembler executable. This is 'aspcp' for the
PCP assembler.

Example:
ANAME: .byte @ASPCP() ; ANAME = 'aspcp'

@ASTC()
Returns the name of the assembler executable. This is 'astc' for the TriCore
assembler.

Example:
ANAME: .byte @ASTC() ; ANAME = 'astc'

• • • • • • • •
 3-8 TriCore Reference Manual

@AT2(expr1,expr2)
Returns the arc tangent of expr1/expr2 as a floating-point value in the
range -pi to pi. Expr1 and expr2 must be separated by a comma.

Example:
ATAN2 .EQU @AT2(-1.0,1.0) ;ATAN2 = -0.7853982

@ATN(expression)
Returns the arc tangent of expression as a floating-point value in the range
-pi/2 to pi/2.

Example:
ATAN .SET @ATN(1.0) ;ATAN = 0.78539816339744828

@CAT(string1,string2)
Concatenates the two strings into one string. The two strings must be
enclosed in single or double quotes.
ASSEMBLY LANGUAGE

Example:
.DEFINE ID "@CAT('Tri','Core')" ;ID = 'TriCore'

@CEL(expression)
Returns a floating-point value which represents the smallest integer greater
than or equal to expression.

Example:
CEIL .SET @CEL(-1.05) ;CEIL = -1.0

@CNT()
Returns the number of arguments of the current macro expansion as an
integer. The assembler issues a warning if this function is used when no
macro expansion is active.

Example:
ARGCNT .SET @CNT() ;reserve argument count
 TriCore Assembly Language 3-9

@COH(expression)
Returns the hyperbolic cosine of expression as a floating-point value.

Example:
HYCOS .EQU @COH(VAL) ;compute hyperbolic cosine

@COS(expression)
Returns the cosine of expression as a floating-point value.

Example:
.WORD -@COS(@CVF(COUNT)*FREQ) ;compute cosine value

@CPU(string)
Returns an integer 1 if string corresponds to the selected CPU type; 0
otherwise. See also the assembler option -C (Select CPU).

Example:
IF @CPU("tc2") ;TriCore 2 specific part

@CVF(expression)
Converts the result of expression to a floating-point value.

Example:
FLOAT .SET @CVF(5) ;FLOAT = 5.0

@CVI(expression)
Converts the result of expression to an integer value. This function should
be used with caution since the conversions can be inexact (e.g.,
floating-point values are truncated).

Example:
INT .SET @CVI(-1.05) ;INT = -1

• • • • • • • •
 3-10 TriCore Reference Manual

@DEF('symbol' | symbol)
Returns an integer 1 if symbol has been defined, 0 otherwise. symbol can
be any symbol or label not associated with a .MACRO or .SDECL directive.
If symbol is quoted it is looked up as a .DEFINE symbol; if it is not
quoted it is looked up as an ordinary symbol or label.

Example:
.IF @DEF('ANGLE') ;is symbol ANGLE defined?
.IF @DEF(ANGLE) ;does label ANGLE exist?

@EXP(expression)
Returns 0 if the evaluation of expression would normally result in an error.
Returns 1 if the expression can be evaluated correctly. With the @EXP
function, you prevent the assembler of generating an error if expression
contains an error. No test is made by the assembler for warnings. The
expression may be relative or absolute.

Example:
ASSEMBLY LANGUAGE

.IF !@EXP(3/0) ;Do the IF on error

;assembler generates no error

.IF !(3/0) ;assembler generates an error

@FLD(base,value,width[,start])
Shift and mask value into base for width bits beginning at bit start. If start
is omitted, zero (least significant bit) is assumed. All arguments must be
positive integers and none may be greater than the target word size.
Returns the shifted and masked value.

Example:
VAR1 .EQU @FLD(0,1,1) ;turn bit 0 on, VAR1=1
VAR2 .EQU @FLD(0,3,1) ;turn bit 0 on, VAR2=1
VAR3 .EQU @FLD(0,3,2) ;turn bits 0 and 1 on, VAR3=3
VAR4 .EQU @FLD(0,3,2,1) ;turn bits 1 and 2 on, VAR4=6
VAR5 .EQU @FLD(0,1,1,7) ;turn eighth bit on, VAR5=0x80
 TriCore Assembly Language 3-11

@FLR(expression)
Returns a floating-point value which represents the largest integer less
than or equal to expression.

Example:
FLOOR .SET @FLR(2.5) ;FLOOR = 2.0

@FRACT(expression)
This function returns the 32-bit fractional representation of the
floating-point expression. The expression must be in the range [-1,+1>.

Example:
.WORD @FRACT(0.1), @FRACT(1.0)

@HI(expression)
Returns the upper 16 bits of a value. @HI(expression) is equivalent to
((expression>>16) & 0xffff).

Example:
mov.u d2,#@LO(COUNT)
addih d2,d2,#@HI(COUNT) ; upper 16 bits of COUNT

@HIS(expression)
Returns the upper 16 bits of a value, adjusted for a signed addition.
@HIS(expression) is equivalent to (((expression+0x800)>>16) &
0xffff).

Example:
movh.a a3,#@HIS(label)
lea a3,[a3]@LOS(label)

@INT(expression)
Returns an integer 1 if expression has an integer result; otherwise, it
returns a 0. The expression may be relative or absolute.

Example:
.IF @INT(TERM) ;Test if result is an integer

• • • • • • • •
 3-12 TriCore Reference Manual

@L10(expression)
Returns the base 10 logarithm of expression as a floating-point value.
expression must be greater than zero.

Example:
LOG .EQU @L10(100.0) ;LOG = 2

@LEN(string)
Returns the length of string as an integer.

Example:
SLEN .SET @LEN('string') ;SLEN = 6

@LNG(expr1,expr2)
Concatenates the 16-bit expr1 and expr2 into a 32-bit word value such
that expr1 is the high half and expr2 is the low half.

Example:
ASSEMBLY LANGUAGE

LWORD .WORD @LNG(HI,LO) ;build long word

@LO(expression)
Returns the lower 16 bits of a value. @LO(expression) is equivalent to
expression & 0xffff).

Example:
mov.u d2,#@LO(COUNT) ;lower 16 bits of COUNT
addih d2,d2,#@HI(COUNT)

@LOG(expression)
Returns the natural logarithm of expression as a floating-point value.
expression must be greater than zero.

Example:
LOG .EQU @LOG(100.0) ;LOG = 4.605170
 TriCore Assembly Language 3-13

@LOS(expression)
Returns the lower 16 bits of a value, adjusted for a signed addition.
@LOS(expression) is equivalent to (((expression+0x8000) &
0xffff) - 0x8000).

Example:
movh.a a3,#@HIS(label)
lea a3,[a3]@LOS(label)

@LSB(expression)
Returns the least significant byte of the result of the expression.
expression is interpreted as a half word (16 bit).

Example:
VAR1 .SET @LSB(0x34) ;VAR1 = 0x34
VAR2 .SET @LSB(0x1234) ;VAR2 = 0x34
VAR3 .SET @LSB(0x654321) ;VAR3 = 0x21

@LST()
Returns the value of the $LIST ON/OFF control flag as an integer.
Whenever a $LIST ON control is encountered in the assembler source, the
flag is incremented; when a $LIST OFF control is encountered, the flag is
decremented.

Example:
.DUP @ABS(@LST()) ;list unconditionally

@LUN(expression)
Converts the 32-bit expression to a floating-point value. expression should
represent a binary fraction.

Example:
DBLFRC1 .EQU @LUN(0x40000000) ;DBLFRC1 = 0.5
DBLFRC2 .EQU @LUN(3928472) ;DBLFRC2 = 0.007354736
DBLFRC3 .EQU @LUN(0xE0000000) ;DBLFRC3 = -0.75

• • • • • • • •
 3-14 TriCore Reference Manual

@MAC(symbol)
Returns an integer 1 if symbol has been defined as a macro name, 0
otherwise.

Example:
.IF @MAC(DOMUL) ;does macro DOMUL exist?

@MAX(expr1[,exprN]...)
Returns the greatest of expr1,...,exprN as a floating-point value.

Example:
MAX: .BYTE @MAX(1,-2.137,3.5) ;MAX = 3.5

@MIN(expr1[,exprN]...)
Returns the least of expr1,...,exprN as a floating-point value.

Example:
ASSEMBLY LANGUAGE

MIN: .BYTE @MIN(1,-2.137,3.5) ;MIN = -2.137

@MSB(expression)
Returns the most significant byte of the result of the expression.
expression is interpreted as a half word (16 bit).

Example:
VAR1 .SET @MSB(0x34) ;VAR1 = 0x00
VAR2 .SET @MSB(0x1234) ;VAR2 = 0x12
VAR3 .SET @MSB(0x654321) ;VAR3 = 0x43

@MXP()
Returns an integer 1 if the assembler is expanding a macro, 0 otherwise.

Example:
.IF @MXP() ;macro expansion active?
 TriCore Assembly Language 3-15

@POS(str1,str2[,start])
Returns the position of str2 in str1 as an integer, starting at position start. If
start is not given the search begins at the beginning of str1. If the start
argument is specified it must be a positive integer and cannot exceed the
length of the source string. Note that the first position in a string is
position 0.

Example:
ID .EQU @POS('TriCore','Core') ;ID = 3
ID2 .EQU @POS('ABCDABCD','B',2) ;ID2 = 5

@POW(expr1,expr2)
Returns expr1 raised to the power expr2 as a floating-point value. expr1
and expr2 must be separated by a comma.

Example:
BUF .EQU @CVI(@POW(2.0,3.0)) ;BUF = 8

@RND()
Returns a random value in the range 0.0 to 1.0.

Example:
SEED .EQU @RND() ;save initial SEED value

@RVB(expr1,expr2)
Reverse the order of bits in expr1 delimited by the number of bits in
expr2. If expr2 is omitted the field is bounded by the target word size.
Both expressions must be 16-bit integer values.

Example:
VAR1 .SET @RVB(0x200) ;reverse all bits, VAR1=0x40
VAR2 .SET @RVB(0xB02) ;reverse all bits, VAR2=0x40D0
VAR3 .SET @RVB(0xB02,2) ;reverse bits 0 and 1,
;VAR3=0xB01

• • • • • • • •
 3-16 TriCore Reference Manual

@SCP(str1,str2)
Returns an integer 1 if the two strings compare, 0 otherwise. The two
strings must be separated by a comma.

Example:
.IF @SCP(STR,'MAIN') ;does STR equal MAIN?

@SFRACT(expression)
This function returns the 16-bit fractional representation of the
floating-point expression. The expression must be in the range [-1,+1>.

Example:
.WORD @SFRACT(0.1), @SFRACT(1.0)

@SGN(expression)
Returns the sign of expression as an integer: -1 if the argument is negative,
0 if zero, 1 if positive. The expression may be relative or absolute.
ASSEMBLY LANGUAGE

Example:
VAR1 .SET @SGN(-1.2e-92) ;VAR1 = -1
VAR2 .SET @SGN(0) ;VAR2 = 0
VAR3 .SET @SGN(28.382) ;VAR3 = 1

@SIN(expression)
Returns the sine of expression as a floating-point value.

Example:
.WORD @SIN(@CVF(COUNT)*FREQ) ;compute sine value

@SNH(expression)
Returns the hyperbolic sine of expression as a floating-point value.

Example:
HSINE .EQU @SNH(VAL) ;hyperbolic sine
 TriCore Assembly Language 3-17

@SQT(expression)
Returns the square root of expression as a floating-point value. expression
must be positive.

Example:
SQRT1 .EQU @SQT(3.5) ;SQRT1 = 1.870829
SQRT2 .EQU @SQT(16) ;SQRT2 = 4

@SUB(string,expression1,expression2)
Returns the substring from string as a string. Expression1 is the starting
position within string, and expression2 is the length of the desired string.
The assembler issues an error if either expression1 or expression2 exceeds
the length of string. Note that the first position in a string is position 0.

Example:
.DEFINE ID "@SUB('TriCore',3,4)" ;ID = 'Core'

@TAN(expression)
Returns the tangent of expression as a floating-point value.

Example:
TANGENT .SET @TAN(1.0) ;TANGENT = 1.5574077

@TNH(expression)
Returns the hyperbolic tangent of expression as a floating-point value.

Example:
HTAN .SET @TNH(1) ;HTAN = 0.76159415595

@UNF(expression)
Converts expression to a floating-point value. expression should represent
a 16-bit binary fraction.

Example:
FRC .EQU @UNF(0x4000) ;FRC = 0.5

• • • • • • • •
 3-18 TriCore Reference Manual

@XPN(expression)
Returns the exponential function (base e raised to the power of
expression) as a floating-point value.

Example:
EXP .EQU @XPN(1.0) ;EXP = 2.718282
ASSEMBLY LANGUAGE
 TriCore Assembly Language 3-19

3.3 ASSEMBLER DIRECTIVES AND CONTROLS

3.3.1 OVERVIEW OF ASSEMBLER DIRECTIVES

Assembler directives are grouped in the following categories:
• Assembly control directives
• Symbol definition directives
• Data definition / Storage allocation directives
• Macro and conditional assembly directives
• Debug directives
The following tables provide an overview of all assembler directives.

Overview of assembly control directives

Directive Description
.COMMENT Start comment lines
.DEFINE Define substitution string
.END End of source program
.FAIL Programmer generated error message
.INCLUDE Include file
.MESSAGE Programmer generated message
.ORG Initialize memory space and location counters to
create a nameless section
.SDECL Declare a section with name, type and attributes
.SECT Activate a declared section
.UNDEF Undefine DEFINE symbol
.WARNING Programmer generated warning

• • • • • • • •
 3-20 TriCore Reference Manual

Overview of symbol definition directives

Directive Description
.EQU Assign permanent value to a symbol
.EXTERN External symbol declaration
.GLOBAL Global section symbol declaration
.LOCAL Local symbol declaration
.SET Set temporary value to a symbol
.SIZE Set size of symbol in the ELF symbol table
.TYPE Set symbol type in the ELF symbol table
.WEAK Mark symbol as 'weak'

Overview of data definition / storage allocation directives

Directive Description
.ACCUM Define 64-bit constant of 18 + 46 bits format
ASSEMBLY LANGUAGE

.ALIGN Define alignment

.ASCII / .ASCIIZ Define ASCII string without / with ending NULL byte
.BYTE Define constant byte
.FLOAT / .DOUBLE Define a 32-bit / 64-bit floating-point constant
.FRACT / .SFRACT Define a 16-bit / 32-bit constant fraction
.SPACE Define storage
.WORD / .HALF Define a word / half-word constant
 TriCore Assembly Language 3-21

Overview of macro and conditional assembly directives

Directive Description
.DUP / .ENDM Duplicate sequence of source lines
.DUPA / .ENDM Duplicate sequence with arguments
.DUPC / .ENDM Duplicate sequence with characters
.DUPF / .ENDM Duplicate sequence in loop
.EXITM Exit macro
.IF / .ELIF / .ELSE / Conditional assembly
.ENDIF
.MACRO / .ENDM Define macro
.PMACRO Undefine (purge) macro definition

Overview of debug directives

Function Description
.CALLS Passes call information to object file. Used by the
linker to build a call graph and calculate stack size.

3.3.2 DETAILED DESCRIPTION OF ASSEMBLER

DIRECTIVES
Some assembler directives can be preceeded with a label. If you do not
preceede an assembler directive with a label, you must use white space
instead (spaces or tabs). The assembler recognizes both upper and lower
case for directives.

• • • • • • • •
 3-22 TriCore Reference Manual

.ACCUM
Syntax
[label:] .ACCUM expression[,expression]...

Description
With the .ACCUM directive (Define 64-bit Constant) the assembler allocates
and initializes two words of memory (64 bits) for each argument. Use
commas to separate multiple arguments.

An expression can be:

• a fractional fixed point expression (range [-217, 217>)
• NULL (indicated by two adjacent commas: ,,)
Multiple arguments are stored in successive address locations in sets of
two bytes. If an argument is NULL its corresponding address location is
filled with zeros.

If the evaluated expression is out of the range [-217, 217>, the assembler
ASSEMBLY LANGUAGE

issues a warning and saturates the fractional value.

Example
ACC: .ACCUM 0.1,0.2,0.3

Related information
.SPACE (Define storage)

.FRACT / .SFRACT (Define 32-bit / 16-bit constant fraction)

 TriCore Assembly Language 3-23

.ALIGN
Syntax
.ALIGN expression

Description
With the .ALIGN directive you instruct the assembler to align the location
counter. By default the assembler aligns on one byte.

When the assembler encounters the .ALIGN directive, it advances the

location counter to an address that is aligned as specified by expression
and places the next instruction or directive on that address. The alignment
is in minimal addressable units (MAUs). The assembler fills the 'gap' with
NOP instructions for code sections or with zeros for data sections. If the
location counter is already aligned on the specified alignment, it remains
unchanged. The location of absolute sections will not be changed.

The expression must be a power of two: 2, 4, 8, 16, ... If you specify

another value, the assembler changes the alignment to the next higher
power of two and issues a warning.

The assembler aligns sections automatically to the largest alignment value

occurring in that secton.

A label is not allowed before this directive.

Example
.ALIGN 16 ; the assembler aligns
add d2,d2,d4 ; this instruction at 16 bytes and
; fills the 'gap' with NOP instructions

.ALIGN 12 ; WRONG: not a power of two, the

add d2,d2,d4 ; assembler aligns this instruction at
; 16 bytes and issues a warning

Related information
-

• • • • • • • •
 3-24 TriCore Reference Manual

.ASCII/.ASCIIZ
Syntax
[label:] .ASCII string[,string]...

[label:] .ASCIIZ string[,string]...

Description
With the .ASCII or .ASCIIZ directive the assembler allocates and
initializes memory for each string argument.

The .ASCII directive does not add a NULL byte to the end of the string.
The .ASCIIZ directive does add a NULL byte to the end of the string. The
"z" in .ASCIIZ stands for "zero". Use commas to separate multiple strings.

Example
STRING: .ASCII "Hello world"

STRINGZ: .ASCIIZ "Hello world"

ASSEMBLY LANGUAGE

With the .BYTE directive you can obain exactly the same effect:
STRING: .BYTE "Hello world" ; without a NULL byte
STRINGZ: .BYTE "Hello world",0 ; with a NULL byte

Related information
.SPACE (Define storage)

.BYTE (Define a constant byte)

.WORD / .HALF (Define a word / halfword)
 TriCore Assembly Language 3-25

.BYTE
Syntax
[label] .BYTE argument[,argument]...

Description
With the .BYTE directive (Define Constant Byte) the assembler allocates
and initializes a byte of memory for each argument.

An argument can be:

• a single or multiple character string constant
• an integer expression
• NULL (indicated by two adjacent commas: ,,)
Multiple arguments are stored in successive byte locations. If an argument
is NULL its corresponding byte location is filled with zeros.

If you specify label, it gets the value of the location counter at the start of
the directive processing.

Integer arguments are stored as is, but must be byte values (within the
range 0-255); floating-point numbers are not allowed. If the evaluated
expression is out of the range [-256, +255] the assembler issues an error.
For negative values within that range, the assembler adds 256 to the
specified value (for example, -254 is stored as 2).

In case of single and multiple character strings, each character is stored in

consecutive bytes whose lower seven bits represent the ASCII value of the
character. The standard C escape sequences are allowed:
.BYTE 'R' ; = 0x52
.BYTE 'AB',,'D' ; = 0x41420043

Example
TABLE .BYTE 'two',0,'strings',0
CHARS .BYTE 'A','B','C','D'

Related information
.SPACE (Define storage)

.ASCII / .ASCIIZ (Define ASCII string without/with ending NULL)

.WORD / .HALF (Define a word / halfword)

• • • • • • • •
 3-26 TriCore Reference Manual

.CALLS
Syntax
.CALLS 'caller', 'callee' [,call_frequency [,stack_usage]...]

Description
Create a flow graph reference between caller and callee. With this
information the linker can build a call graph and calculate stack size.
Caller and Callee are names of functions. The call_frequency shows how
many times the callee is called. The stack_usage represents the stack usage
in bytes at the location of the call or the maximum stack usage of function
caller. A function can use multiple stacks.

The compiler inserts .CALLS directives automatically to pass call tree

information. Normally it is not necessary to use the .CALLS directive in
hand coded assembly.

A label is not allowed before this directive.

ASSEMBLY LANGUAGE

Example
.CALLS 'main', 'nfunc', 1, 8

Indicates that the function main calls the function nfunc 1 time and that
the stack usage at the location of the call is 8 bytes.
.CALLS 'main', '', 0, 8

Specifies the maximum stack usage of function main (8 bytes).

Related information
-
 TriCore Assembly Language 3-27

.COMMENT
Syntax
.COMMENT delimiter
.
.
delimiter

Description
With the .COMMENT directive (Start Comment Lines) you can define one or
more lines as comments. The first non-blank character after the .COMMENT
directive is the comment delimiter. The two delimiters are used to define
the comment text. The line containing the second comment delimiter will
be considered the last line of the comment. The comment text can include
any printable characters and the comment text will be produced in the
source listing as it appears in the source file.

A label is not allowed before this directive.

Example
.COMMENT + This is a one line comment +
.COMMENT * This is a multiple line
comment. Any number of lines
can be placed between the two
delimiters.
*

Related information
-

• • • • • • • •
 3-28 TriCore Reference Manual

.DEFINE
Syntax
.DEFINE symbol string

Description
With the .DEFINE directive you define a substitution string that you can
use on all following source lines. The assembler searches all succeeding
lines for an occurrence of symbol, and replaces it with string. If the symbol
occurs in a double quoted string it is also replaced. Strings between single
quotes are not expanded.

This directive is useful for providing better documentation in the source

program. A symbol can consist of letters, digits and underscore characters
(_), and the first character cannot be a digit.

The assembler issues a warning if you redefine an existing symbol.

Macros represent a special case. .DEFINE directive translations are applied

ASSEMBLY LANGUAGE

to the macro definition as it is encountered. When the macro is expanded

any active .DEFINE directive translations will again be applied.

A label is not allowed before this directive.

Example
If the following .DEFINE directive occurred in the first part of the source
program:
.DEFINE LEN '32'

then the source line below:

.SPACE LEN
MSG "The length is: LEN"

would be transformed by the assembler to the following:

.SPACE 32
MSG "The length is: 32"

Related information
.UNDEF (Undefine .DEFINE symbol)
.SET (Set temporary value to a symbol)
 TriCore Assembly Language 3-29

.DUP / .ENDM
Syntax
[label] .DUP expression
.
.
.ENDM

Description
The sequence of source lines between the .DUP and .ENDM directives will
be duplicated by the number specified by the integer expression. If the
expression evaluates to a number less than or equal to 0, the sequence of
lines will not be included in the assembler output. The expression result
must be an absolute integer and cannot contain any forward references to
address labels (labels that have not already been defined). You can nest
the .DUP directive to any level.

If you specify label, it gets the value of the location counter at the start of
the DUP directive processing.

Example
Consider the following source input statements,
COUNT .SET 3
.DUP COUNT ; duplicate NOP count times
NOP
.ENDM

This is expanded as follows:

COUNT .SET 3
NOP
NOP
NOP

Related information
.DUPA (Duplicate Sequence with Arguments),
.DUPC (Duplicate Sequence with Characters),
.DUPF (Duplicate Sequence in Loop),
.MACRO (Define Macro)

• • • • • • • •
 3-30 TriCore Reference Manual

.DUPA / .ENDM
Syntax
[label] .DUPA formal_arg,argument[,argument]...
.
.
.ENDM

Description
With the .DUPA and .ENDM directives (Duplicate Sequence with
Arguments) you can repeat a block of source statements for each
argument. For each repetition, every occurrence of the formal_arg
parameter within the block is replaced with each succeeding argument
string. If an argument includes an embedded blank or other
assembler-significant character, it must be enclosed with single quotes.

If you specify label, it gets the value of the location counter at the start of
the .DUPA directive processing.
ASSEMBLY LANGUAGE

Example
Consider the following source input statements,
.DUPA VALUE,12,,32,34
.BYTE VALUE
.ENDM

This is expanded as follows:

.BYTE 12
.BYTE VALUE ; results in a warning
.BYTE 32
.BYTE 34

The second statement results in a warning of the assembler that the local
symbol VALUE is not defined in this module and is made external.

Related information
.DUP (Duplicate Sequence of Source Lines),
.DUPC (Duplicate Sequence with Characters),
.DUPF (Duplicate Sequence in Loop),
.MACRO (Define Macro)
 TriCore Assembly Language 3-31

.DUPC / .ENDM
Syntax
[label] .DUPC formal_arg,string
.
.
.ENDM

Description
With the .DUPC and .ENDM directives (Duplicate Sequence with
Characters) you can repeat a block of source statements for each character
within string. For each character in the string, the formal_arg parameter
within the block is replaced with that character If the string is empty, then
the block is skipped.

If you specify label, it gets the value of the location counter at the start of
the .DUPC directive processing.

Example
Consider the following source input statements,
.DUPC VALUE,'123'
.BYTE VALUE
.ENDM

This is expanded as follows:

.BYTE 1
.BYTE 2
.BYTE 3

Related information
.DUP (Duplicate Sequence of Source Lines),
.DUPA (Duplicate Sequence with Arguments),
.DUPF (Duplicate Sequence in Loop),
.MACRO (Define Macro)

• • • • • • • •
 3-32 TriCore Reference Manual

.DUPF / .ENDM
Syntax
[label] .DUPF formal_arg,[start],end[,increment]
.
.
.ENDM

Description
With the .DUPF and .ENDM directives (Duplicate Sequence in Loop) you
can repeat a block of source statements (end - start) + 1 / increment
times. Start is the starting value for the loop index; end represents the final
value. Increment is the increment for the loop index; it defaults to 1 if
omitted (as does the start value). The formal_arg parameter holds the
loop index value and may be used within the body of instructions.

If you specify label, it gets the value of the location counter at the start of
the .DUPF directive processing.
ASSEMBLY LANGUAGE

Example
Consider the following source input statements,
.DUPF NUM,0,7
MOV D\NUM,#0
.ENDM

This is expanded as follows:

MOV D0,#0
MOV D1,#0
MOV D2,#0
MOV D3,#0
MOV D4,#0
MOV D5,#0
MOV D6,#0
MOV D7,#0

Related information
.DUP (Duplicate Sequence of Source Lines),
.DUPA (Duplicate Sequence with Arguments),
.DUPC (Duplicate Sequence with Characters),
.MACRO (Define Macro)
 TriCore Assembly Language 3-33

.END
Syntax
.END [expression]

Description
With the optional .END directive you tell the assembler that the logical end
of the source program is reached. If the assembler finds assembly source
lines beyond the .END directive, it ignores those lines and issues a
warning.

The expression is only permitted here for compatibility reasons. It is

ignored during assembly.

You cannot use the .END directive in a macro expansion.

A label is not allowed before this directive.

Example
.END ;End of source program

Related information
-

• • • • • • • •
 3-34 TriCore Reference Manual

.EQU
Syntax
symbol .EQU expression

Description
With the .EQU directive you assign the value of expression to symbol
permanently. Once defined, you cannot redefine the symbol.

The expression can be relocatable or absolute and forward references are

allowed.

Example
To assign the value 0x4000 permanently to the symbol A_D_PORT :
A_D_PORT .EQU 0x4000

You cannot redefine the symbol A_D_PORT after this.

ASSEMBLY LANGUAGE

Related information
.SET (Set temporary value to a symbol)
 TriCore Assembly Language 3-35

.EXITM
Syntax
.EXITM

Description
With the .EXITM directive (Exit Macro) the assembler will immediately
terminate a macro expansion. It is useful when you use it with the
conditional assembly directive .IF to terminate macro expansion when,
for example, error conditions are detected.

A label is not allowed before this directive.

Example
CALC .MACRO XVAL,YVAL
.IF XVAL<0
.FAIL 'Macro parameter value out of range'
.EXITM ;Exit macro
.ENDIF
.
.
.
.ENDM

Related information
.DUP (Duplicate Sequence of Source Lines),
.DUPA (Duplicate Sequence with Arguments),
.DUPC (Duplicate Sequence with Characters),
.DUPF (Duplicate Sequence in Loop),
.MACRO (Define Macro)

• • • • • • • •
 3-36 TriCore Reference Manual

.EXTERN
Syntax
.EXTERN symbol[,symbol]...

Description
With the .EXTERN directive (External Symbol Declaration) you specify that
the list of symbols is referenced in the current module, but is not defined
within the current module. These symbols must either have been defined
outside of any module or declared as globally accessible within another
module with the .GLOBAL directive.

If you do not use the .EXTERN directive to specify that a symbol is

defined externally and the symbol is not defined within the current
module, the assembler issues a warning and inserts the .EXTERN directive
for that symbol.

A label is not allowed before this directive.

ASSEMBLY LANGUAGE

Example
.EXTERN AA,CC,DD ;defined elsewhere

Related information
.GLOBAL (Global symbol declaration)
.LOCAL (Local symbol declaration)
 TriCore Assembly Language 3-37

.FAIL
Syntax
.FAIL [{string | exp}[,{string | exp}]...]

Description
With the .FAIL directive (Programmer Generated Error) you tell the
assembler to output an error message during the assembling process.

The total error count will be incremented as with any other error. The
.FAIL directive is for example useful in combination with conditional
assembly for exceptional condition checking. The assembly process
proceeds normally after the error has been printed.

Optionally, you can specify an arbitrary number of strings and expressions,

in any order but separated by commas, to describe the nature of the
generated error. If you use expressions, the assembler outputs the result.
The assembler outputs a space between each argument.

With this directive the assembler exits with exit code 1 (an error).

A label is not allowed before this directive.

Example
.FAIL 'Parameter out of range'

This results in the error:

E143: ["filename" line] Parameter out of range

Related information
.MESSAGE (Programmer Generated Message),
.WARNING (Programmer Generated Warning)

• • • • • • • •
 3-38 TriCore Reference Manual

.FLOAT/.DOUBLE
Syntax
[label] .FLOAT expression[,expression]...

[label] .DOUBLE expression[,expression]...

Description
With the .FLOAT or .DOUBLE directive the assembler allocates and
initializes a floating-point number (32 bits) or a double (64 bits) in
memory for each argument.

An expression can be:

• a floating-point expression
• NULL (indicated by two adjacent commas: ,,)
You can represent a constant as a signed whole number with fraction or
with the 'e' format as used in the C language. 12.457 and +0.27E-13 are
legal floating-point constants.
ASSEMBLY LANGUAGE

If you specify label, it gets the value of the location counter at the start of
the directive processing.

If the evaluated argument is too large to be represented in a single word /

double-word, the assembler issues an error and truncates the value.

Examples
FLT: .FLOAT 12.457,+0.27E-13

DBL: .DOUBLE 12.457,+0.27E-13

Related information
.SPACE (Define storage)
 TriCore Assembly Language 3-39

.FRACT/.SFRACT
Syntax
[label:] .FRACT expression[,expression]...

[label:] .SFRACT expression[,expression]...

Description
With the .FRACT or .SFRACT directive the assembler allocates and
initializes one word of memory (32 bits) or a halfword (16 bits) for each
argument. Use commas to separate multiple arguments.

An expression can be:

• a fractional fixed point expression (range [-1, +1>)
• NULL (indicated by two adjacent commas: ,,)
Multiple arguments are stored in successive address locations in sets of
two bytes. If an argument is NULL its corresponding address location is
filled with zeros.

If the evaluated argument is out of the range [-1, +1> , the assembler
issues a warning and saturates the fractional value.

Example
FRCT: .FRACT 0.1,0.2,0.3

SFRCT: .SFRACT 0.1,0.2,0.3

Related information
.SPACE (Define storage)

.ACCUM (Define 64-bit constant fraction in 18+46 bits format )

• • • • • • • •
 3-40 TriCore Reference Manual

.GLOBAL
Syntax
.GLOBAL symbol[,symbol]...

Description
All symbols or labels defined in the current section or module are local to
the module by default. You can change this default behavior with
assembler option -ig.

With the .GLOBAL directive (Global Section Symbol Declaration) you

declare one of more symbols as global. This means that the specified
symbols are defined within the current section or module, and that those
definitions should be accessible by all modules, using the EXTERN
directive.

Only symbols that are defined with the .EQU directive or program labels
can be made global.
ASSEMBLY LANGUAGE

If the symbols that appear in the operand field are not used in the module,
the assembler gives a warning.

A label is not allowed before this directive.

Example
.SDECL ".data.io",DATA
.SECT ".data.io"
.GLOBAL LOOPA ; LOOPA will be globally
; accessible by other modules
LOOPA .HALF 0x100 ; assigns the value 0x100 to LOOPA

Related information
.EXTERN (External symbol declaration)
.LOCAL (Local symbol declaration)
 TriCore Assembly Language 3-41

.IF / .ELIF / .ELSE / .ENDIF

Syntax
.IF expression
.
.
[.ELIF expression] (the .ELIF directive is optional)
.
.
[.ELSE] (the .ELSE directive is optional)
.
.
.ENDIF

Description
With the .IF/ .ENDIF directives you can create a part of conditional
assembly code. The assembler assembles only the code that matches a
specified condition.

The expression must evaluate to an absolute integer and cannot contain

forward references. If expression evaluates to zero, the .IF-condition is
considered FALSE. Any non-zero result of expression is considered as
TRUE.

You can nest .IF directives to any level. The .ELSE, .ELIF and .ENDIF
directives always refer to the nearest previous .IF directive.

A label is not allowed before this directive.

Example
Suppose you have an assemble source file with specific code for a test
version, for a demo version and for the final version. Within the assembly
source you define this code conditionally as follows:
.IF TEST
... ; code for the test version
.ELIF DEMO
... ; code for the demo version
.ELSE
... ; code for the final version
.ENDIF

• • • • • • • •
 3-42 TriCore Reference Manual

Before assembling the file you can set the values of the symbols .TEST
and .DEMO in the assembly source before the .IF directive is reached. For
example, to assemble the demo version:
TEST .SET 0
DEMO .SET 1

You can also define the symbols on the command line with the option -D:
astc -DDEMO -DTEST=0 test.src

Related information
-
ASSEMBLY LANGUAGE
 TriCore Assembly Language 3-43

.INCLUDE
Syntax
.INCLUDE 'filename' | <filename>

Description
With the .INCLUDE directive you include another file at the exact location
in the source where the .INCLUDE occurs. The .INCLUDE directive works
similarly to the #include statement in C. The source from the include file
is assembled as if it followed the point of the .INCLUDE directive. When
the end of the included file is reached, assembly of the original file
continues.

The filename specifies the filename of the file to be included. The

filename must be compatible with the operating system
(forward/backward slashes) and can include a directory specification.

If an absolute pathname is specified, the assembler searches for that file. If

a relative path is specified or just a filename, the order in which the
assembler searches for include files is:

1. The current directory if you used the 'filename' construction.

The current directory is not searched if you use the <filename> syntax.

2. The path that is specified with the assembler option -I.

3. The path that is specified in the environment variable ASTCINC when

the product was installed.

4. The include directory relative to the installation directory.

A label is not allowed before this directive.

Example
.INCLUDE 'storage\mem.asm' ; include file
.INCLUDE <data.asm> ; Do not look in
; current directory

Related information
Assembler option -I (Add directory to include file search path) in section
5.2, Assembler Options, of Chapter Tool Options.

• • • • • • • •
 3-44 TriCore Reference Manual

.LOCAL
Syntax
.LOCAL symbol[,symbol]...

Description
All symbols or labels defined in the current section or module are local to
the module by default. You can change this default behavior with
assembler option -ig.

With the .LOCAL directive (Local Section Symbol Declaration) you declare
one of more symbols as local. This means that the specified symbols are
explicitly local to the module in which you define them.

If the symbols that appear in the operand field are not used in the module,
the assembler gives a warning.

A label is not allowed before this directive.

ASSEMBLY LANGUAGE

Example
.SDECL ".data.io",DATA
.SECT ".data.io"
.LOCAL LOOPA ; LOOPA is local to this section

LOOPA .HALF 0x100 ; assigns the value 0x100 to LOOPA

Related information
.EXTERN (External symbol declaration)
.GLOBAL (Global symbol declaration)
 TriCore Assembly Language 3-45

.MACRO / .ENDM
Syntax
macro_name .MACRO [dumarg[,dumarg]...]
.
macro_definition_statements
.
.
.ENDM

Description
With the .MACRO directive you define a macro. Macros provide a
shorthand method for handling a repeated pattern of code or group of
instructions. You can define the pattern as a macro, and then call the
macro at the points in the program where the pattern would repeat. The
.ENDM directive indicates the end of the macro.

The definition of a macro consists of three parts:

• Header, which assigns a name to the macro and defines the arguments.
• Body, which contains the code or instructions to be inserted when the
macro is called.
• Terminator, which indicates the end of the macro definition (ENDM
directive).
The arguments are symbolic names that the macro preprocessor replaces
with the literal arguments when the macro is expanded (called). Each
formal argument must follow the same rules as symbol names: the name
can consist of letters, digits and underscore characters (_). The first
character cannot be a digit. Argument names cannot start with a percent
sign (%).

Macro definitions can be nested but the nested macro will not be defined
until the primary macro is expanded.

You can use the following operators in macro definition statements:

• • • • • • • •
 3-46 TriCore Reference Manual

Operator Name Description

\ Macro argument Concatenates a macro argument with
concatenation adjacent alphanumeric characters.
? Return decimal Substitutes the ?symbol sequence with a
value of symbol character string that represents the decimal
value of the symbol.
% Return hex Substitutes the %symbol sequence with a
value of symbol character string that represents the
hexadecimal value of the symbol.
" Macro string Allows the use of macro arguments as literal
delimiter strings.
^ Macro local label Causes local labels in its term to be evaluated
override at normal scope rather than at macro scope.

Example
The macro definition:
CONSTD .MACRO reg,value ;header
mov.u reg,#lo(value) ;body
ASSEMBLY LANGUAGE

addih reg,reg,#hi(value)
.ENDM ;terminator

The macro call:

.SDECL ".text",code
.SECT ".text"
CONSTD d4,0x12345678

The macro expands as follows:

mov.u d4,#lo(0x12345678)
addih d4,d4,#hi(0x12345678)

Related information
.DUP (Duplicate Sequence of Source Lines),
.DUPA (Duplicate Sequence with Arguments),
.DUPC (Duplicate Sequence with Characters),
.DUPF (Duplicate Sequence in Loop)

Section 4.10, Macro Operations, in Chapter Assembly Language of the

User's Manual.
 TriCore Assembly Language 3-47

.MESSAGE
Syntax
.MESSAGE [{string | exp}[,{string | exp}]...]

Description
With the .MESSAGE directive (Programmer Generated Message) you tell
the assembler to output an information message durring assembly.

The error and warning counts will not be affected. The .MESSAGE
directive is for example useful in combination with conditional assembly
for informational purposes. The assembly proceeds normally after the
message has been printed.

Optionally, you can specify an arbitrary number of strings and expressions,

in any order but separated by commas, to describe the nature of the
message. If you use expressions, the assembler outputs the result. The
assembler outputs a space between each argument.

This directive has no effect on the exit code of the assembler.

A label is not allowed before this directive.

Example
.DEFINE LONG "SHORT"
.MESSAGE 'This is a LONG string'
.MESSAGE "This is a LONG string"

Within single quotes, the defined symbol LONG is not expanded. Within
double quotes the symbol LONG is expanded. So, the actual message is
printed as:
This is a LONG string
This is a SHORT string

Related information
.FAIL (Programmer Generated Error)
.WARNING (Programmer Generated Warning)

• • • • • • • •
 3-48 TriCore Reference Manual

.ORG
Syntax
.ORG [abs-loc][,sect_type][,attribute]...

Description
With the .ORG directive you can specify an absolute location (abs_loc) in
memory of a section. This is the same as a .SDECL/.SECT without a
section name.

This directive uses the following arguments:

abs-loc Initial value to assign to the run-time location counter.

abs-loc must be an absolute expression. If abs_loc is not
specified, then the value is zero.

sect_type An optional section type:

code code section

ASSEMBLY LANGUAGE

data data section

attribute An optional section attribute:

Code attibutes:
init section is copied from ROM to RAM at startup
noread section can be executed from but not read

Data attibutes:
noclear section is not cleared during startup
max data overlay with other parts with the same
name, is implicit a type of 'noclear'
rom data section remains in ROM

A label is not allowed before this directive.

Example
; define a section on location 100 decimal
.org 100

; define a relocatable nameless section

.org

; define a relocatable data section

.org ,data
 TriCore Assembly Language 3-49

; define a data section on 0x8000

.org 0x8000,data

Related information
.SDECL (Declare section name and attributes)
.SECT (Activate a declared section)

• • • • • • • •
 3-50 TriCore Reference Manual

.PMACRO
Syntax
.PMACRO symbol[,symbol]...

Description
With the .PMACRO directive (Purge Macro) you tell the assembler to
undefine the specified macro, so that later uses of the symbol will not be
expanded.

A label is not allowed before this directive.

Example
.PMACRO MAC1,MAC2

This statement causes the macros named MAC1 and MAC2 to be undefined.

Related information
ASSEMBLY LANGUAGE

.MACRO (Define Macro)

 TriCore Assembly Language 3-51

.SDECL
Syntax
.SDECL "name", type [, attribute ]... [AT address]

Description
With the .SDECL directive you can define a section with a name, type and
optional attributes. Before any code or data can be placed in a section,
you must use the .SECT directive to activate the section.

This directive uses the following arguments:

type: A section type:

code code section

data data section

attribute: An optional section attribute:

Code attibutes:
init section is copied from ROM to RAM at startup
noread section can be executed from but not read

Data attibutes:
noclear section is not cleared during startup
max data overlay with other parts with the same
name, is implicit a type of 'noclear'
rom data section remains in ROM

Sections with attribute noclear are not zeroed at startup. This is a default
attribute for data sections. You can only use this attribute with a data
type section. This attribute is only useful with BSS sections, which are
cleared at startup by default.

The attribute init defines that the code section contains initialization
data, which is copied from ROM to RAM at program startup.

Sections with the attribute rom contain data to be placed in ROM. This
ROM area is not executable.

When data sections with the same name occur in different object
modules with the attribute max, the linker generates a section with a size
that is the largest of the sizes in the individual object modules. The
attribute max only applies to data sections.

• • • • • • • •
 3-52 TriCore Reference Manual

The name of a section can have a special meaning for locating sections.
The name of code sections should always start with ".text" (or
".pcptext" for PCP code). With data sections, the prefix in the name is
important. The prefix determines if the section is initialized, constant or
uninitialized and which addressing mode is used.

Name prefix Type of DATA section

.data initialized
.zdata initialized, abs 18 addressing
.sdata initialized, a0 addressing
.data_a8 initialized, a8 addressing
.data_a9 initialized, a9 addressing
.rodata constant data
.zrodata constant data, abs 18 addressing
.srodata constant data, a0 addressing
.rodata_a8 constant data, a8 addressing
.rodata_a9 constant data, a9 addressing
ASSEMBLY LANGUAGE

.bss uninitialized
.zbss uninitialized, abs 18 addressing
.sbss uninitialized, a0 addressing
.bss_a8 uninitialized, a8 addressing
.bss_a9 uninitialized, a9 addressing
.ldata a1 addressing (read only constants, literal data)
.pcpdata pcp data

Table 3-1: Data section name prefixes

Note that the compiler uses the following name convention:

prefix.module-name.function-or-object-name

Examples:
.sdecl ".text.t.main", CODE ; declare code section
.sect ".text.t.main" ; activate section

.sdecl ".data.t.var1", DATA ; declare data section

.sect ".data.t.var1" ; activate section
 TriCore Assembly Language 3-53

.sdecl ".text.intvec.00a", CDOE ; declare interrupt

; vector table entry for interrupt 10
.sect ".text.intvec.00a" ; activate section

.SECT (Activate a declared section)

.ORG (Initialize a nameless section)

• • • • • • • •
 3-54 TriCore Reference Manual

.SECT
Syntax
.SECT "name" [, RESET]

Description:
With the .SECT directive you activate a previously declared section with
the name name. Before you can activate a section, you must define the
section with the .SDECL directive. You can activate a section as many
times as you need.

With the section attribute RESET you can reset counting storage allocation
in data sections that have section attribute max.

Examples:
.sdecl ".zdata.t.var2", DATA ; declare data section
.sect ".zdata.t.var2" ; activate section
ASSEMBLY LANGUAGE

.SDECL (Declare a section with name, type and attributes)

.ORG (Initialize a nameless section)
 TriCore Assembly Language 3-55

.SET
Syntax
symbol .SET expression

.SET symbol expression

Description
With the .SET directive you assign the value of expression to symbol
temporarily. If a symbol was defined with the .SET directive, you can
redefine that symbol in another part of the assembly source, using another
.SET. directive.

The .SET directive is useful in establishing temporary or reusable counters

within macros. Expression must be absolute and forward references are
allowed.

Symbols that are set with the .EQU directive, cannot be redefined.

Example
COUNT .SET 0 ; Initialize COUNT. Later on you can
; assign other values to the symbol COUNT.

Related information
..EQU (Assign permanent value to a symbol)

• • • • • • • •
 3-56 TriCore Reference Manual

.SIZE
Syntax
.SIZE symbol, expression

Description
With the .SIZE directive you set the size of the specified symbol to the
value represented by expression.

The .SIZE directive may occur anywhere in the source file unless the
specified symbol is a function. In this case, the .SIZE directive must occur
after the function has been defined.

Example
main: .type func
. ; function main
.
ret16
ASSEMBLY LANGUAGE

main_function_end:
.size main,main_function_end-main

Related information
.TYPE (Set Symbol Type)
 TriCore Assembly Language 3-57

.SPACE
Syntax
[label] .SPACE expression

Description
With the .SPACE directive (Define Storage) the assembler reserves a block
of memory. The reserved block of memory is not initialized to any value.

With expression you specify the number of MAUs (Minimum Addressable

Units) you want to reserve, and how much the location counter will
advance. The expression must be an integer greater than zero and cannot
contain any forward references to address labels (labels that have not yet
been defined). For the TriCore assembler astc, the MAU size is 1 byte. For
the PCP assembler aspcp, the MAU size is 2 bytes for pcp code sections
and 4 bytes for pcp data sections.

If you specify label, it gets the value of the location counter at the start of
the directive processing.

Example
To reserve 12 bytes (not initialized) of memory in a TriCore data section:
.sdecl ".zbss.tst.uninit",DATA
.sect ".zbss.tst.uninit"
uninit .SPACE 12 ; Sample buffer

Related information
.ASCII / .ASCIIZ (Define ASCII string without/with ending NULL)
.BYTE (Define a constant byte)
.FLOAT / .DOUBLE (Define a 32-bit / 64-bit floating-point constant)
.WORD / .HALF (Define a word / halfword)

• • • • • • • •
 3-58 TriCore Reference Manual

.TYPE
Syntax
symbol .TYPE typeid

Description
With the .TYPE directive you set a symbol's type to the specified value in
the ELF symbol table. Valid symbol types are:

FUNC The symbol is associated with a function or other

executable code.

OBJECT The symbol is associated with an object such as a

variable, an array, or a structure.

FILE The symbol name represents the filename of the

compilation unit.

Labels in code sections have the default type FUNC. Labels in data sections
ASSEMBLY LANGUAGE

have the default type OBJECT.

Example
Afunc .TYPE FUNC

Related information
.SIZE (Set Symbol Size)
 TriCore Assembly Language 3-59

.UNDEF
Syntax
.UNDEF symbol

Description
With the .UNDEF directive you can undefine a substitution string that was
previously defined with the .DEFINE directive. The substitution string
associated with symbol is released, and symbol will no longer represent a
valid .DEFINE substitution.

A label is not allowed before this directive.

Example
.UNDEF LEN ; Undefines the LEN substitution string
; that was previously defined with the
; .DEFINE directive

Related information
.DEFINE (Define Substitution String)

• • • • • • • •
 3-60 TriCore Reference Manual

.WARNING
Syntax
.WARNING [{string | exp}[,{string | exp}]...]

Description
With the .WARNING directive (Programmer Generated Warning) you tell
the assembler to output a warning message during the assembling process.

The total warning count will be incremented as with any other warning.
The .WARNING directive is for example useful in combination with
conditional assembly for exceptional condition checking. The assembly
process proceeds normally after the warning has been printed.

Optionally, you can specify an arbitrary number of strings and expressions,

in any order but separated by commas, to describe the nature of the
generated warning. If you use expressions, the assembler outputs the
result. The assembler outputs a space between each argument.
ASSEMBLY LANGUAGE

This directive has no effect on the exit code of the assembler, unless you
use the assembler option --warnings-as-errors. In that case the
assembler exits with exit code 1 (an error).

A label is not allowed before this directive.

Example
.WARNING 'parameter too large'

This results in the warning:

W144: ["filename" line] Parameter out of range

Related information
.FAIL (Programmer Generated Error),
.MESSAGE (Programmer Generated Message)
 TriCore Assembly Language 3-61

.WEAK
Syntax
.WEAK symbol[,symbol]...

Description
With the .WEAK directive you mark one of more symbols as 'weak'. The
symbol can be defined in the same module with the .GLOBAL directive or
the .EXTERN directive. If the symbol does not already exist, it will be
created.

A 'weak' external reference is resolved by the linker when a global (or

weak) definition is found in one of the object files. However, a weak
reference will not cause the extraction of a module from a library to
resolve the reference.

You can overrule a weak definition with a .GLOBAL definition in another

module. The linker will not complain about the duplicate definition, and
ignore the weak definition.

Only program labels and symbols defined with EQU can be made weak.

Example
LOOPA .EQU 1 ; definition of symbol LOOPA
.GLOBAL LOOPA ; LOOPA will be globally
; accessible by other modules
.WEAK LOOPA ; mark LOOPA as weak

Related information
-

• • • • • • • •
 3-62 TriCore Reference Manual

.WORD/.HALF
Syntax
[label] .WORD argument[,argument]...

[label] .HALF argument[,argument]...

Description
With the .WORD or .HALF directive the assembler allocates and initializes
one word (32 bits) or a halfword (16 bits) of memory for each argument.

An argument can be:

• a single or multiple character string constant
• an expression
• NULL (indicated by two adjacent commas: ,,)
Multiple arguments are stored in sets of four or two bytes. If an argument
is NULL its corresponding address locations are filled with zeros.
ASSEMBLY LANGUAGE

If you specify label, it gets the value of the location counter at the start of
the directive processing.

In case of single and multiple character strings, each character is stored in

consecutive bytes whose lower seven bits represent the ASCII value of the
character. The standard C escape sequences are allowed:
.WORD 'R' ; = 0x52
.WORD 'ABCD' ; = 0x41424344

.HALF 'R' ; = 0x52

.HALF 'AB' ; = 0x4142
.HALF 'ABCD' ; = 0x4142
0x4344

If the evaluated argument is too large to be represented in a word /

halfword, the assembler issues an error and truncates the value.

Examples
WRD: .WORD 14,1635,0x34266243,'ABCD'

HLF: .HALF 14,1635,0x2662,'AB'

 TriCore Assembly Language 3-63

With the .BYTE directive you can obain exactly the same effect:
WRD: .BYTE 14,0,0,0,1635%256,6,0,0,
0x43,0x62,0x26,0x34,'D','C','B','A'

HLF: .BYTE 14,0,1635%256,6,0x62,0x26,'B','A'

Related information
.SPACE (Define storage)

.ASCII / .ASCIIZ (Define ASCII string without/with ending NULL)

.BYTE (Define a constant byte)

• • • • • • • •
 3-64 TriCore Reference Manual

3.3.3 OVERVIEW OF ASSEMBLER CONTROLS

The following tables provide an overview of all assembler controls.

Overview of assembler listing controls

Function Description
$LIST ON / OFF Generation of assembly list file temporary ON/OFF
$LIST "flags" Exclude / include lines in assembly list file
$PAGE Generate formfeed in assembly list file
$PAGE settings Define page layout for assemly list file
$PRCTL Send control string to printer
$STITLE Set program subtitle in header of assembly list file
$TITLE Set program title in headerof assembly list file

Overview of miscellaneous assembler controls

ASSEMBLY LANGUAGE

Function Description
$CASE ON / OFF Case sensitive user names ON/OFF
$DEBUG ON / OFF Generation of symbolic debug ON/OFF
$DEBUG "flags" Select debug information
$FPU Allow single precision floating-point instructions
$HW_ONLY Prevent substitution of assembly instructions by
smaller or faster instructions
$IDENT LOCAL / Assembler treats labels by default as local or global
GLOBAL
$MMU Allow memory management instructions
$OBJECT Alternative name for the generated object file
$TCdefect ON / OFF Enable/disable assembler check for specified
functional problem
$TC2 Allow TriCore 2 instructions
$WARNING OFF [num] Suppress all or some warnings
 TriCore Assembly Language 3-65

3.3.4 DETAILED DESCRIPTION OF ASSEMBLER

CONTROLS
The assembler recognizes both upper and lower case for controls.

• • • • • • • •
 3-66 TriCore Reference Manual

$CASE ON / OFF
Syntax
$CASE ON (default)
$CASE OFF

Description
With the $CASE ON and $CASE OFF controls you specify whether the
assembler operates in case sensitive mode or not. By default the assembler
operates in case sensitive mode. This means that all user-defined symbols
and labels are treated case sensitive, so LAB and Lab are distinct. Note that
instruction mnemonics, register names, directives and controls are always
treated case insensitive.

Example
;begin of source
$CASE OFF ; assembler in case insensitive mode
ASSEMBLY LANGUAGE

Related option
Assembler option -c (Switch to case insensitive mode) in section 5.2,
Assembler Options, of Chapter Tool Options.

Related information
-
 TriCore Assembly Language 3-67

$DEBUG ON / OFF
Syntax
$DEBUG ON
$DEBUG OFF
$DEBUG "flags"

Description
With the $DEBUG ON and $DEBUG OFF controls you turn the generation
of debug infomation on or off. ($DEBUG ON is similar to the assembler
option -gl).

If you use $DEBUG control with flags, you can set the following flags:

a/A assembler source line information

h/H pass HLL debug information

You cannot use these two types of debug information both. So,
$DEBUG "ah" is not allowed.

l/L local symbols debug information

s/S always debug; either "AhL" or "aHl"

Debug information that is generated by the C compiler, is always passed

to the object file.

Example
;begin of source
$DEBUG ON ; generate local symbols debug information

Related option
Assembler option -g (Select debug information) in section 5.2, Assembler
Options, of Chapter Tool Options.

Related information
-

• • • • • • • •
 3-68 TriCore Reference Manual

$FPU
Syntax
$FPU

Description
With the $FPU control you instruct the assembler to accept and encode
single precision floating-point instructions in the assembly source file.

When you use this control, the define __FPU__ is set to 1. By default the
define __FPU__ is set to 0 which tells the assembler not to accept single
precision floating-point instructions.

Example
;begin of source
$FPU ; the use of single precision FPU instructions
; in this source is allowed.
ASSEMBLY LANGUAGE

Related option
Assembler option --fpu-present (Allow the use of single precision
floating-point instructions) in section 5.2, Assembler Options, of Chapter
Tool Options.

Related information
-
 TriCore Assembly Language 3-69

$HW_ONLY
Syntax
$HW_ONLY

Description
Normally the assembler replaces instructions by other, smaller or faster
instructions. For example, the instruction jeq d0,#0,label1 is replaced
by jz d0,label1.

With the $HW_ONLY control you instruct the assembler to encode all
instruction as they are. The assembler does not substitute instructions with
other, faster or smaller instructions.

Example
;begin of source
$HW_ONLY ; the assembler does not substitute
; instructions with other, smaller or
; faster instructions.

Related option
Assembler option -Og (Allow generic instructions) in section 5.2,
Assembler Options, of Chapter Tool Options.

Related information
-

• • • • • • • •
 3-70 TriCore Reference Manual

$IDENT
Syntax
$IDENT LOCAL
$IDENT GLOBAL

Description
With the controls $IDENT LOCAL and $IDENT GLOBAL you tell the
assembler how to treat symbols that you have not specified explicitly as
local or global with the assembler directives .LOCAL or .GLOBAL.

By default the assembler treats all symbols as local symbols unless you
have defined them explicitly as global.

Example
;begin of source
$IDENT GLOBAL ; assembly labels are global by default
ASSEMBLY LANGUAGE

Related option
Assembler option -i (Treat labels by default local / global) in section 5.2,
Assembler Options, of Chapter Tool Options.

Related information
Assembler directive .LOCAL (Local symbol declaration)
Assembler directive .GLOBAL (Global symbol declaration)
 TriCore Assembly Language 3-71

$LIST ON / OFF
Syntax
$LIST ON
.
. ; assembly source lines
.
$LIST OFF

Description
If you generate a list file with the assembler option -l, you can use the
$LIST ON and $LIST OFF controls to specify which source lines the
assembler must write to the list file. Without the command line option -l,
the $LIST ON and $LIST OFF controls have no effect.

The $LIST ON control actually increments a counter that is checked for a

positive value and is symmetrical with respect to the $LIST OFF control.
Note the following sequence:
; Counter value currently 1
$LIST ON ; Counter value = 2
$LIST ON ; Counter value = 3
$LIST OFF ; Counter value = 2
$LIST OFF ; Counter value = 1

The listing still would not be disabled until another $LIST OFF control
was issued.

Example
Suppose you assemble the following assembly source with the assembler
option -l:
.SDECL ".text",CODE
.SECT ".text"
... ; source line in list file
$LIST OFF
... ; source line not in list file
$LIST ON
... ; source line also in list file
.END

• • • • • • • •
 3-72 TriCore Reference Manual

The assembler generates a list file with the following lines:

.SDECL ".text",CODE
.SECT ".text"
... ; source line in list file
$LIST ON
... ; source line also in list file
.END

Related option
Assembler option -l (Generate list file) in section 5.2, Assembler Options,
of Chapter Tool Options.

Related information
Assembler control $LIST (Exclude / include lines in assembly list file)

Assembler function @LST() in section 3.2, Built-in Asembly Functions.

ASSEMBLY LANGUAGE
 TriCore Assembly Language 3-73

$LIST flags
Syntax
Begin of assembly file

$LIST "flags"

Description
If you generate a list file with the assembler option -l, you can use the
$LIST controls to specify which type of source lines the assembler must
exclude from the list file. Without the command line option -l, the $LIST
control has no effect.

You can set the following flags to remove or include lines:

c/C Lines with assembler controls

d/D Lines with section directives (.SECT and .SDECL)
e/E Lines with symbol definition directives (.EXTERN, .GLOBAL,
.LOCAL, .CALLS)
g/G Lines with generic instruction expansion
i/I Lines with generic instructions
l/L #Line source lines
m/M Lines with macro definitions (.MACRO and .DUP)
n/N Empty source lines
p/P Lines with conditional assembly
q/Q Lines with the .EQU or .SET directive
r/R Lines with relocation characters ('r')
v/V Lines with .EQU or .SET values
w/W Wrapped part of a line
x/X Lines with expanded macros
y/Y Lines with cycle counts

If you do not specify this control or the assembler option -Lflag, the
assembler uses the default: -LcDEGilMnPqrVWXy.

Example
To exclude assembly files with controls from the list file:
;begin of source
$LIST "c"

• • • • • • • •
 3-74 TriCore Reference Manual

Related option
Assembler option -L (List file formatting options) in section 5.2, Assembler
Options, of Chapter Tool Options.

Related information
Assembler control $LIST ON / OFF (Assembly list file ON / OFF)

Assembler function @LST() in section 3.2, Built-in Asembly Functions.

ASSEMBLY LANGUAGE
 TriCore Assembly Language 3-75

$MMU
Syntax
$MMU

Description
With the $MMU control you instruct the assembler to accept and encode
memory management instructions in the assembly source file.

When you use this control, the define __MMU__ is set to 1.

Example
;begin of source
$MMU ; the use of memory management instructions
; in this source is allowed.

Related option
Assembler option --mmu-present (Allow the use of memory
management instructions) in section 5.2, Assembler Options, of Chapter
Tool Options.

Related information
-

• • • • • • • •
 3-76 TriCore Reference Manual

$OBJECT
Syntax
$OBJECT "file"
$OBJECT OFF

Description
With the $OBJECT control you can specify an alternative name for the
generated object file. With the $OBJECT OFF control, the assembler does
not generate an object file at all.

Example
;Begin of source
$object "x1.o" ; generate object file x1.o

Related option
Assembler option -o (Define output filename) in section 5.2, Assembler
ASSEMBLY LANGUAGE

Options, of Chapter Tool Options.

Related information
-
 TriCore Assembly Language 3-77

$PAGE
Syntax
$PAGE [width,length,blanktop,blankbtm,blankleft]

Description
If you generate a list file with the assembler option -l, you can use the
$PAGE control to format the generated list file.

width Number of characters on a line (1-255). Default is 132.

length Number of lines per page (10-255). Default is 66. As a special

case a page length of 0 (zero) turns off all headers, titles,
subtitles, and page breaks.

blanktop Number of blank lines at the top of the page. Default = 0.

Specify a value so that blanktop + blankbtm ≤ length - 10.

blankbtm Number of blank lines at the bottom of the page. Default = 0.

Specify a value so that blanktop + blankbtm ≤ length - 10.

blankleft Number of blank columns at the left of the page. Default = 0.

Specify a value smaller than width.

If you use the $PAGE control without arguments, it causes a 'formfeed': the
next source line is printed on the next page in the list file. The $PAGE
control itself is not printed.

You can omit an argument by using two adjacent commas. If the

remaining arguments after an argument are all empty, you can omit them.

Example
$PAGE ; formfeed, the next source line is printed
; on the next page in the list file.

$PAGE 96 ; set page width to 96. Note that you can

; omit the last four arguments.

$PAGE ,,3,3; use 3 line top/bottom margins.

Related option
-

• • • • • • • •
 3-78 TriCore Reference Manual

Related information
Assembler control $STITLE (Set program subtitle in header of list file)
Assembler control $TITLE (Set program title in header of list file)

Assembler option -l (Generate list file) in Section 5.2, Assembler Options,

of Chapter Tool Options.

Assembler option -L (List file formatting options) in Section 5.2, Assembler

Options, of Chapter Tool Options.
ASSEMBLY LANGUAGE
 TriCore Assembly Language 3-79

$PRCTL
Syntax
$PRCTL exp|string[,exp|string]...

Description
If you generate a list file with the assembler option -l, you can use the
$PRCTL control to send control strings to the printer.

The $PRCTL control simply concatenates its arguments and sends them to
the listing file (the control line itself is not printed unless there is an error).

You can specify the following arguments:

exp a byte expression which may be used to encode

non-printing control characters, such as ESC.

string an assembler string. which may be of arbitrary length, up to

the maximum assembler-defined limits.

The $PRCTL control can appear anywhere in the source file; the assembler
sends out the control string at the corresponding place in the listing file.

If a $PRCTL control is the last line in the last input file to be processed,
the assembler insures that all error summaries, symbol tables, and
cross-references have been printed before sending out the control string.
In this manner, you can use a PRCTL control to restore a printer to a
previous mode after printing is done.

Similarly, if the $PRCTL control appears as the first line in the first input
file, the assembler sends out the control string before page headings or
titles.

Example
$PRCTL $1B,'E' ; Reset HP LaserJet printer

Related option
-

Related information
Assembler option -l (Generate list file) in Section 5.2, Assembler Options,
of Chapter Tool Options.

• • • • • • • •
 3-80 TriCore Reference Manual

$STITLE
Syntax
$STITLE "title"

Description
If you generate a list file with the assembler option -l, you can use the
$STITLE control to specify the program subtitle which is printed at the
top of all succeeding pages in the assembler list file below the title.

The specified subtitle is valid until the assembler encouters a new STITLE
control. By default, the subtitle is empty.

The $STITLE control itself will not be printed in the source listing.

If the page width is too small for the title to fit in the header, it will be
truncated.

Example
ASSEMBLY LANGUAGE

$TITLE 'This is the title'

$STITLE 'This is the subtitle'

The header of the second page in the list file will now be:
TASKING TriCore Assembler vx.yrz Build nnn SN 00000000
This is the title Page 2
This is the subtitle

Related option
-

Related information
Assembler control $TITLE (Set program title in header of list file)

Assembler option -l (Generate list file) in Section 5.2, Assembler Options,

of Chapter Tool Options.
 TriCore Assembly Language 3-81

$TC
Syntax
$TCdefect ON
$TCdefect OFF

Description
With this control you can enable or disable specific CPU functional
problem checks.

To enable the assembler checks for all TriCore CPU TC112 problems
(respectively TC113 problems) at once, use the control $TC112_DEFECTS
(respectively $TC113_DEFECTS ).

Example
$TC112_COR1 ON ; enable assembler check for CPU
functional problem TC112_COR1

Related option
Assembler option --silicon-bug (Check on CPU functional defect) in
section 5.2, Assembler Options, of Chapter Tool Options.

Related information
See Chapter 9, CPU Functional Problems, for more information about the
individual problems.

• • • • • • • •
 3-82 TriCore Reference Manual

$TC2
Syntax
$TC2

Description
With the $TC2 control you instruct the assembler to accept and encode
TriCore 2 instructions in the assembly source file.

When you use this control, the define __TC2__ is set to 1.

Example
;begin of source
$TC2 ; the use of TriCore 2 instructions
; in this source is allowed.

Related option
Assembler option --is-tricore2 (Allow the use of TriCore 2 instructions)
ASSEMBLY LANGUAGE

in section 5.2, Assembler Options, of Chapter Tool Options.

Related information
-
 TriCore Assembly Language 3-83

$TITLE
Syntax
$TITLE "title"

Description
If you generate a list file with the assembler option -l, you can use the
$TITLE control to specify the program title which is printed at the top of
each page in the assembler list file.

By default, the title is empty.

If the page width is too small for the title to fit in the header, it will be
truncated.

Example
$TITLE 'This is the title'

The header of the list file will now be:

TASKING TriCore Assembler vx.yrz Build nnn SN 00000000
This is the title Page 1

Related option
-

Related information
STITLE (Set program subtitle in header of assembly list file)

• • • • • • • •
 3-84 TriCore Reference Manual

$WARNING OFF
Syntax
$WARNING OFF
$WARNING OFF number

Description
With the $WARNING OFF control you can suppresses all warning
messages or specific warning messages.
• By default, all warnings are reported.
• If you specify this option but without numbers, all warnings are
suppressed.
• If you specify this option with a number, only the specified warning is
suppressed.

Example
$WARNING OFF ; all warning messages are suppressed
ASSEMBLY LANGUAGE

$WARNING OFF 135 ; suppress warning message 135

Related option
Assembler option -w (Suppress some or all warnings) in section 5.2,
Assembler Options, of Chapter Tool Options.

Related information
-
CHAPTER
RUN-TIME
ENVIRONMENT

4
 4-2 TriCore Reference Manual

CHAPTER
4
RUN-TIME
 Run-time Environment 4-3

4.1 INTRODUCTION
This chapter describes the startup code used by the TASKING TriCore C
compiler, the stack layout and the heap; and the floating-point arithmetic.

4.2 STARTUP CODE

You need the run-time startup code to build an executable application.
The default startup code consists of the following components:
• Initialization code. This code is executed when the program is
initiated and before the function main() is called.
• Exit code. This controls the closedown of the application after the
program's main function terminates.
• The trap vector table. This contains default trap vectors.
The startup code is part of the C library libc.a, and the source is present
in the file cstart.asm in the directory lib\src.

If the default run-time startup code does not match your configuration,
you need to modify the startup code accordingly.

See also section 7.6, Linking the C Startup Code in Chapter Using the Linker
of the User's Manual.

The entry point of the startup code (power-on vector) is label _START.
This global label should not be removed, since the C compiler refers to it.
It is also used as the default start address of the application.

Initialization code
The following initialization actions are executed before the application
starts:

1. Re-enable and reset the call depth counter and make A0, A1, A8, A9
write-able. It is required for CrossView Pro that these RESET values are
restored for each time the startup code is executed.

2. Initialize the user stack pointer. The user stack pointer is loaded into
memory by the stack address, located at _lc_ue_ustack . This label is
defined in the Linker Script File. See section 4.3, Stack Usage for
detailed information on the stack.

• • • • • • • •
 4-4 TriCore Reference Manual

3. Clear Previous Context Pointer Segment Address and Offset Field. It is

required for CrossView Pro's stack trace that these RESET values are
restored for each time the startup code is executed.

4. Setup the context save area lists. Tables with start/end addresses go in
a separate 'csa_areas' section.

5. Initialize registers and bus configuration. In the file cstart.asm the

actual location of several special function registers is required. These
addresses are specified in the regcpu_name.def SFR system include
files. You can include such a file with the assembler option
-Ccpu_name. In EDE the appropriate file is included when you have
selected a CPU type. If you do not specify an SFR file, the default SFR
regtc11ib.def file is included.

6. Load Base Address of Trap Vector Table. This address is indicated by

the linker label _lc_u_trap_tab as defined in the Linker Script File.

7. Load Base Address of Interrupt Vector Table. This address is indicated

by the linker label _lc_u_int_tab as defined in the Linker Script File.

8. Initialize the interrupt stack pointer. The interupt stack pointer is

loaded into memory by the interrupt stack address, located at
_lc_ue_istack . This label is defined in the Linker Script File.

9. Initialize and clear C variables.

10. Copy initialized sections from ROM to RAM, using a linker generated
table (also known as the 'copy table') and a run-time library function
_c_init.

11. Initialize the argc and argv arguments to zero.

12. Call the entry point of your application with a call to function main().

Exit code
RUN-TIME

When the C application 'returns', which is not likely to happen in an

embedded environment, the program ends with a DEBUG16 instruction, at
the assembly label _exit. When using a debugger, it can be useful to set
a breakpoint on this label to indicate that the program has reached the
end, or that the library function exit() has been called.
 Run-time Environment 4-5

Trap vector table

The default startup code makes sure that the trap vectors for exceptions 0
to 7 are filled in. Default trap vectors are resolved from the C library. You
can overrule these routines with your own exception routines.

To disable a default trap vector from EDE:

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

The Project Options dialog appears.

2. Expand the Processor entry, expand Startup, expand Startup Code

and select Trap Vectors.

3. Disable the trap vectors you do not want to be automatically defined in

the startup code.

See also section 3.9.2, Interrupt and Trap Functions in Chapter TriCore C
Language of the User's Manual.

Control Startup Code from EDE

To control cstart.asm from within EDE, you first have to add
cstart.asm to your project:

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

The Project Options dialog appears.

2. Expand the Processor entry and select Startup.

3. Enable the option Automatically copy and link cstart.asm to your

project.

The file cstart.asm is copied to your project directory and added to

your project.

Now you can specify all your startup settings in the pages Startup Code,
Boot Memory and Memory Control.

You can specify CPU settings in the same dialog:

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

The Project Options dialog appears.

2. Expand the Processor entry and select Bus Configuration.

• • • • • • • •
 4-6 TriCore Reference Manual

3. Select the appropriate bus configuration settings.

EDE automatically defines macros according to the selected settings.

Macro Preprocessor Symbols

A number of macro preprocessor symbols are used in the startup code.
These can be enabled or disabled using the assembler command line
option -D with the following syntax:

-Didentifier[=replacement]).

In the startup file (cstart.asm) the following macro preprocessor

symbols are used:

Define Description
External Boot Memory Configuration (BOOTCFG)
_BOOTCFG_VALUE Boot memory Offset Address + 0x4
Memory Control (PMUCON/DMUCON)
_PMU_CON_VALUE If defined, value of PMU Control register
_PMU_EIFCON_VALUE If defined, value of PMU External Instruction
Fetch Control register
_DMU_CON_DCAON If defined, Enable data cache
Startup
_NO_BTV_INIT If defined, Base Address of Trap Vector Table is
not initialized with trap table start address
(trap_tab).
_NO_BIV_INIT If defined, Base Address of Interrupt Vector
Table is not initialized with interrupt table start
address (_lc_u_int_tab).
_NO_ISP_INIT If defined, Interrupt Stack Pointer is not initialized
with end address of interrupt stack
RUN-TIME

(_lc_ue_istack).
_NO_USP_INIT If defined, User Stack Pointer is not initialized
with end address of user stack (_lc_ue_istack).
_NO_PCX_RESET If defined, the Previous Context is not explicitly
cleared.
_NO_PSW_RESET If defined, the Call Depth Counter is not explicitly
cleared.
 Run-time Environment 4-7

Define Description
_NO_A0A1_ADDRESSING If defined, global address register A0/A1 is not
initialized with start address of the _a0/_a1
addressable area (_lc_gb_a0/1).
_NO_A8A9_ADDRESSING If defined, global address register A8/A9 is not
initialized with start address of the _a8/_a9
addressable area (_lc_gb_a8/9).
_NO_CSA_INIT If defined, Context Save Area lists are not
initialized.
_NO_WATCHDOG_INIT If defined, Watchdog timer disabled.
_NO_BUS_CONF If defined, bus configuration registers are not
initialized.
_NO_C_INIT If defined, C variables are not initialized.
_NO_ARG_INIT If defined, disable initialization of argc and argv[].
_NO_EXIT If defined, C library function exit() or abort() not
supported.
_USERDEFINED_TRAP_n If defined, the default trap vector n is disabled.
Miscellaneous
_CALL_INIT Can be set to a function to be called before
main. This function cannot have a return or
arguments. This function can be used, for
example, to initialize the serial port before main
is called. This is useful for building programs
without making any modifications to the original
source.
_CALL_ENDINIT Can be set to a function to be called before the
ENDINIT instruction is executed. Like the
CALLINIT function, it cannot not have a return
value or arguments.
CPU functional bypasses
_TC112_XXX If defined, TC112 CPU functional defect XXX is
bypassed and/or checked.
_TC113_XXX If defined, TC113 CPU functional defect XXX is
bypassed and/or checked. See Chapter 9 CPU
Functional Problems for a complete list of these
macros.

Table 4-1: Defines used in cstart.src

• • • • • • • •
 4-8 TriCore Reference Manual

The following table shows the linker labels used in the startup code.

Define Description
_START start label, mentioned in LSL file (tc_arch.lsl)
_c_init label copy table init function
main start label user C program
exit start label of exit() function
_exit exit() function jumps to this place
_CALL_ENDINIT label called before ENDINIT
_CALL_INIT _CALL_INIT label called before main()
_lc_gb_a0 linker label start of A0 addressable area
_lc_gb_a1 linker label start of A1 addressable area
_lc_gb_a8 linker label start of A8 addressable area
_lc_gb_a9 linker label start of A9 addressable area
_lc_u_int_tab linker label interrupt table
_lc_ub_csa linker label context save area begin
_lc_ue_csa linker label context save area end
_lc_ue_istack linker label interrupt stack end
_lc_ue_ustack linker label user stack end

Table 4-2: Linker labels used in startup code

RUN-TIME
 Run-time Environment 4-9

4.3 STACK USAGE

The stack is used for local automatic variables and function parameters.

The following diagram show the structure of a stack frame.

high memory
incoming
stack
ÉÉÉÉÉÉ
parameters

ÉÉÉÉÉÉ
sp
grows down
on entry

local variables
framesize

outgoing
parameters
sp
low memory
($sp)
during execution

Figure 4-1: Stack diagram

The stack size is defined in the linker script file (tc_arch.lsl in

directory include.lsl) with the macro USTACK and ISTACK, which
results in sections called ustack and istack.

The linker defined label _lc_ue_ustack refers to the top of the user
stack area and is used in the file cstart.asm to initialize the user stack
pointer register (SP). The linker defined label _lc_ue_istack refers to
the top of the interrupt stack area and is used in the file cstart.asm to
initialize the interrupt stack pointer register (ISP)

As long as the user program does not change the IS bit in the program
status word (PSW), only the user stack is used. Refer to the TriCore
Architecture (v1.3) Manual for the implications of an IS bit change.

• • • • • • • •
 4-10 TriCore Reference Manual

4.4 HEAP ALLOCATION

The heap is only needed when you use one or more of the dynamic
memory management library functions: malloc(), calloc(), free()
and realloc(). The heap is a reserved area in memory. Only if you use
one of the memory allocation functions listed above, the linker
automatically allocates a heap, as specified in the linker script file with the
keyword heap.

A special section called heap is used for the allocation of the heap area.
The size of the heap is defined in the linker script file (tc_arch.lsl in
directory include.lsl) with the macro HEAP, which results in a section
called heap. The linker defined labels _lc_bh and _lc_eh (begin and
end of heap) are used by the library function sbrk(), which is called by
malloc() when memory is needed from the heap.

The special heap section is only allocated when its linker labels are used
in the program.

4.5 FLOATING-POINT ARITHMETIC

Floating-point arithmetic support for the compiler ctc is included in the
software as a separate set of libraries or in the hardware when available
(only single precision). During linking you have to specify the desired
floating-point library after the C library. The libraries are reentrant, and
only use temporary program stack memory.

To ensure portability of floating-point arithmetic, floating-point arithmetic

for the compiler ctc has been implemented complying with the IEEE-754
standard for floating-point arithmetic. See the IEEE Standard Binary for
Floating-Point Arithmetic document [IEEE Computer Society, 1985] for
more details on the floating-point arithmetic definitions. This document is
referred to as IEEE-754 in this manual.
RUN-TIME

The compiler ctc supports both single and double precision floating-point
operations using the ISO C types float and double respectively. To
optimize for speed, also a non-trapping library is included.

It is possible to intercept floating-point exceptional cases and, if desired,

handle them with an application defined exception handler. The
intercepting of floating-point exceptions is referred to as 'trapping'.
Examples of how to install a trap handler are included.
 Run-time Environment 4-11

4.5.1 COMPLIANCE WITH IEEE-754

The level to which the floating-point implementation complies with the
IEEE-754 standard, depends on the choosen configuration.

All floating-point calculations are executed using the 'round to nearest

(even)' rounding mode, since this is required by ANSI-C 89. This is
conform IEEE-754. Because there are no double precision floating-point
hardware instructions, an emulating library is always needed for double
precision calculation.

When the use of hardware FPU instructions is choosen (--fpu-present),

the available hardware instructions for single precision floating-point will
be used either in the compiler or in one of the libraries. For double
precision floating-point calculations the choosen floating-point emulaton
library will be used. When no hardware FPU instructions are allowed, all
floating-point operations will be used from the choosen floating-point
emulaton library.

In EDE you can specify to use the single precision floating-point:

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

The Project Options dialog appears.

2. Expand the C Compiler entry and select Miscellaneous.

3. Enable the option Single precision floating-point only: treat type

'double' as 'float'.

Compiler option --fpu-present in Chapter 5, Tool Options.

Compliance with IEEE-754: TriCore hardware FPU instructions

The following implementation issues for the single precision hardware
instructions (optionally implemented on the TriCore chip), are important:
• subnormals are not supported (hardware design decision).
• when converting single precision floats to integers, rounding is done to
the nearest (even) integer. This does not comply with ANSI-C 89 or
ISO-C 99, but does comply with IEEE-754, since this is the current
rounding mode (hardware design decision).
• when a converted single precision float overflows the target integer
type, the value is saturated to MAX_INT or MIN_INT (hardware design
decision).

• • • • • • • •
 4-12 TriCore Reference Manual

• whenever a double precision float is involved, the results are

determined by the chosen emulation library.

Compliance with IEEE-754: Trapping emulation library

The following implementation issues for the trapping floating-point library
are important:
• subnormals are not supported. This is conform the TriCore hardware
design.
• when converting floats to integers, the value is truncated. This complies
with ANSI-C 89 and ISO-C 99, but does not comply with IEEE-754,
since the current rounding mode is 'round to nearest (even)'.
• when a converted float overflows the target integer type, a predictable
value is assigned to the target integer.

Compliance with IEEE-754: Hand-optimized non-trapping emulation

library
The following implementation issues for the non-trapping floating-point
library are important:
• when calculating with floats, rounding is done to the nearest integer
(rounding towards infinity when equally near).
• there is no distinction between -0 and +0
• when an operand of a calculation is a NaN, Inf or subnormal, the result
is undefined.
• when the result of a calculation would be a subnormal, the result is 0.
• whenever a NaN or Inf would be the result of a calculation, the result
is undefined
• when converting single precision floats to integers, rounding is done to
the nearest integer (rounding towards infinity when equally near). This
is similar to the TriCore FPU hardware.
• when converting double precision floats to integers, the value is
RUN-TIME

truncated. This is similar to the trapping emulation library.

• when a converted float overflows the target integer type, the value is
saturated to MAX_INT or MIN_INT.
 Run-time Environment 4-13

4.5.2 SPECIAL FLOATING-POINT VALUES

Below is a list of special, IEEE-754 defined, floating-point values as they
can occur during run-time.

Special value Sign Exponent Mantissa

+0.0 (Positive Zero) 0 all zeros all zeros
-0.0 (Negative Zero) 1 all zeros all zeros
+INF (Positive Infinite) 0 all ones all zeros
-INF (Negative Infinite) 1 all ones all zeros
NaN (Not a number) 0 all ones not all zeros

Table 4-3: Special floating-point values

4.5.3 TRAPPING FLOATING-POINT EXCEPTIONS

Four floating-point libraries are delivered:

Library to link Description

libfp.a Floating-point library (non-trapping, no FPU).
This is the default.
libfpt.a Floating-point library (trapping, no FPU)
(Control program option --fp-trap)
libfp_fpu.a Floating-point library (non-trapping, with FPU instructions)
(Compiler option --fpu-present)
libfpt_fpu.a Floating-point library (trapping, with FPU instructions)
(Control program option --fp-trap, compiler option
--fpu-present)

Table 4-4: Floating-point libraries

Both EDE and the control program cctc automatically select the
appropriate libraries depending on the specified TriCore derivative. By
specifying the --fp-trap option to the control program cctc, the trapping
type floating-point library is linked into your application. By specifying
the --fpu-present option to the control program cctc, a floating-point
library with single precision FPU instructions is linked into your
application. If these options are not specified, the floating-point library
without trapping mechanism and without FPU instructions is used.

• • • • • • • •
 4-14 TriCore Reference Manual

In EDE you can specify to use the trapping type floating-point library as
follows:

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

The Project Options dialog appears.

2. Expand the Linker entry and select Libraries.

3. Enable the option Use traping floating-point library.

IEEE-754 Trap Handler

In the IEEE-754 standard a trap handler is defined, which is invoked on
(specified) exceptional events, passing along much information about the
event. To install your own trap handler, use the library call
_fp_install_trap_handler. When installing your own exception
handler, you must select on which types of exceptions you want to have
your handler invoked, using the function call
_fp_set_exception_mask . See below for more details on the
floating-point library exception handling function interface.

SIGFPE Signal Handler

In ANSI-C the regular approach of dealing with floating-point exceptions
is by installing a so-called signal handler by means of the ANSI-C library
call signal. If such a handler is installed, floating-point exceptions cause
this handler to be invoked. To have the signal handler for the SIGFPE
signal actually become operational with the provided floating-point
libraries, a (very) basic version of the IEEE-754 exception handler must be
installed (see example below) which will raise the desired signal by means
of the ANSI-C library function call raise. For this to be achieved, the
function call _fp_install_trap_handler is present. When installing
your own exception handler, you will have to select on which types of
exceptions you want to receive a signal, using the function call
_fp_set_exception_mask . See further below for more details on the
RUN-TIME

floating-point library exception handling function interface.

There is no way to specify any information about the context or nature of

the exception to the signal handler. Just that a floating-point exception
occurred can be detected. See therefor the IEEE-754 trap handler
discussion above if you want more control over floating-point results.
 Run-time Environment 4-15

Example:
#include <float.h>
#include <signal.h>

static void pass_fp_exception_to_signal(

_fp_exception_info_t *info )
{
info; /* suppress parameter not used warning */

/* cause SIGFPE signal to be raised */

raise( SIGFPE );
/*
* now continue the program
* with the unaltered result
*/
}

4.5.4 FLOATING-POINT TRAP HANDLING API

For purposes of dealing with floating-point arithmetic exceptions, the
following library calls are available:
#include <float.h>

int _fp_get_exception_mask( void );

void _fp_set_exception_mask( int );

A pair of functions to get or set the mask which controls which type of
floating-point arithmetic exceptions are either ignored or passed on to the
trap handler. The types of possible exception flag bits are defined as:
EFINVOP
EFDIVZ
EFOVFL
EFUNFL
EFINEXCT

while,
EFALL

is the OR of all possible flags. See below for an explanation of each flag.

• • • • • • • •
 4-16 TriCore Reference Manual

#include <float.h>

int _fp_get_exception_status( void );

void _fp_set_exception_status( int );

A pair of functions for examining or presetting the status word containing

the accumulation of all floating-point exception types which occurred so
far. See the possible exception type flags above.
#include <float.h>

void _fp_install_trap_handler( void (*)

(_fp_exception_info_t * ) );

This function call expects a pointer to a function, which in turn expects a

pointer to a structure of type _fp_exception_info_t . The members of
_fp_exception_info_t are:

exception

This member contains one of the following (numerical) values:

EFINVOP
EFDIVZ
EFOVFL
EFUNFL
EFINEXCT

operation

This member contains one of the following numbers:

_OP_ADDITION
_OP_SUBTRACTION
_OP_COMPARISON
_OP_EQUALITY
_OP_LESS_THAN
RUN-TIME

_OP_LARGER_THAN
_OP_MULTIPLICATION
_OP_DIVISION
_OP_CONVERSION

source_format
destination_format
 Run-time Environment 4-17

Numerical values of these two members are:

_TYPE_SIGNED_CHARACTER
_TYPE_UNSIGNED_CHARACTER
_TYPE_SIGNED_SHORT_INTEGER
_TYPE_UNSIGNED_SHORT_INTEGER
_TYPE_SIGNED_INTEGER
_TYPE_UNSIGNED_INTEGER
_TYPE_SIGNED_LONG_INTEGER
_TYPE_UNSIGNED_LONG_INTEGER
_TYPE_FLOAT
_TYPE_DOUBLE

operand1 /* left side of binary or */

/* right side of unary */
operand2 /* right side for binary */
result

These three are of the following type, to receive and return a value
of arbitrary type:
typedef union _fp_value_union_t
{
char c;
unsigned char uc;
short s;
unsigned short us;
int i;
unsigned int ui;
long l;
unsigned long ul;
float f;
#if ! _SINGLE_FP
double d;
#endif
}
_fp_value_union_t;

The member d is not present when specifying the -F option (treat double
as float) to the C compiler.

• • • • • • • •
 4-18 TriCore Reference Manual

The following table lists all the exception code flags, the corresponding
error description and result:

Error Description Exception Flag Default Result with Trapping

Invalid Operation EFINVOP NaN
Division by zero EFDIVZ +INF or -INF
Overflow EFOVFL +INF or -INF
Underflow EFUNFL zero
Inexact EFINEXT undefined
INF Infinite which is the largest absolute floating-point number,
which is always: -INF < every finite number < +INF
NAN Not a Number, a symbolic entity encoded in floating-point format.

Table 4-5: Exception Type Flag Codes

To ensure all exception types are specified, you can specify EFALL to a
function, which is the binary OR of all above enlisted flags.
RUN-TIME
CHAPTER

TOOL OPTIONS

5
 5-2 TriCore Reference Manual

CHAPTER
5
TOOL OPTIONS
 Tool Options - Compiler 5-3

5.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...

The Project Options dialog appears.

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:
ctc -Oac test.c
ctc --optimize=+coalesce,+cse test.c

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

• • • • • • • •
 5-4 TriCore Reference Manual

-? (--help)
EDE
-

Command line syntax

-?

--help[=item]

You can specify the following arguments:

intrinsics Show the list of intrinsic functions

options Show extended option descriptions
pragmas Show the list of supported pragmas

Description
Displays an overview of all command line options. When you specify an
argument you can list extended information such as a list of intrinsic
functions, pragmas or option descriptions.

Example
The following invocations all display a list of the available command line
options:
ctc -?
ctc --help
TOOL OPTIONS

ctc

The following invocation displays a list of the available pragmas:

ctc --help=pragmas

Related information
-
 Tool Options - Compiler 5-5

-A (--language)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the C Compiler entry and select Language.

3. Enable or disable the options Allow C++ style comments in ISO C90
mode and Allow relaxed const check for string literals.

Command line syntax

-A[flags]

--language=[flags]

You can set the following flags:

p/P (+/-comments) Allow C++ style (//)comments in ISO C90

x/X (+/-strings) Relaxed const check for string literals

Default
-Apx

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

The option -A (--language) without flags is the equivalent of -APX and

disables all language extensions.

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.

With -Ax you tell the compiler not to check for assignments of a constant
string to a non-constant string pointer. With this option the following
example does not produces a warning:
char *p;
void main( void ) { p = "hello"; }

• • • • • • • •
 5-6 TriCore Reference Manual

Example
ctc -APx -c90 test.c
ctc --language=-comments,+strings --iso=90 test.c

The compiler compiles in ISO C90 mode, accepts assignments of a

constant string to a non-constant string pointer but ignores C++ style
comments.

Related information
Compiler option -c (ISO C standard)
TOOL OPTIONS
 Tool Options - Compiler 5-7

--align
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the C Compiler entry and select Code Generation.

3. Specify a value in the Minimum alignment field.

Command line syntax

--align=value

Default
--align=1

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:
ctc --align=4 test.c

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

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 Manual.

• • • • • • • •
 5-8 TriCore Reference Manual

-C (--cpu)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Processor entry and select Processor Definition.

3. Select a processor from the Target processor list.

Command line syntax

-Ccpu

--cpu=cpu

Description
With this option you define the target processor for which you create your
application. Default the control program generates an object file for the
TC11IB.

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 always includes the register file regcpu.sfr, unless you
disable the option Automatic inclusion of '.sfr' file on the Preprocessing
TOOL OPTIONS

page of the Compiler options (command line option --no-tasking-sfr).

Example
To compile the file test.c for the TC11IB processor and use the SFR file
regtc11ib.sfr :

ctc -Ctc11ib test.c

ctc --cpu=tc11ib test.c

To avoid conflicts, make sure you specify the same target processor to the
assembler.
 Tool Options - Compiler 5-9

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.4, Calling the Compiler, in Chapter Using the Compiler of the
User's Manual.

• • • • • • • •
 5-10 TriCore Reference Manual

-c (--iso)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the C Compiler entry and select Language.

3. Select the ISO C standard C90 or C99.

Command line syntax

-c{90|99}

--iso={90|99}

Default
-c99

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:
TOOL OPTIONS

ctc -c90 test.c

ctc --iso=90 test.c

Related information
Compiler option -A (Language extensions)
 Tool Options - Compiler 5-11

--check
EDE
1. In the project window, select the file you want to check.

2. From the Build menu, select Check Syntax.

Command line syntax

--check

Description
With this option you can check the source code for syntax errors, without
generating code. This saves time in developing your application.

The compiler reports any warnings and/or errors.

Example
To check for syntax errors, without generating code:
ctc --check test.c

Related information
Assembler option --check (Check syntax)

• • • • • • • •
 5-12 TriCore Reference Manual

--cse-all-addresses
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the C Compiler entry and select Miscellaneous.

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

Command line syntax

--cse-all-addresses

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
ctc --cse-all-addresses -Oc test.c

The compiler makes all addresses available for common subexpression

TOOL OPTIONS

evaluation.

Related information
Compiler option -Oc (Common subexpression elimination)
 Tool Options - Compiler 5-13

-D (--define)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the C Compiler entry and select Preprocessing.

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

field.

Use commas to separate multiple macro definitions.

Command line syntax

-Dmacro_name[=macro_definition]

--define=macro_name[=macro_definition]

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.

• • • • • • • •
 5-14 TriCore Reference Manual

Example
Consider the following C program with conditional code to compile a
demo program and a real program:
void main( void )
{
#if DEMO
demo_func(); /* compile for the demo program */
#else
real_func(); /* compile for the real program */
#endif
}

You can now use a macro definition to set the DEMO flag:
ctc -DDEMO test.c
ctc -DDEMO=1 test.c

ctc --define=DEMO test.c

ctc --define=DEMO=1 test.c

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.
ctc -D"MAX(A,B)=((A) > (B) ? (A) : (B))"

Related information
TOOL OPTIONS

Compiler option -U (Undefine macro)

Compiler option -f (Specify an option file)
 Tool Options - Compiler 5-15

--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.

A description of the selected message appears.

Command line syntax

--diag=[format:]{all | number[,number]... }

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

text The default is plain text

html Display explanation in HTML format
rtf Display explanation in RTF 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.

To create a file with the descriptions, you must redirect the output.

With the suboption all, the descriptions of all error messages are given. If
you want the description of one or more selected error messages, you can
specify the error message numbers, separated by commas.

With this option the compiler does not compile any files.

Example
To display an explanation of message number 282, enter:
ctc --diag=282

This results in the following message and explanation:

E282: unterminated comment

Make sure that all every comment starting with /* has

a matching */. Nested comments are not possible.

• • • • • • • •
 5-16 TriCore Reference Manual

To write an explanation of all errors and warnings in HTML format to file

cerrors.html , enter:

ctc --diag=html:all > cerrors.html

Related information
Section 5.8, C Compiler Error Messages, in Chapter Using the Compiler of
the User's Manual.
TOOL OPTIONS
 Tool Options - Compiler 5-17

-E (--preprocess)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the C Compiler entry and select Preprocessing.

3. Enable the option Store the C compiler preprocess output

(<file>.pre).

Command line syntax

-E[flags]

--preprocess[=flags]

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

c/C (+/-comments) Keep comments

m/M (+/-make) Generate dependencies for make
p/P (+/-noline) Strip #line source position info

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 -Em the compiler will generate dependency lines that can be used
in a Makefile. The preprocessor output is discarded.

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 easier to read.

• • • • • • • •
 5-18 TriCore Reference Manual

Example
ctc -EcMP test.c -o test.pre

ctc --preprocess=+comments,-make,-noline test.c

--output=test.pre

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

Related information
-
TOOL OPTIONS
 Tool Options - Compiler 5-19

--error-file
EDE
-

Command line syntax

--error-file[=file]

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:
ctc --error-file=errors.err test.c

Related information
Compiler option --warnings-as-errors (Treat warnings as errors)

• • • • • • • •
 5-20 TriCore Reference Manual

-F (--no-double)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the C Compiler entry and select Language.

3. Enable the option Single precision floating-point only.

Command line syntax

-F

--no-double

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
ctc -F test.c

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

Related information
-
 Tool Options - Compiler 5-21

-f (--option-file)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

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:
• 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

-f file,...

--option-file=file,...

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.

• • • • • • • •
 5-22 TriCore Reference Manual

Format of an option file

• Multiple command line arguments on one line in the option file are
allowed.
• To include whitespace in an argument, surround the argument with
single or double quotes.
• If you want to use single quotes as part of the argument, surround the
argument by double quotes and vise versa:
"This has a single quote ' embedded"

'This has a double quote " embedded'

'This has a double quote " and \

a single quote '"' embedded"
• When a text line reaches its length limit, use a '\' to continue the line.
Whitespace between quotes is preserved.
"This is a continuation \
line"
-> "This is a continuation line"
• It is possible to nest command line files up to 25 levels.

Example
Suppose the file myoptions contains the following lines:
-Ctc11ib
-s
test.c
TOOL OPTIONS

Specify the option file to the compiler:

ctc -f myoptions

This is equivalent to the following command line:

ctc -Ctc11ib -s test.c

Related information
-
 Tool Options - Compiler 5-23

--fpu-present
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Processor entry and select Processor Definition.

3. In the Target processor list select (user defined TriCore-1 v1.3) or

(user defined TriCore-2).

4. Enable the option FPU present.

Command line syntax

--fpu-present

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.

If you choose a valid target processor (command line option -C (--cpu)),

this option is automatically set, based on the chosen target processor.

Example
To allow the use of floating-point unit (FPU) instructions in the assembly
code, enter:
ctc --fpu-present test.c

Related information
Compiler option --is-tricore2 (Tricore2 instructions allowed)

Compiler option -C (Use SFR definitions for CPU)

• • • • • • • •
 5-24 TriCore Reference Manual

-g (--debug-info)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

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

3. Enable the option Generate symbolic debug infomation

Command line syntax

-g

--debug-info

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
TOOL OPTIONS

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

ctc -g test.c

Related information
-
 Tool Options - Compiler 5-25

-H (--include-file)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

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

-Hfile,...

--include-file=file,...

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
ctc -Hstdio.h test1.c test2.c

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.5, How the Compiler Searches Include Files, in Chapter Using the
Compiler of the User's Manual.

• • • • • • • •
 5-26 TriCore Reference Manual

-I (--include-directory)
EDE
1. From the Project menu, select Directories...

The Directories dialog appears.

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

Command line syntax

-Ipath,...

--include-directory=path,...

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.
TOOL OPTIONS

4. The default directory $(PRODDIR)\include .

Example
Suppose that the C source file test.c contains the following lines:
#include <stdio.h>
#include "myinc.h"

You can call the compiler as follows:

ctc -Imyinclude test.c

First the compiler looks for the file stdio.h in the directory myinclude
relative to the current directory. If it was not found, the compiler searches
in the environment variable and then in the default include directory.
 Tool Options - Compiler 5-27

The compiler now looks for the file myinc.h in the directory where
test.c is located. If the file is not there the compiler searches in the
directory myinclude. If it was still not found, the compiler searches in the
environment variable and then in the default include directory.

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

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

Section 1.3.2, Configuring the Command Line Environment, in Chapter

Software Installation of the User's Manual.

• • • • • • • •
 5-28 TriCore Reference Manual

--indirect
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the C Compiler entry and select Code Generation.

3. Enable the option Call functions indirectly.

Command line syntax

--indirect

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

Example
ctc --indirect test.c

The compiler generates far calls for all functions.

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

Related information
Compiler option --indirect-runtime

See also section 3.9.3, Function Calling Modes: __indirect, in Chapter

TriCore C Language of the User's Manual.
 Tool Options - Compiler 5-29

--indirect-runtime
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the C Compiler entry and select Code Generation.

3. Enable the option Call run-time functions indirectly.

Command line syntax

--indirect-runtime

Description
With this option you tell the compiler to generate code for indirect calls to
run-time functions. Use this option if you locate the entire run-time library
in far memory.

Example
ctc --indirect-runtime test.c

The compiler generates far calls for all run-time functions.

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

Related information
Compiler option --indirect

See also section 3.9.3, Function Calling Modes: __indirect, in Chapter

TriCore C Language of the User's Manual.

• • • • • • • •
 5-30 TriCore Reference Manual

--inline
EDE
-

Command line syntax

--inline

Description
With this option you instruct the compiler to inline all functions, regardless
whether they have the keyword inline or not. This option has the same
effect as a #pragma inline at the start of the source file.

This option can be useful to increase the possibilities for code compaction
(option -Or).

Example
To inline all functions:
ctc --inline test.c

Related information
Compiler option -Or (Optimization: code compaction)
TOOL OPTIONS
 Tool Options - Compiler 5-31

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

Command line syntax

--inline-max-incr=percentage

--inline-max-size=threshold

Default
--inline-max-incr=25

--inline-max-size=10

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.

• • • • • • • •
 5-32 TriCore Reference Manual

Example
ctc --inline-max-incr=40 --inline-max-size=15 test.c

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 Manual.
TOOL OPTIONS
 Tool Options - Compiler 5-33

--integer-enumeration
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the C Compiler entry and select Language.

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

Command line syntax

--integer-enumeration

Description
With this option you tell the compiler to use (32-bit) integers for
enumerations. Without this option, the treats small enumerated types as a
smaller integer, a char or even a __bit type to reduce code size.

Example
To treat enumerated types always as 32-bit integer, enter:
ctc --integer-enumeration test.c

Related information
-

• • • • • • • •
 5-34 TriCore Reference Manual

--is-tricore2
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Processor entry and select Processor Definition.

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

4. Optionally enable or disable the options FPU present and MMU

present.

Command line syntax

--is-tricore2

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.

If you choose a valid target processor (command line option -C (--cpu)),

this option is automatically set, based on the chosen target processor.

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

ctc --is-tricore2 test.c

Related information
Compiler option --fpu-present (Use hardware floating-point
instructions)
Assembler option --mmu-present (Allow use of MMU instructions)

Compiler option -C (Use SFR definitions for CPU)

 Tool Options - Compiler 5-35

-k (--keep-output-files)
EDE
EDE always removes the .src file when errors occur during compilation.

Command line syntax

-k

--keep-output-files

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
ctc -k test.c

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 errors)

• • • • • • • •
 5-36 TriCore Reference Manual

--misrac
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

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

--misrac={all | number [-number],... }

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
ctc --misrac=9-13 test.c

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

Related information
See Chapter 10 MISRA C Rules for a list of all supported MISRA C rules.

Linker option --misra-c-report.

 Tool Options - Compiler 5-37

-N (--default-near-size)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the C Compiler entry and select Allocation.

3. Enable the option Default __near allocations for objects below

threshold and enter a threshold value.

Command line syntax

-N[threshold]

--default-near-size[=threshold]

Default
-N8

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, __a1 or __far sections.

The default threshold is eight bytes.

If you specify -N without a threshold value, all objects will be allocated

__near, including arrays and string constants.

Instead of this option you can also use #pragma default_near_size

in the C source.

Example
ctc -N12 test.c

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

sections.

• • • • • • • •
 5-38 TriCore Reference Manual

Related information
Compiler option -Y (maximum size in bytes for data elements that are
default located in __a1 sections)
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 Manual.
TOOL OPTIONS
 Tool Options - Compiler 5-39

-n (--stdout)
EDE
-

Command line syntax

-n

--stdout

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
ctc -n test.c

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

Related information
-

• • • • • • • •
 5-40 TriCore Reference Manual

--no-tasking-sfr
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the C Compiler entry and select Preprocessing.

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

Command line syntax

--no-tasking-sfr

Description
Normally, the compiler includes a special function register (SFR) file before
compiling. The compiler automatically selects the SFR file belonging to the
target you select on the Processor definition page of the Processor
options (compiler option -C).

With this option the compiler does not include the register file
regcpu.sfr as based on the selected target processor.

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

Example
ctc -Ctc11ib --no-tasking-sfr test.c
TOOL OPTIONS

The register file regtc11ib.sfr is not included.

Related information
Compiler option -C (Use SFR definitions for CPU)
 Tool Options - Compiler 5-41

-O (--optimize)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the C Compiler entry and select Optimization.

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

Command line syntax

-O[flags]
--optimize[=flags]

You can set the following flags:

a/A (+/-coalesce) Coalescer: remove unnecessary moves

c/C (+/-cse) Common subexpression elimination
e/E (+/-expression) Expression simplification
f/F (+/-flow) Control flow optimization and
code reordering
g/G (+/-glo) Generic assembly optimizations
i/I (+/-inline) Function inlining
k/K (+/-schedule) Instruction scheduler
l/L (+/-loop) Loop transformations
m/M (+/-simd) Perform SIMD optimizations
o/O (+/-forward) Forward store
p/P (+/-propagate) Constant propagation
s/S (+/-subscript) Subscript strength reduction
v/V (+/-ifconvert) Convert IF statements using predicates
w/W (+/-pipeline) Software pipelining
y/Y (+/-peephole) Peephole optimizations

Use the following options for predefined sets of flags:

-O0 (--optimize=0) No optimization.

Alias for: -OACEFGIKLMOPSVWY

No optimizations are performed. The compiler tries to achieve a 1-to-1

resemblance between source code and produced code. Expressions are
evaluated in the same order as written in the source code, associative
and commutative properties are not used.

• • • • • • • •
 5-42 TriCore Reference Manual

-O1 (--optimize=1) Debug purpose optimization

Alias for: -OaCefgIKLMOPSVWy

Enables optimizations that do not affect the debug-ability of the source

code. Use this level when you are developing/debugging new source
code.

-O2 (--optimize=2) Release purpose optimization (default)

Alias for: -OacefgIklMopsvwy

Enables more optimizations to reduce code size and/or execution time.

The debugger can handle this code but the relation between source
code and generated instructions may be hard to understand. Use this
level for those modules that have already been debugged. This is the
default optimization level.

-O3 (--optimize=3) Aggressive optimization

Alias for: -Oacefgiklmopsvwy

Enables aggressive global optimization techniques. Although in theory

debugging is still possible, the relation between source code and
generated instructions is complex and hard to understand. Use this
level to compress your program into the system memory, or to
decrease execution time to meet your real-time requirements.

Default
-O2

Description
TOOL OPTIONS

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 -OacefgIklMopsvwy).

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).
 Tool Options - Compiler 5-43

Example
The following invocations are equivalent and result all in the default
medium optimization set:
ctc test.c

ctc -O2 test.c

ctc --optimize=2 test.c

ctc -O test.c
ctc --optimize test.c

ctc -OacefgIklpswy test.c

ctc --optimize=+coalesce,+cse,+expression,+flow,
+glo,-inline,+schedule,+loop,+propagate,
+subscript,+ifconvert,+pipeline,+peephole test.c

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 Manual.

• • • • • • • •
 5-44 TriCore Reference Manual

-o (--output)
EDE
-

Command line syntax

-ofile

--output=file

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
ctc -o output.src test.c
ctc --output=output.src test.c

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
TOOL OPTIONS

-
 Tool Options - Compiler 5-45

--object-comment
EDE
-

Command line syntax

--object-comment=comment

Description
With this option the compiler generates a .comment section at the end of
the assembly file. The section contains the comment specified with this
option. After assembling, this text is included in the .o object and .elf
files. Place the comment between double quotes.

Example
ctc --object-comment="Created by TASKING" test.c

The compiler creates the file test.src with a .comment section at the
end of the file. After assembling this file, the text "Created by TASKING" is
incorporated in the generated object file.

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

Related information
-

• • • • • • • •
 5-46 TriCore Reference Manual

-R (--rename-sections)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the C Compiler entry and select Miscellaneous.

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

Command line syntax

-R [name]

--rename-sections[=name]

Description
The compiler defaults to a section naming convention, using a prefix
indicating the section type, the module name and a symbol name:
section_type_pref.module_name.symbol_name

For example .text.module_name.symbol_name for code sections.

If a module must be loaded at a fixed address or if a data section needs a

special place in memory, you can use the -R option to generate a different
section name (section_type_pref.name where name replaces the part
module_name.symbol_name). You can now use the new unique section
TOOL OPTIONS

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_pref.NEW instead of the
default section name section_type_pref.module_name.symbol_name, enter:
ctc -RNEW test.c

To generate the section name section_type_pref instead of the default

section name section_type_pref.module_name.symbol_name, enter:

ctc -R" " test.c (note the space between the quotes)
 Tool Options - Compiler 5-47

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

• • • • • • • •
 5-48 TriCore Reference Manual

-s (--source)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

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

-s

--source

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
ctc -s test.c

The output file test.src contains the original C source lines as

comments, besides the generated assembly code.
TOOL OPTIONS

Related information
-
 Tool Options - Compiler 5-49

--section-per-data-object
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the C Compiler entry and select Code Generation.

3. Enable the option Generate a section for each data object.

Command line syntax

--section-per-data-object

Description
Normally the compiler generates one section for each data type in a
module (such as .data, .rodata, .bss, .zdata, ...).

With this option you force the compiler to generate a separate section for
each data object. This provides more control about allocation during the
linking process.

Example
ctc --section-per-data-object test.c

For each data object in test.c the compiler generates a separate section.

Related information
-

• • • • • • • •
 5-50 TriCore Reference Manual

--silicon-bug
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Processor entry and select Bypasses.

3. Select the bypasses you want to enable.

Command line syntax

--silicon-bug=arg,...

You can give one or more of the following arguments:

all-tc112 All TriCore 1 v1.2 (TC112) workarounds

all-tc113 All TriCore 1 v1.3 (TC113) workarounds

cor1 workaround for TC112 COR1 (#pragma TC112_COR1 )

cor4 workaround for TC112 COR4 (#pragma TC112_COR4 )
cor7 workaround for TC112 COR7 (#pragma TC112_COR7 )
cor10 workaround for TC112 COR10 (#pragma TC112_COR10)
cor13 workaround for TC112 COR13 (#pragma TC112_COR13)
cor14 workaround for TC112 COR14 (#pragma TC112_COR14)
cor16 workaround for TC112 COR16 (#pragma TC112_COR16)
cor17 workaround for TC112 COR17 (#pragma TC112_COR17)
TOOL OPTIONS

cpu-tc013 workaround for CPU_TC.013 (#pragma CPU_TC013)

cpu-tc030 workaround for CPU_TC.030 (#pragma CPU_TC030)
cpu-tc031 workaround for CPU_TC.031 (#pragma CPU_TC031)
cpu-tc034 workaround for CPU_TC.034 (#pragma CPU_TC034)
cpu-tc048 workaround for CPU_TC.048 (#pragma CPU_TC048)
cpu-tc050 workaround for CPU_TC.050 (#pragma CPU_TC050)
cpu-tc060 workaround for CPU_TC.060 (#pragma CPU_TC060)
 Tool Options - Compiler 5-51

cpu5 workaround for TC113 CPU5 (#pragma TC113_CPU5 )

cpu9 workaround for TC113 CPU9 (#pragma TC113_CPU9 )
cpu11 workaround for TC113 CPU11 (#pragma TC113_CPU11)
cpu14 workaround for TC113 CPU14 (#pragma TC113_CPU14)
cpu15 workaround for TC113 CPU15 (#pragma TC113_CPU15)
cpu16 workaround for TC113 CPU16 (#pragma TC113_CPU16)
dmu1 workaround for TC113 DMU1 (#pragma TC113_DMU1)
lfi2 workaround for TC113 LFI2 (#pragma TC113_LFI2 )
lfi3 workaround for TC113 LFI3 (#pragma TC113_LFI3 )

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

Example
ctc --silicon-bug=cpu5,cpu9 test.c

The compiler uses workarounds for TC113 problems CPU5 and CPU9.

Related information
See Chapter 9, CPU Functional Problems, for more information about the
individual problems and workarounds.
#pragma CPU_functional_problem
#pragma TC112_functional_problem
#pragma TC113_functional_problem

• • • • • • • •
 5-52 TriCore Reference Manual

--static
EDE
-

Command line syntax

--static

Description
With this option, the compiler treats external definitions at file scope
(except for main) as if they were declared static. As a result, unused
functions will be eliminated, and the alias checking algorithm assumes that
objects with static storage cannot be referenced from functions outside the
current module.

This option only makes sense when you specify all modules of an
application on the command line.

Example
ctc --static module1.c module2.c module3.c

Related information
-
TOOL OPTIONS
 Tool Options - Compiler 5-53

--switch
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the C Compiler entry and select Code generation.

3. Select an Algorithm for switch statments.

Command line syntax

--switch=arg

You can give one of the following arguments:

auto Choose most optimal code

jumptab Generate jump tables
linear Use linear jump chain code
lookup Generate lookup tables

Default
--switch=auto

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
ctc --switch=jumptab test.c

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:
#pragma switch jumptab

• • • • • • • •
 5-54 TriCore Reference Manual

Related information
See also section 3.11, Switch Statement, in Chapter TriCore C Language of
the User's Manual.
TOOL OPTIONS
 Tool Options - Compiler 5-55

-t (--tradeoff)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

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

-t{0|1|2|3|4}

--tradeoff={0|1|2|3|4}

Default
-t2

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 balances speed and size while optimizing (-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:
ctc -t4 test.c
ctc --tradeoff=4 test.c

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)

• • • • • • • •
 5-56 TriCore Reference Manual

-U (--undefine)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the C Compiler entry and select Preprocessing.

3. Disable one or both predefined macros.

Command line syntax

-Umacro_name

--undefine=macro_name

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

#define __TASKING__ 1
#define __CTC__ compiler_version_nr

This option is for example useful to undefine predefined macros.

The following predefined ISO C standard macros cannot be undefined:

__FILE__ current source filename
TOOL OPTIONS

__LINE__ current source line number (int type)

__TIME__ hh:mm:ss
__DATE__ Mmm dd yyyy
__STDC__ level of ANSI standard

Example
To undefine the predefined macro __TASKING__:
ctc -U__TASKING__ test.c
ctc --undefine=__TASKING__ test.c
 Tool Options - Compiler 5-57

Related information
Compiler option -D (Define macro)

Section 3.8, Predefined Macros, in Chapter Using the Compiler of the User's
Manual.

• • • • • • • •
 5-58 TriCore Reference Manual

-u (--uchar)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the C Compiler entry and select Language.

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

signed.

Command line syntax

-u

--uchar

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:
ctc -u test.c
ctc --uchar test.c
TOOL OPTIONS

Related information
-
 Tool Options - Compiler 5-59

-V (--version)
EDE
-

Command line syntax

-V

--version

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

Example
ctc -v
ctc --version

The compiler does not compile any files but displays the following version
information:
TASKING TriCore VX-toolset C compiler vxx.yrz Build 000
Copyright 2002-2004 Altium BV Serial# 00000000

Related information
-

• • • • • • • •
 5-60 TriCore Reference Manual

-w (--no-warnings)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

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.

If you select Suppress specific warnings:

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

suppress.

Command line syntax

-w[nr]

--no-warnings[=nr]

Description
With this option you can suppresses all warning messages or specific
warning messages.
• If you do not specify this option, all warnings are reported.
• If you specify this option but without numbers, all warnings are
TOOL OPTIONS

suppressed.
• If you specify this option with a number, only the specified warning is
suppressed. You can specify the option -w multiple times.

Example
To suppress all warnings:
ctc test.c -w
ctc test.c --no-warnings

To suppress warnings 135 and 136:

ctc test.c -w135 -w136
ctc test.c --no-warnings=135 --no-warnings=136
 Tool Options - Compiler 5-61

Related information
Compiler option --warnings-as-errors (Treat warnings as errors)

• • • • • • • •
 5-62 TriCore Reference Manual

--warnings-as-errors
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the C Compiler entry and select Warnings.

3. Enable the option Treat warnings as errors.

Command line syntax

--warnings-as-errors

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

Example
ctc --warnings-as-errors test.c

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

Related information
Compiler option -w (suppress some or all warnings)
TOOL OPTIONS
 Tool Options - Compiler 5-63

-Y (--default-a1-size)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the C Compiler entry and select Allocation.

3. Enable the option Default __a1 allocations for objects below

threshold and enter a threshold value.

Command line syntax

-Z[threshold]

--default-a1-size[=threshold]

Default
-Y0

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 -Y threshold, the object is allocated in
__a1 memory. Larger objects, arrays and strings will be allocated __far.

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

Allocation in __a1 memory means that the object is addressed indirectly,

using A1 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_a1_size in the C
source.

• • • • • • • •
 5-64 TriCore Reference Manual

Example
ctc -Y12 test.c

Data elements smaller than or equal to 12 bytes are allocated in __a1

sections.

Related information
Compiler option -Z (max size (in bytes) for rodata elements located in
__a1 sections)

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 Manual.
TOOL OPTIONS
 Tool Options - Compiler 5-65

-Z (--default-a0-size)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the C Compiler entry and select Allocation.

3. Enable the option Default __a0 allocations for objects below

threshold and enter a threshold value.

Command line syntax

-Z[threshold]

--default-a0-size[=threshold]

Default
-Z0

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.

• • • • • • • •
 5-66 TriCore Reference Manual

Example
ctc -Z12 test.c

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

sections.

Related information
Compiler option -Y (max size (in bytes) for data elements located in __a0
sections)

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 Manual.
TOOL OPTIONS
 Tool Options - Assembler 5-67

5.2 ASSEMBLER OPTIONS

This section lists all assembler 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...

The Project Options dialog appears.

2. Expand the Assembler 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 -V displays version
header information 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:
astc -Lmx test.src
astc --list-format=+macro,+macro-expansion test.src

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

• • • • • • • •
 5-68 TriCore Reference Manual

-? (--help)
EDE
-

Command line syntax

-?

--help[=options]

Description
Displays an overview of all command line options. When you specify the
options argument, a list with option descriptions is displayed.

Example
The following invocations all display a list of the available command line
options:
astc -?
astc --help
astc

The following invocation displays extended information about all options:

astc --help=options

Related information
TOOL OPTIONS

-
 Tool Options - Assembler 5-69

-C (--cpu)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Processor entry and select Processor Definition.

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

Command line syntax

-Ccpu

--cpu=cpu

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

Based on the target processor the assembler automatically detects whether

a MMU or FPU-unit is present and whether the architecture is a TriCore2.
This means you do not have to specify the assembler options
--mmu-present, --fpu-present and --is-tricore2 explicitly when one
of the supported derivatives is selected.

The assembler automatically includes the register file regcpu.def, unless

you specify assembler option --no-tasking-sfr.

Example
In EDE, the target CPU has the following settings:
• Target processor: TC11IB
To define this on the command line:
astc -Ctc11ib test.src
astc --cpu=tc11ib test.src

The assembler assembles test.src for the TC11IB processor and

includes the register file regtc11ib.def . Furthermore the assembler
allows MMU instructions to be used.

• • • • • • • •
 5-70 TriCore Reference Manual

To avoid conflicts, make sure you specify the same target processor as you
did for the compiler.

Related information
Assembler option --no-tasking-sfr (Do not include .def file)

Compiler option -C (Use SFR definitions for CPU)

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

Section 6.4, Calling the Assembler, in Chapter Using the Assembler of the
User's Manual.
TOOL OPTIONS
 Tool Options - Assembler 5-71

-c (--case-insensitive)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Assembler entry and select Miscellaneous.

3. Disable the option Assemble case sensitive.

Command line syntax

-c

--case-insensitive

Description
With this option you tell the assembler not to distinguish between upper
and lower case characters. By default the assembler considers upper and
lower case characters in labels and user-defined symbols as different
characters. Note that instruction mnemonics, register names, directives and
controls are always treated case insensitive.

Disabling the option Assemble case sensitive in EDE is the same as

specifying the option -c on the command line.

Assembly source files that are generated by the compiler must always be
assembled case sensitive. When you are writing your own assembly code,
you may want to specify the case insensitive mode.

Example
To assemble case insensitive:
astc -c test.src
astc --case-insensitive test.src

The assembler considers upper and lower case characters as being the
same. So, for example, the label LabelName is the same label as
labelname.

Related information
Linker option --case-sensitive (Link case insensitive)

• • • • • • • •
 5-72 TriCore Reference Manual

--check
EDE
1. In the project window, select the file you want to check.

2. From the Build menu, select Check Syntax.

Command line syntax

--check

Description
With this option you can check the source code for syntax errors, without
generating code. This saves time in developing your application.

The assembler reports any warnings and/or errors.

Example
To check for syntax errors, without generating code:
astc --check test.src

Related information
Compiler option --check (Check syntax)
TOOL OPTIONS
 Tool Options - Assembler 5-73

-D (--define)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Assembler entry and select Preprocessing.

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

field.

Use commas to separate multiple macro definitions.

Command line syntax

-Dmacro_name[=macro_definition]

--define=macro_name[=macro_definition]

Description
With this option you can define a macro and specify it to the assembler
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 you can 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 assembler with the option -ffile.

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

This option has the same effect as defining symbols via the .SET, and
.EQU directives. (similar to #define in the C language). With the .MACRO
directive you can define more complex macros.

• • • • • • • •
 5-74 TriCore Reference Manual

Example
Consider the following C program with conditional code to compile a
demo program and a real program:
.IF DEMO == 1
... ; instructions for demo application
.ELSE
... ; instructions for the real application
.ENDIF

You can now use a macro definition to set the DEMO flag:
astc -DDEMO test.src
astc -DDEMO=1 test.src

astc --define=DEMO test.src

astc --define=DEMO=1 test.src

Note that all four invocations have the same effect.

Related information
Assembler option -f (Specify an option file)

Section 4.10.5, Conditional Assembly, in Chapter TriCore Assembly

Language of the User's Manual.
TOOL OPTIONS
 Tool Options - Assembler 5-75

--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.

A description of the selected message appears.

Command line syntax

--diag=[format:]{all | number[,number]... }

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

text The default is plain text

html Display explanation in HTML format
rtf Display explanation in RTF format

Description
With this option you can ask for an extended description of error
messages in the format you choose. The output is directed to stdout
(normally your screen) and in the format you specify.

To create a file with the descriptions, you must redirect the output.

With the suboption all, the descriptions of all error messages are given. If
you want the description of one or more selected error messages, you can
specify the error message numbers, separated by commas.

With this option the assembler does not assemble any files.

Example
To display an explanation of message number 241, enter:
astc --diag=241

This results in the following message and explanation:

W241: additional input files will be ignored

The assembler supports only a single input file. All

other input files are ignored.

• • • • • • • •
 5-76 TriCore Reference Manual

To write an explanation of all errors and warnings in HTML format to file

aserrors.html , enter:

astc --diag=html:all > aserrors.html

Related information
Section 6.7, Assembler Error Messages, in Chapter Using the Assembler of
the User's Manual.
TOOL OPTIONS
 Tool Options - Assembler 5-77

--emit-locals
EDE
-

Command line syntax

--emit-locals

Description
With this option the assembler also emits local symbols to the object file's
symbol table. Normally, only global symbols are emitted.

Example
To emit local symbols, enter:
astc --emit-locals test.src

Related information
-

• • • • • • • •
 5-78 TriCore Reference Manual

--error-file
EDE
-

Command line syntax

--error-file[=file]

Description
With this option the assembler 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 .ers.

Example
To write errors to errors.ers instead of stderr, enter:
astc --error-file=errors.ers test.src

Related information
Assembler option --warnings-as-errors (Treat warnings as errors)
TOOL OPTIONS
 Tool Options - Assembler 5-79

-f (--option-file)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Assembler entry and select Miscellaneous.

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

In EDE you can save your options in a file and restore them to call the
assembler 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 assembler options you have set in the
Project Options dialog. Only in extraordinary cases you may want to use
them in combination.

Command line syntax

-f file,...

--option-file=file,...

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 assembler.

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.

• • • • • • • •
 5-80 TriCore Reference Manual

Format of an option file

• Multiple command line arguments on one line in the option file are
allowed.
• To include whitespace in an argument, surround the argument with
single or double quotes.
• If you want to use single quotes as part of the argument, surround the
argument by double quotes and vise versa:
"This has a single quote ' embedded"

'This has a double quote " embedded'

'This has a double quote " and \

a single quote '"' embedded"

Note that adjacent strings are concatenated.

• When a text line reaches its length limit, use a '\' to continue the line.
Whitespace between quotes is preserved.
"This is a continuation \
line"
-> "This is a continuation line"
• It is possible to nest command line files up to 25 levels.

Example
Suppose the file myoptions contains the following lines:
-Ctc11ib
test.src
TOOL OPTIONS

Specify the option file to the assembler:

astc -f myoptions
astc --option-file=myoptions

This is equivalent to the following command line:

astc -Ctc11ib test.src

Related information
-
 Tool Options - Assembler 5-81

--fpu-present
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

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.

Command line syntax

--fpu-present

Description
With this option you can use single precision floating-point instructions in
the assembly code. When you select this option, the define __FPU__ is set
to 1. By default the define __FPU__ is set to 0.

Example
To allow the use of floating-point unit (FPU) instructions in the assembly
code, enter:
astc --fpu-present test.src

Related information
Assembler option -C (Select CPU)

• • • • • • • •
 5-82 TriCore Reference Manual

-g (--debug-info)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Assembler entry and select Debug Information.

3. Enable one or more debug options.

You cannot use Assembly source line information and Pass HLL
debug information simultaneously.

Command line syntax

-g[flag]

--debug-info[=flag]

You can set the following flags:

a/A (+/-asm) Assembly source line information

h/H (+/-hll) Pass HLL debug information
l/L (+/-local) Local symbols debug information
s/S (+/-smart) Smart debug information

Default
-gs
TOOL OPTIONS

Description
With this option you tell the assembler to generate debug information. If
you do not use this option or if you specify -g without any flags, the
default is -gs.

You cannot specify -gah. Either the assembler generates assembly source
line information, or it passes HLL debug information.

When you specify -gs, the assembler selects which flags to use. If high
level language information is available in the source file, the assembler
passes this information (same as -gAhL). If not, the assembler generates
assembly source line information and local symbols debug information
(same as -gaHl).
 Tool Options - Assembler 5-83

With -gAHLS the assembler does not generate any debug information.

Example
To disable symbolic debug information, turn all flags off:
astc -gAHLS test.src
astc --debug-info=-asm,-hll,-local,-smart test.src

To enable smart debugging, enter:

astc -gs test.src
astc --debug-info=+smart test.src

Related information
-

• • • • • • • •
 5-84 TriCore Reference Manual

-H (--include-file)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Assembler entry and select Preprocessing.

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

Command line syntax

-Hfile,...

--include-file=file,...

Description
With this option you include one extra file at the beginning of the
assembly source file, before other includes. This is the same as specifying
.INCLUDE 'file' at the beginning of your assembly sources.

Example
astc -Hmyinc.inc test1.src
astc --include-file=myinc.inc test1.src

The file myinc.inc is included at the beginning of test1.src before it

is assembled.
TOOL OPTIONS

Related information
Assembler option -I (Add directory to include file search path)

Section 6.5, How the Assembler Searches Include Files, in Chapter Using the
Assembler of the User's Manual.
 Tool Options - Assembler 5-85

-I (--include-directory)
EDE
1. From the Project menu, select Directories...

The Directories dialog appears.

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

Command line syntax

-Ipath,...

--include-directory=path,...

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 assembler searches for include files is:

1. The absolute pathname, if specified in the .INCLUDE directive. Or, if

no path or a relative path is specified, the same directory as the source
file.

2. The path that is specified with this option.

3. The path that is specified in the environment variable ASTCINC when

the product was installed.

4. The default include directory relative to the installation directory.

Example
Suppose that your assembly source file test.src contains the following
line:
.INCLUDE 'myinc.inc'

You can call the assembler as follows:

astc -Ic:\proj\include test.src
astc --include-directory=c:\proj\include test.src

• • • • • • • •
 5-86 TriCore Reference Manual

First the assembler looks in the directory where test.src is located for
the file myinc.inc. If it does not find the file, it looks in the directory
c:\proj\include for the file myinc.inc (this option).

Related information
Section 6.5, How the Assembler Searches Include Files, in Chapter Using the
Assembler of the User's Manual.

Section 1.3.2, Configuring the Command Line Environment, in Chapter

Software Installation of the User's Manual.

Assembler option -H (Include file at the start of the input files)

TOOL OPTIONS
 Tool Options - Assembler 5-87

-i (--symbol-scope)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Assembler entry and select Miscellaneous.

3. Select the default label mode: Local or Global.

Command line syntax

-i{g|l}

--symbol-scope={global|local}

Default
-il

Description
With this option you tell the assembler how to treat symbols that you have
not specified explicitly as global or local.

By default the assembler treats all symbols as local symbols unless you
have defined them explicitly as global.

Example
astc -ig test.src
astc --symbol-scope=global test.src

The assembler treats all symbols as global symbols unless they are defined
as local symbols in the assembly source file.

Related information
-

• • • • • • • •
 5-88 TriCore Reference Manual

--is-tricore2
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Processor entry and select Processor Definition.

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

Command line syntax

--is-tricore2

Description
With this option you can use TriCore 2 instructions in the assembly code.
When you select this option, the define __TC2__ is set to 1.

Example
To allow the use of TriCore 2 instructions in the assembly code, enter:
astc --is-tricore2 test.src

Related information
Assembler option -C (Select CPU)
TOOL OPTIONS
 Tool Options - Assembler 5-89

-k (--keep-output-files)
EDE
EDE always removes the .o file when errors occur during assembly.

Command line syntax

-k

--keep-output-files

Description
If an error occurs during assembly, the resulting .o file may be incomplete
or incorrect. With this option you keep the generated object file (.o)
when an error occurs.

By default the assembler removes the generated object file (.o) 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 use the generated object. For
example when you know that a particular error does not result in a
corrupt object file.

Example
astc -k test.src

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

Related information
Assembler option --warnings-as-errors (Treat warnings as errors)

• • • • • • • •
 5-90 TriCore Reference Manual

-L (--list-format)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Assembler entry and select List File.

3. Enable the options to include that information in the list file.

Command line syntax

-Lflags

--list-format=flags

You can set the following flags:

0 same as -LCDEGILMNPQRVWXY
1 same as -Lcdegilmnpqrvwxy

c/C (+/-control) Assembler controls

d/D (+/-section) Section directives
e/E (+/-symbol) Symbol definition directives
g/G (+/-generic-expansion) Generic instruction expansion
i/I (+/-generic) Generic instructions
l/L (+/-line) #line source lines
m/M (+/-macro) Macro definitions
TOOL OPTIONS

n/N (+/-empty-line) Empty source lines

p/P (+/-conditional) Conditional assembly
q/Q (+/-equate) Assembler .EQU and .SET directives
r/R (+/-relocations) Relocation characters ('r')
v/V (+/-equate-values) Assembler .EQU and .SET values
w/W (+/-wrap-lines) Wrapped source lines
x/X (+/-macro-expansion) Macro expansions
y/Y (+/-cycle-count) Cycle counts

Default
-LcDEGilMnPqrVWXy
 Tool Options - Assembler 5-91

Description
With this option you specify which information you want to include in the
list file. Use this option in combination with the option -l (--list-file).

If you do not specify this option, the assembler uses the default:
-LcDEGilMnPqrVWXy.

With option -tl, the assembler also writes section information to the list
file.

Example
astc -l -Ldm test.src
astc --list-file --list-format=+section,+macro
test.src

The assembler generates a list file that includes all default information plus
section directives and macro definitions.

Related information
Assembler option -l (Generate list file)
Assembler option -tl (Display section information in list file)

Linker option -M (Generate map file)

Section 6.1, Assembler List File Format, in Chapter List File Formats.

• • • • • • • •
 5-92 TriCore Reference Manual

-l (--list-file)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Assembler entry and select List File.

3. Enable the option Generate list file.

Command line syntax

-l

--list-file

Description
With this option you tell the assembler to generate a list file. A list file
shows the generated object code and the relative addresses. Note that the
assembler generates a relocatable object file with relative addresses.

Example
To generate a list file with the name test.lst, enter:
astc -l test.src
astc --list-file test.src
TOOL OPTIONS

Related information
Assembler option -L (List file formatting options)

Linker option -M (Generate map file)

Section 6.1, Assembler List File Format, in Chapter List File Formats.
 Tool Options - Assembler 5-93

-m (--preprocessor-type)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Assembler entry and select Preprocessing.

3. Select No preprocessor or the TASKING preprocessor.

Command line syntax

-m{n|t}

--preprocessor-type={none|tasking}

Default
-mt

Description
With this option you select the preprocessor that the assembler will use.
By default, the assembler uses the TASKING preprocessor.

When the assembly source file does not contain any preprocessor
symbols, you can specify the assembler not to use a preprocessor.

Example
astc test.src
astc -mt test.src
astc --preprocessor=tasking test.src

These invocations have the same effect: the assembler preprocesses the
file test.src with the TASKING preprocessor.

Related information
-

• • • • • • • •
 5-94 TriCore Reference Manual

--mmu-present
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Processor entry and select Processor Definition.

3. In the Target processor list select (user defined TriCore-1 v1.3) or

(user defined TriCore-2).

4. Enable the option MMU present.

This option is only available (and relevant) for specific target processors.
See option -C (--cpu) to select a target processor.

Command line syntax

--mmu-present

Description
With this option you can use memory management instructions in the
assembly code. When you select this option, the define __MMU__ is set to
1.

Example
To allow the use of memory management unit (MMU) instructions in the
TOOL OPTIONS

assembly code, enter:

astc --mmu-present test.src

Related information
Assembler option -C (Select CPU)
 Tool Options - Assembler 5-95

--no-tasking-sfr
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Assembler entry and select Preprocessing.

3. Disable the option Include '.def' file.

Command line syntax

--no-tasking-sfr

Description
Normally, the assembler includes a special function register (SFR) file
before compiling. The assembler automatically selects the SFR file
belonging to the target you select on the Processor definition page of
the Processor options (assembler option -C).

With this option the assembler does not include the register file
regcpu.def as based on the selected target processor.

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

Example
astc -Ctc11ib --no-tasking-sfr test.src

The register file regtc11ib.def is not included, but the assembler allows
the use of MMU instructions due to -C.

Related information
Assembler option -C (Select CPU)

• • • • • • • •
 5-96 TriCore Reference Manual

-O (--optimize)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Assembler entry and select Optimization.

3. Enable or disable the optimization suboptions.

Command line syntax

-Oflags

--optimize=flags

You can set the following flags:

g/G (+/-generics) Allow generic instructions

s/S (+/-instr-size) Optimize instruction size

Default
-Ogs

Description
With this option you can control the level of optimization. If you do not
use this option, -Ogs is the default.
TOOL OPTIONS

Example
The following invocations are equivalent and result all in the default
optimizations:
astc test.src
astc -Ogs test.src
astc --optimize=+generics,+instr-size test.src

Related information
Section 6.3, Assembler Optimizations, in Chapter Using the Assembler of the
User's Manual.
 Tool Options - Assembler 5-97

-o (--output)
EDE
-

Command line syntax

-ofile

--output=file

Description
With this option you can specify another filename for the output file of the
assembler. Without this option, the basename of the assembly source file is
used with extension .o.

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

Example
astc -o relobj.o asm.src
astc --output=relobj.o asm.src

The assembler creates the file relobj.o for the assembled file asm.src.

Without the option -o, like EDE, the assembler uses the name of the input
file and creates asm.o.

Related information
-

• • • • • • • •
 5-98 TriCore Reference Manual

--silicon-bug
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Processor entry and select Bypasses.

3. Select the CPU functional problems you want to check for.

Command line syntax

--silicon-bug=arg,...

You can give one or more of the following arguments:

all-tc112 All TriCore 1 v1.2 (TC112) checks:

alias for cor1, cor4, cor6,
cor7, cor10, cor13, cor15, cor16, cor17,
cpu-tc013, cpu-tc030, cpu-tc031, cpu-tc034,
cpu-tc048, cpu-tc050, cpu-tc060

all-tc113 All TriCore 1 v1.3 (TC113) checks:

alias for pmu1, pmu3, cpu9,
cpu11, cpu13, cpu14, cpu15, cpu16,
dmu1,lfi2, lfi3, cpu-tc060

cor1 check for TC112 COR1

TOOL OPTIONS

cor4 check for TC112 COR4

cor6 check for TC112 COR6
cor7 check for TC112 COR7
cor10 check for TC112 COR10
cor13 check for TC112 COR13
cor15 workaround for TC112 COR15
cor16 workaround for TC112 COR16
cor17 check for TC112 COR17
 Tool Options - Assembler 5-99

cpu-tc013 check for CPU TC013

cpu-tc030 check for CPU TC030
cpu-tc031 check for CPU TC031
cpu-tc034 check for CPU TC034
cpu-tc048 check for CPU TC048
cpu-tc050 check for CPU TC050
cpu-tc060 check for CPU TC060

cpu9 check for TC113 CPU9

cpu11 check for TC113 CPU11
cpu13 workaround for TC113 CPU13
cpu14 check for TC113 CPU14
cpu15 check for TC113 CPU15
cpu16 check for TC113 CPU16
dmu1 check for TC113 DMU1
lfi2 check for TC113 LFI2
lfi3 check for TC113 LFI3
pmu1 workaround for TC113 PMU1
pmu3 workaround for TC113 PMU3

Description
With this option you tell the assembler to check for some CPU functional
problems. The assembles gives a warning when the specified problem is
present.

Example
astc --silicon-bug=cpu5,cpu9 test.src

The assembler checks for TC113 problems CPU5 and CPU9 and gives a
warning when the problem is present.

Related information
See Chapter 9, CPU Functional Problems, for more information about the
individual problems.

• • • • • • • •
 5-100 TriCore Reference Manual

-t (--section-info)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Assembler entry and select List File.

3. Enable the option Generate list file.

4. Enable the option Display section information.

EDE always writes the section information to the list file.

Command line syntax

-tflags

--section-info=flags

You can set the following flags:

c/C (+/-console) Display section information on stdout.

l/L (+/-list) Write section information to the list file.

Description
With this option you tell the assembler to display section information. For
each section its memory space, size, total cycle counts and name is listed
TOOL OPTIONS

on stdout and/or in the list file.

The cycle count consists of two parts: the total accumulated count for the
section and the total accumulated count for all repeated instructions. In the
case of nested loops it is possible that the total supersedes the section
total.

With -tl, the assembler writes the section information to the list file. You
must specify this option in combination with the option -l (generate list
file).
 Tool Options - Assembler 5-101

Example
astc -l -tcl test.src
astc -l --section-info=+console,+list test.src

The assembler generates a list file and writes the section information to
this file. The section information is also displayed on stdout.
Section summary:

REL 4 .zbss_clr_test1
REL 46 .text_test1
REL 4 .zdata_rom_test1

Related information
Assembler option -l (Generate list file)

• • • • • • • •
 5-102 TriCore Reference Manual

-V (--version)
EDE
-

Command line syntax

-V

--version

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

Example
astc -V
astc --version

The assembler does not assemble any files but displays the following
version information:
TASKING TriCore VX-toolset Assembler vxx.yrz Build nnn
Copyright years Altium BV Serial# 00000000

Related information
-
TOOL OPTIONS
 Tool Options - Assembler 5-103

-w (--no-warnings)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Assembler entry and select Warnings.

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

warnings, or Suppress specific warnings.

If you select Suppress specific warnings:

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

suppress.

Command line syntax

-w[nr,...]

--no-warnings[=nr,...]

Description
With this option you can suppresses all warning messages or specific
warning messages.
• If you do not specify this option, all warnings are reported.
• If you specify this option but without numbers, all warnings are
suppressed.
• If you specify this option with a number, only the specified warning is
suppressed. You can specify the option -w multiple times.

Example
To suppress all warnings:
astc -w test.src
astc --no-warnings test.src

To suppress warnings 135 and 136:

astc -w135,136 test.src
astc --no-warnings=135,136 test.src

• • • • • • • •
 5-104 TriCore Reference Manual

Related information
Assembler option --warnings-as-errors (Treat warnings as errors)
TOOL OPTIONS
 Tool Options - Assembler 5-105

--warnings-as-errors
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Assembler entry and select Warnings.

3. Enable the option Treat warnings as errors.

Command line syntax

--warnings-as-errors

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

Example
astc --warnings-as-errors test.src

When a warning occurs, the assembler considers it as an error. No object

file is generated, unless you specify option -k (--keep-output-files).

Related information
Assembler option -w (suppress some or all warnings)

• • • • • • • •
 5-106 TriCore Reference Manual

5.3 LINKER 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. EDE invokes the linker
via the control program. Therefore, it uses the syntax of the control
program to pass options and files to the linker.

See section 5.4, Control Program Options.

If necessary, you can specify a command line option in EDE.

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

The Project Options dialog appears.

2. Expand the Linker entry and select Miscellaneous.

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

field.

Because EDE uses the control program, EDE automatically precedes the
option with -Wl to pass the option via the control program directly to the
linker.

For example, if you enter the option -DDEMO in the Additional

options field, EDE generates the option -Wl-DDEMO for the control
program which tells the control program to pass the option -DDEMO to
the linker.
TOOL OPTIONS

Be aware that some options are not useful in EDE or just will not have any
effect. For example, the option -k keeps files after an error occurred.
When you specify this option in EDE, it will have no effect because EDE
always removes the output file after an error had occurred.

Short and long option names

Options can 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.
 Tool Options - Linker 5-107

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:
ltc -mfkl test.o
ltc --map-file-format=+files,+link,+locate test.o

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

• • • • • • • •
 5-108 TriCore Reference Manual

-? (--help)
EDE
-

Command line syntax

-?
--help

Description
Displays an overview of all command line options.

Example
The following invocations all display a list of the available command line
options:
ltc -?
ltc --help
ltc

Related information
-
TOOL OPTIONS
 Tool Options - Linker 5-109

-c (--chip-output)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Linker entry and select Output Format.

3. Enable one or more output formats.

4. Enable the option Create file for each memory chip.

For some output formats you can specify a number of suboptions.

Command line syntax

-c[basename]:format[:addr_size],...

--chip-output=[basename]:format[:addr_size],...

You can specify the following formats:

IHEX Intel Hex

SREC Motorola S-records

The addr_size specifies the size of the addresses in bytes (record length).
For Intel Hex you can use the values: 1, 2 and 4 (default). For Motorola S
you can specify: 2 (S1 records), 3 (S2 records, default) or 4 bytes (S3
records).

Description
With this option you specify the Intel Hex or Motorola S-record output
format for loading into a PROM-programmer. The linker generates a file
for each ROM memory defined in the LSL file, where sections are located:
memory memname
{ type=rom; }

The name of the file is the name of the EDE project or, on the command
line, the name of the memory space that was emitted with extension .hex
or .sre. Optionally you can specify a basename which prepends the
generated file name.

• • • • • • • •
 5-110 TriCore Reference Manual

Examples
To generate Intel Hex output files for each defined memory, enter the
following on the command line:
ltc -cmyfile:IHEX test1.o
ltc --chip-output=myfile:IHEX test1.o

This generates the file myfile_memspace.hex.

Related information
Linker option -o (output file),
Section 7.2, Motorola S-Record Format,
Section 7.3, Intel Hex Record Format, in Chapter Object File Formats.
TOOL OPTIONS
 Tool Options - Linker 5-111

--case-insensitive
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Linker entry and select Miscellaneous.

3. Disable the option Link case sensitive.

Command line syntax

--case-insensitive

Description
With this option you tell the linker not to distinguish between upper and
lower case characters. By default the linker considers upper and lower
case characters as different characters.

Disabling the option Link case sensitive in EDE is the same as specifying
the option --case-insensitive on the command line.

Assembly source files that are generated by the compiler must always be
assembled and thus linked case sensitive. When you have written your
own assembly code and specified to assemble it case insensitive, you must
also link the .o file case insensitive.

Example
To link case insensitive:
ltc --case-insensitive test.o

The linker considers upper and lower case characters as being the same.
So, for example, the label LabelName is considered the same label as
labelname.

Related information
Assembler option -c (Assemble case insensitive)

• • • • • • • •
 5-112 TriCore Reference Manual

-D (--define)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog box appears.

2. Expand the Linker entry and select Miscellaneous.

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

Command line syntax

-Dmacro_name[=macro_definition]

--define=macro_name[=macro_definition]

Description
With this option you can define a macro and specify it to the linker
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: you can 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 linker with the option -ffile.

Define macro to the preprocessor, as in #define. Any number of symbols

can be defined. The definition can be tested by the preprocessor with #if,
TOOL OPTIONS

#ifdef and #ifndef, for conditional locating.

Example
To define the RESET vector, interrupt table start address and trap table start
address which is used in the linker script file tc1v1_3.lsl, enter:
ltc test.o -otest.elf -dtc1v1_3.lsl -DRESET=0xa0000000
-DINTTAB=0xa00f0000 --define=TRAPTAB=0xa00f2000

Related information
Linker option -f (Name of invocation file)
 Tool Options - Linker 5-113

-d (--lsl-file)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Linker entry and select Script File.

3. Select Use project specific memory and section LSL file and specify
a name.

Command line syntax

-dfile
--lsl-file=file

Description
With this option you specify a linker script file to the linker. If you do not
specify this option, the linker uses a default script file. You can specify the
existing file target.lsl or the name of a manually created linker script
file. You can use this option multiple times. The linker processes the LSL
files in the order in which they appear on the command line.

The linker script file contains vital information about the core for the
locating phase of the linker. A linker script file is coded in LSL and
contains the following types of information:
• the architecture definition describes the core's hardware architecture.
• the memory definition describes the physical memory in the system.
• the section layout definition describes how to locate sections in
memory.

Example
To read linker script file information from file tc1v1_3.lsl:
ltc -dtc1v1_3.lsl test.o
ltc --lsl-file=tc1v1_3.lsl test.o

• • • • • • • •
 5-114 TriCore Reference Manual

Related information
Linker option --lsl-check (Check LSL file(s) and exit)

Section 7.7, Controlling the Linker with a Script in Chapter Linker of the
User's Manual.
TOOL OPTIONS
 Tool Options - Linker 5-115

--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.

A description of the selected message appears.

Command line syntax

--diag=[format:]{all | number[,number]... }

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

text The default is plain text

html Display explanation in HTML format
rtf Display explanation in RTF format

Description
With this option you can ask for an extended description of error
messages in the format you choose. The output is directed to stdout
(normally your screen) and in the format you specify.

To create a file with the descriptions, you must redirect the output.

With the suboption all, the descriptions of all error messages are given. If
you want the description of one or more selected error messages, you can
specify the error message numbers, separated by commas.

With this option the linker does not link any files.

Example
To display an explanation of message number 106, enter:
ltc --diag=106

This results in the following message and explanation:

E106: unresolved external: message

The linker could not resolve all external symbols. This is an

error when the incremental linking option is disabled. The
<message> indicates the symbol that is unresolved.

• • • • • • • •
 5-116 TriCore Reference Manual

To write an explanation of all errors and warnings in HTML format to file

lerrors.html , enter:

ltc --diag=html:all > lerrors.html

Related information
Section 7.10, Linker Error Messages, in Chapter Using the Linker of the
User's Manual.
TOOL OPTIONS
 Tool Options - Linker 5-117

-e (--extern)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Linker entry and select Miscellaneous.

3. Add the option -e in the Additional options field.

Command line syntax

-e symbol
--extern=symbol

Description
With this option you force the linker to consider the given symbol as an
undefined reference. The linker tries to resolve this symbol by extracting
the corresponding symbol definition from a library. If the symbol is
defined in an object file, this option has no influence on the link process.

Suppose you are linking from a library. Because the library itself already
has been compiled and assembled, the linker does not find any
unresolved symbols. Hence, the linker will not extract any module from
the library. When you force a symbol to be undefined, the linker extracts
those modules that contain the symbol.

This option is, for example, useful if the startup code is part of a library.
Because your own application does not refer to the startup code, you can
force the startup code to be extracted by specifying the symbol _START as
an unresolved external.

Example:
Consider the following invocation:
ltc mylib.a

Nothing is linked and no output file will be produced, because there are
no unresolved symbols when the linker searches through mylib.a.
ltc -e _START mylib.a
ltc --extern=_START mylib.a

• • • • • • • •
 5-118 TriCore Reference Manual

In this case the linker searches for the symbol _START in the library and
(if found) extracts the object that contains _START, the startup code. If this
module contains new unresolved symbols, the linker looks again in
mylib.a. This process repeats until no new unresolved symbols are
found.

Related information
Section 7.4.1, Specifying Libraries to the Linker, in Chapter Using the Linker
of the User's Manual.
TOOL OPTIONS
 Tool Options - Linker 5-119

--error-file
EDE
-

Command line syntax

--error-file[=file]

Description
With this option the linker redirects error messages to a file.

If you do not specify a filename, the error file is ltc.elk.

Example
ltc --error-file=my.elk test.o

The linker writes error messages to the file my.elk instead of stderr.

Related information
Linker option --warnings-as-errors (Treat warnings as errors)

• • • • • • • •
 5-120 TriCore Reference Manual

-f (--option-file)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Linker entry and select Miscellaneous.

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

In EDE you can save your options in a file and restore them to call the
linker 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 linker options you have set in the
Project Options dialog. Only in extraordinary cases you may want to use
them in combination.

Command line syntax

-f file,...
--option-file=file,...

Description
Instead of typing all options on the command line, you can create an
TOOL OPTIONS

option file which contains all options and files you want to specify. With
this option you specify the option file to the linker.

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

• Multiple command line arguments on one line in the option file are
allowed.
• To include whitespace in an argument, surround the argument with
single or double quotes.
• If you want to use single quotes as part of the argument, surround the
argument by double quotes and vise versa:
 Tool Options - Linker 5-121

"This has a single quote ' embedded"

'This has a double quote " embedded'

'This has a double quote " and \

a single quote '"' embedded"

Note that adjacent strings are concatenated.

• When a text line reaches its length limit, use a '\' to continue the line.
Whitespace between quotes is preserved.
"This is a continuation \
line"
-> "This is a continuation line"
• It is possible to nest command line files up to 25 levels.

Example
Suppose the file myoptions contains the following lines:

-Mmymap (generate a map file)

test.o (input file)
-Lc:\mylibs (additional search path for system libraries)

Specify the option file to the linker:

ltc -f myoptions
ltc --option-file=myoptions

This is equivalent to the following command line:

ltc -Mmymap test.o -Lc:\mylibs

Related information
-

• • • • • • • •
 5-122 TriCore Reference Manual

--first-library first
EDE
-

Command line syntax

--first-library-first

Description
When the linker processes a library it searches for symbols that are
referenced by the objects and libraries processed so far. If the library
contains a definition for an unresolved reference the linker extracts the
object that contains the definition from the library.

By default the linker processes object files and libraries in the order in
which they appear on the command line. If you specify the option
--first-library-first the linker always tries to take the symbol definition
from the library that appears first on the command line before scanning
subsequent libraries.

This is for example useful when you are working with a newer version of
a library that partially overlaps the older version. Because they do not
contain exactly the same functions, you have to link them both. However,
when a function is present in both libraries, you may want the linker to
extract the most recent function.

With this option, you tell the linker to scan the libraries from left to right,
TOOL OPTIONS

and extract the symbol from the first library where the linker finds it.

Example:
ltc --first-library-first a.a test.o b.a

If the file test.o calls a function which is both present in a.a and b.a,
normally the function in b.a would be extracted. With this option the
linker first tries to extract the symbol from the first library a.a.

Related information
Linker option --no-rescan (Do not rescan libraries)
 Tool Options - Linker 5-123

-I (--include-directory)
EDE
-

Command line syntax

-Ipath,...

--include-directory=path,...

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

The order in which the linker searches for LSL include files is:

1. The pathname in the LSL file and the directory where the LSL files are
located (only for #include files that are enclosed in "")

2. The path that is specified with this option.

3. The default ..\include.lsl directory relative to the installation

directory.

Example
Suppose that the LSL file lslfile.lsl contains the following lines:
#include "mypart.lsl"

You can call the linker as follows:

ltc -Imyinclude -dlslfile.lsl test.o

ltc --include-directory=myinclude
--lsl-file=lslfile.lsl test.o

First the linker looks in the directory where lslfile.lsl is located for
the file mypart.lsl. If it does not find the file, it looks in myinclude
subdirectory relative to the current directory for the file mypart.lsl (this
option). Finally it looks in the directory ..\include.lsl .

Related information
Linker option -d (Linker script file)

• • • • • • • •
 5-124 TriCore Reference Manual

-i
(--user-provided-initialization-co
de)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Linker entry and select Miscellaneous.

3. Disable the option Use standard copy-table for initialization.

Command line syntax

-i

--user-provided-initialization-code

Description
It is possible to use your own initialization code, for example, to save
ROM space. With this option you tell the linker not to generate a copy
table for initialize/clear sections. Use linker labels in your source code to
access the positions of the sections when located.

If the linker detects references to the TASKING initialization code, an error

is emitted: it is either the TASKING initialization routine or your own, not
TOOL OPTIONS

both.

Note that the options --no-rom-copy and --non-romable, may vary

independently. The 'copytable-compression' optimization is automatically
disabled when you enable this option.

Example:
To link with your own startup code:
ltc -i test.o
ltc --user-provided-initialization-code test.o

Related information
-
 Tool Options - Linker 5-125

-k (--keep-output-files)
EDE
EDE always removes the output files when errors occurred.

Command line syntax

-k
--keep-output-files

Description
If an error occurs during linking, the resulting output file may be
incomplete or incorrect. With this option you keep the generated output
files when an error occurs.

By default the linker removes the generated output files 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 use the generated file. For example
when you know that the error(s) do not result in a corrupt output file, or
when you want to inspect the output file, or send it to Altium support.

Example
ltc -k test.o
ltc --keep-output-files test.o

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

Related information
-

• • • • • • • •
 5-126 TriCore Reference Manual

-L (--library-directory /
--ignore-default-library-path)
EDE
1. From the Project menu, select Directories...

The Directories dialog appears.

2. Add a pathname in the Library Files Path field.

3. In the Library Files Path field, add the pathnames of the directories
where the linker should look for library files.

If you enter multiple paths, separate them with a semicolon (;).

Command line syntax

-Lpath,...
--library-directory=path,...

-L
--ignore-default-library-path

Description
With this option you can specify the path(s) where your system libraries,
specified with the -l option, are located. If you want to specify multiple
paths, use the option -L for each separate path.
TOOL OPTIONS

The default path is $(PRODDIR)\lib .

If you specify only -L (without a pathname) or the long option

--ignore-default-library-path, the linker will not search the default
path and also not in the paths specified in the environment variable
LIBTC1V1_2, LIBTC1V1_3 or LIBTC2. So, the linker ignores steps 2, 3 and
4 as listed below.

The priority order in which the linker searches for system libraries
specified with the -l option is:

1. The path that is specified with the -L option.

2. The path that is specified in the environment variable LIBTC1V1_2,

LIBTC1V1_3 or LIBTC2 when the product was installed.
 Tool Options - Linker 5-127

3. The default directory $(PRODDIR)\lib .

4. The processor specific directory, for example $(PRODDIR)\lib\tc1 .

Example
Suppose you call the linker as follows:
ltc test.o -Lc:\mylibs -lc

First the linker looks in the directory c:\mylibs for library libc.a (this
option).

If it does not find the requested libraries, it looks in the directory that is set
with the environment variable LIBTC1V1_2, LIBTC1V1_3 or LIBTC2.

Then the linker looks in the default directory $(PRODDIR)\lib for

libraries.

Related information
Linker option -l (Link system library)

Section 7.4.2, How the Linker Searches Libraries, in Chapter Using the
Linker of the User's Manual.

Section 1.3.2, Configuring the Command Line Environment, in Chapter

Software Installation of the User's Manual.

• • • • • • • •
 5-128 TriCore Reference Manual

-l (--library)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Linker entry and select Libraries.

3. Enable the option Link default C libraries.

Command line syntax

-lname
--library=name

Description
With this option you tell the linker to search also in system library
libname.a, where name is a string. The linker first searches for system
libraries in any directories specified with -Lpath, then in the directories
specified with the environment variable LIBTC1V1_2, LIBTC1V1_3 or
LIBTC2, unless you used the option -L without a directory.

If you use the libc.a library, you must always link the libfp.a library
as well. Remember that the order of the specified libraries is important!

Example
To search in the system library libfp.a (floating-point library):
TOOL OPTIONS

ltc test.o mylib.a -lfp

The linker links the file test.o and first looks in mylib.a (in the current
directory only), then in the system library libfp.a to resolve unresolved
symbols.

Related information
Linker option -L (Additional search path for system libraries)

Section 7.4.1, Specifying Libraries to the Linker, in Chapter Using the Linker
of the User's Manual.
 Tool Options - Linker 5-129

--link-only
EDE
-

Command line syntax

--link-only

Description
With this option you suppress the locating phase. The linker stops after
linking. The linker complains if any unresolved references are left.

Example:
ltc --link-only hello.o

The linker checks for unresolved symbols and creates the file taks1.out.

Related information
Control program option -cl (Stop after linking)

• • • • • • • •
 5-130 TriCore Reference Manual

--lsl-check
EDE
-

Command line syntax

--lsl-check

Description
With this option the linker just checks the syntax of the LSL file(s) and
exits. No linking or locating is performed.

Example:
To check the LSL file(s) and exit:
ltc --lsl-check --lsl-file=mylslfile.lsl

Related information
Linker option -d (Linker script file)

Linker option --lsl-dump (Dump LSL info)

Chapter 8, Linker Script Language.

TOOL OPTIONS
 Tool Options - Linker 5-131

--lsl-dump
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Linker entry and select Script File.

3. Enable the option Dump processor and memory info from LSL
file.

Command line syntax

--lsl-dump[=file]

Description
With this option you tell the linker to dump the LSL part of the map file in
a separate file, independent of the -M (generate map file) option. If you
do not specify a filename, the file ltc.ldf is used.

Example
ltc --lsl-dump=mydump.ldf test.o

The linker dumps the processor and memory info from the LSL file in the
file mydump.ldf.

Related information
Linker option -m (Map file formatting options)

• • • • • • • •
 5-132 TriCore Reference Manual

-M (--map-file)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Linker entry and select Map File.

3. Enable the option Generate a map file (.map).

Command line syntax

-M[file]
--map-file[=file]

Description
With this option you tell the linker to generate a linker map file. If you do
not specify a filename, the linker uses the same basename as the output
file with the extension .map.

A linker map file is a text file that shows how the linker has mapped the
sections and symbols from the various object files (.o) to the linked object
file. A locate part shows the absolute position of each section. External
symbols are listed per space with their absolute address, both sorted on
symbol and sorted on address.

With the option -m (map file formatting) you can specify which parts you
TOOL OPTIONS

want to place in the map file.

Example
To generate a map file (test.map):
ltc -Mtest.map test.o
ltc --map-file=test.map test.o

The control program by default tells the linker to generate a map file.

Related information
Linker option -m (Map file formatting options)

Section 6.2, Linker Map File Format, in Chapter List File Formats.
 Tool Options - Linker 5-133

-m (--map-file-format)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Linker entry and select Map File.

3. Enable the options to include that information in the map file.

Command line syntax

-mflags

--map-file-format=flags

You can set the following flags:

0 same as -mcfkLMoQrSU (link info)

1 same as -mCfKlmoQRSU (locate info)
2 same as -mcfklmoqrsu (all info)

c/C (+/-callgraph) Call graph info

f/F (+/-files) Processed files info
k/K (+/-link) Link result info
l/L (+/-locate) Locate result info
m/M (+/-memory) Memory usage info
o/O (+/-overlay) Overlay info
q/Q (+/-statics) Module local symbols
r/R (+/-crossref) Cross references info
s/S (+/-lsl) Processor and memory info
u/U (+/-rules) Locate rules

Default
-mCfklMORSU

Description
With this option you specify which information you want to include in the
map file. Use this option in combination with the option -M
(--map-file). If you do not specify this option, the linker uses the
default: -mCfklMORSU

• • • • • • • •
 5-134 TriCore Reference Manual

Example
ltc -Mtest.map -mFr test.o
ltc --map-file=test.map
--map-file-format=+crossref,-files test.o

The linker generates the map file test.map that includes all default
information plus the cross reference part, but not the processed files part.

Related information
Linker option -M (Generate map file)

Section 6.2, Linker Map File Format, in Chapter List File Formats.
TOOL OPTIONS
 Tool Options - Linker 5-135

--misra-c-report
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

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

3. Select a MISRA C configuration.

4. Enable the option Produce a MISRA C report.

Command line syntax

--misra-c-report[=file]

Description
With this option you tell the linker to create a MISRA C Quality Assurance
report. This report lists the various modules in the project with the
respective MISRA C settings at the time of compilation. If you do not
specify a filename, the file name.mcr is used.

Example
ltc --misra-c-report test.o

The linker creates a MISRA C report file test.mcr.

Related information
Compiler option --misrac

• • • • • • • •
 5-136 TriCore Reference Manual

--munch
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Linker entry and select Miscellaneous.

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

Command line syntax

--munch

Description
With this option you tell the linker to activate the muncher in the
pre-locate phase.

The data sections are initialized when the application is downloaded. The
data sections are not re-initialized when the application is restarted.

Example
ltc --munch test.o

The linker activates the muncher in the pre-locate phase while linking the
file test.o.
TOOL OPTIONS

Related information
-
 Tool Options - Linker 5-137

-N (--no-rom-copy)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Linker entry and select Miscellaneous.

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

Command line syntax

-N
--no-rom-copy

Description
With this option the linker will not generate a ROM copy for data sections.
A copy table is generated and contains entries to clear BSS sections.
However, no entries to copy data sections from ROM to RAM are placed in
the copy table.

The data sections are initialized when the application is downloaded. The
data sections are not re-initialized when the application is restarted.

Example
ltc -N test.o
ltc --no-rom-copy test.o

The linker does not generate a copy table.

Related information
-

• • • • • • • •
 5-138 TriCore Reference Manual

--no-rescan
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Linker entry and select Libraries.

3. Disable the option Rescan libraries to solve unresolved externals.

Command line syntax

--no-rescan

Description
When the linker processes a library, it searches for symbol definitions that
are referenced by the objects and libraries processed so far. If the library
contains a definition for an unresolved reference, the linker extracts the
object that contains the definition from the library. The linker processes
object files and libraries in the order in which they appear on the
command line.

When all objects and libraries are processed the linker checks if there are
unresolved symbols left. If so, the default behavior of the linker is to
rescan all libraries in the order given on the command line. The linker
stops rescanning the libraries when all symbols are resolved, or when the
linker could not resolve any symbol(s) during the rescan of all libraries.
TOOL OPTIONS

Notice that resolving one symbol may introduce new unresolved symbols.

With this option, you tell the linker to scan the object files and libraries
only once. When the linker has not resolved all symbols after the first
scan, it reports which symbols are still unresolved. This option is useful if
you are building your own libraries. The libraries are most efficiently
organized if the linker needs only one pass to resolve all symbols.

Example:
To scan the libraries only once:
ltc --no-rescan test.o a.a b.a

The linker resolves all unresolved symbols while scanning the object files
and libraries and reports all remaining unresolved symbols after this scan.
 Tool Options - Linker 5-139

Related information
Linker option --first-library-first (Scan libraries in the specified order)

• • • • • • • •
 5-140 TriCore Reference Manual

--non-romable
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Linker entry and select Miscellaneous.

3. Add the option to the Additional options field.

Command line syntax

--non-romable

Description
With this option you tell the linker that the application is not romable. The
linker will locate all ROM sections in RAM. A copy table is generated and
is located in RAM. When the application is started, that data and BSS
sections are re-initialized.

Example
ltc --non-romable test.o

The linker locates all ROM sections in RAM.

Related information
TOOL OPTIONS

-
 Tool Options - Linker 5-141

-O (--optimize)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Linker entry and select Optimization.

3. Enable or disable the optimization suboptions.

Command line syntax

-Oflags

--optimize=flags

You can set the following flags:

c/C (+/-delete-unreferenced-code-sections)
Delete unreferenced code sections from the output file
(no effect on sources compiled with debug information)

d/D (+/-delete-unreferenced-data-sections)
Delete unreferenced data sections from the output file
(no effect on sources compiled with debug information)

l/L (+/-first-fit-decreasing)
Use a 'first fit decreasing' algorithm to locate
unrestricted sections in memory.

s/S (+/-delete-unreferenced-symbols)
Delete unreferenced symbols from the output file

t/T (+/-copytable-compression)
Locate (unrestricted) sections in such a way that
the size of the copy table is as small as possible.

x/X (+/-delete-duplicate-code)
Delete duplicate code from the output file

y/Y (+/-delete-duplicate-data)
Delete duplicate constant data from the output file

• • • • • • • •
 5-142 TriCore Reference Manual

Use the following options for predefined sets of flags:

-O0 (--optimize=0) No optimization.

Alias for: -OCDLSTXY

-O1 (--optimize=1) Normal optimization (default).

Alias for: -OCDLStXY

-O2 (--optimize=2) All optimizations.

Alias for: -Ocdlstxy

Default
-O1

Description
With this option you can control the level of optimization. If you do not
use this option, -OCDLStXY (-O1) is the default.

Example
The following invocations are equivalent and result all in the default
optimizations.
ltc test.o
ltc -O test.o
ltc -O1 test.o
ltc -OCDLStXY test.o

ltc --optimize test.o

ltc --optimize=1 test.o
TOOL OPTIONS

ltc --optimize=-delete-unreferenced-code-sections,
-delete-unreferenced-code-sections,
-first-fit-decreasing,+copytable-compression,
-delete-duplicate-code,-delete-duplicate-data test.o

Related information
Section 7.2.3, Linker Optimizations, in Chapter Using the Linker of the
User's Manual.
 Tool Options - Linker 5-143

-o (--output-file)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Linker entry and select Output Format.

3. Enable one or more output formats.

For some output formats you can specify a number of suboptions.

EDE and the control program name the output file always after the first
input file with the extension .elf.

Command line syntax

-o[filename][:format[:addr_size][,space_name]]...

--output=[filename][:format[:addr_size][,space_name]]...

You can specify the following formats:

ELF ELF/DWARF
IEEE IEEE-695
IHEX Intel Hex
SREC Motorola S-records

Description
By default, the linker generates an output file in ELF/DWARF format, with
the name task1.elf.

With this option you can specify an alternative filename, and an alternative
output format. The default output format is the format of the first input
file.

You can use the -o option multiple times. This useful to generate multiple
output formats or to link multiple address spaces. With the first occurrence
of the -o option you must specify the filename without extension. If you
do not specify a filename, or you do not specify the -o option at all, the
linker uses the default basename taskn.

• • • • • • • •
 5-144 TriCore Reference Manual

IHEX and SREC formats

If you specify the Intel Hex format or the Motorola S-records format, you
can use the argument addr_size to specify the size of addresses in bytes
(record length). For Intel Hex you can use the values: 1, 2, and 4
(default). For Motorola S-records you can specify: 2 (S1 records), 3 (S2
records, default) or 4 bytes (S3 records).

With the argument space_name you can specify the name of the address
space. The name of the output file will be filename with the extension
.hex or .sre and contains the specified space. (Remember to use the -o
option multiple times to link multiple address spaces.)

If you do not specify space_name, the default address space is emitted. In

this case the name of the output file will be filename_spacename with the
extension .hex or .sre.

Use option -c (--chip-output) to create Intel Hex or Motorola S-record

output files for each chip (suitable for loading into a PROM-programmer).

Example
To create the output file myfile.hex of the address space named
linear:

ltc test.o -omyfile.hex:IHEX:2,linear

ltc test.o --output-file=myfile.hex:IHEX:2,linear

Related information
Linker option -c (Generate an output file for each chip)
TOOL OPTIONS

Section 7.1, ELF/DWARF Object Format, in Chapter Object File Formats.

 Tool Options - Linker 5-145

-r (--incremental)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Linker entry and select Miscellaneous.

3. Add the option -r in the Additional options field.

Command line syntax

-r
--incremental

Description
Normally the linker links and locates the specified object files. With this
option you tell the linker only to link the specified files. The linker creates
a linker output file .out. You then can link this file again with other
object files until you have reached the final linker output file that is ready
for locating.

In the last pass, you call the linker without this option with the final linker
output file .out. The linker will now locate the file.

Example
In this example, the files test1.o, test2.o and test3.o are
incrementally linked:

ltc -r test1.o -otest.out (test1.o and test2.o are linked)

ltc -r test3.o test.out (test3.o is linked)

ltc test.out (test.out is located)

Related information
Section 7.5, Incremental Linking, in Chapter Using the Linker of the User's
Manual.

• • • • • • • •
 5-146 TriCore Reference Manual

-S (--strip-debug)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Linker entry and select Miscellaneous.

3. Enable the options to include that information in the map file.

4. Disable the option Include symbolic debug information.

Command line syntax

-S

--strip-debug

Description
With this option you specify not to include symbolic debug information in
the resulting output file.

Example
ltc -S test.o -otest.elf
ltc --strip-debug test.o --output=test.elf

The linker generates the object file test.elf without symbolic debug
TOOL OPTIONS

information.
 Tool Options - Linker 5-147

-V (--version)
EDE
-

Command line syntax

-V

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

Example
ltc -V
ltc --version

The linker does not link any files but displays the following version
information:
TASKING TriCore VX-toolset object linker vx.yrz Build 000
Copyright years Altium BV Serial# 00000000

Related information
-

• • • • • • • •
 5-148 TriCore Reference Manual

-v (--verbose)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Linker entry and select Miscellaneous.

3. Enable the option Print the name of each file as it is processed.

Command line syntax

-v

Description
With this option you put the linker in verbose mode. The linker prints the
filenames and the link passes while it processes the files. It also shows
which objects are extracted from libraries. With this option you can
monitor the current status of the linker.

Example
ltc test.o -lc -lfp -lrt -v

The linker links the file test.o and displays the steps it performs.
ltc I405: activating pre link phase
ltc I406: activating link phase
ltc I401: start linking task "task1"
TOOL OPTIONS

ltc I415: reading file "./test.o"

ltc I413: start processing library "/ctc/lib/tc1/libc.a"
ltc I416: reading file "cstart.o" from library "libc.a"
...
ltc I414: start rescanning libraries
...
ltc I407: activating post link phase
ltc I408: activating pre locate phase
ltc I409: activating locate phase
...
ltc I418: binding locator symbols
ltc I411: activating post locate phase
ltc I410: activating file producing phase
ltc I401: start producing files for task "task1"

Related information
-
 Tool Options - Linker 5-149

-w (--no-warnings)
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Linker entry and select Warnings.

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

warnings, or Suppress specific warnings.

If you select Suppress specific warnings:

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

suppress.

Command line syntax

-w[nr[,nr]...]
--no-warnings[=nr[,nr]...]

Description
With this option you can suppresses all warning messages or specific
warning messages.
• If you do not specify this option, all warnings are reported.
• If you specify this option but without numbers, all warnings are
suppressed.
• If you specify this option with a number, only the specified warnings
are suppressed. Separate multiple warnings by commas.

Example:
To suppress all warnings:
ltc -w test.o
ltc --no-warnings test.o

To suppress warnings 113 and 114:

ltc -w113,114 test.o
ltc --no-warnings=113,114 test.o

• • • • • • • •
 5-150 TriCore Reference Manual

Related information
Linker option --warnings-as-errors (Treat warnings as errors)
TOOL OPTIONS
 Tool Options - Linker 5-151

--warnings-as-errors
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Linker entry and select Warnings.

3. Enable the option Treat warnings as errors.

Command line syntax

--warnings-as-errors

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

When the linker detects an error, it tries to continue the link process and
reports other errors and warnings. However, the linker will exit with an
exit status not equal zero (!= 0) and will not produce any output files.

Example
ltc --warnings-as-errors test.o

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

Related information
Linker option -w (Suppress some or all warnings)

• • • • • • • •
 5-152 TriCore Reference Manual

5.4 CONTROL PROGRAM OPTIONS

The control program cctc facilitates the invocation of the various
components of the TriCore toolchain from a single command line. The
control program is a command line tool so there are no equivalent options
in EDE.

For the linker options in EDE, EDE invokes the linker via the control
program. Therefore, it uses the syntax of the control program to pass
options and files to the linker. See section 5.3, Linker Options, for an
overview of the EDE linker options and the corresponding command line
linker options.

Some options are interpreted by the control program itself; other options
are passed to those programs in the toolchain that accept the option.

Recognized input files

The control program recognizes the following input files:
• Files with a .cc, .cxx or .cpp suffix are interpreted as C++ source
programs and are passed to the C++ compiler.
• Files with a .c suffix are interpreted as C source programs and are
passed to the compiler.
• Files with a .asm suffix are interpreted as hand-written assembly
source files which have to be passed to the assembler.
• Files with a .src suffix are interpreted as compiled assembly source
files. They are directly passed to the assembler.
• Files with a .a or .elb suffix are interpreted as library files and are
TOOL OPTIONS

passed to the linker.

• Files with a .o suffix are interpreted as object files and are passed to
the linker.
• Files with a .out suffix are interpreted as linked object files and are
passed to the locating phase of the linker. The linker accepts only one
.out file in the invocation.
• An argument with a .lsl suffix is interpreted as a linker script file and
is passed to the linker.
Normally, the control program tries to compile, assemble, link and locate
all source files to absolute object files. There are however, options to
suppress the assembler, link or locate stage.
 Tool Options - Control Program 5-153

-? (--help)
Command line syntax
-?[options]

--help[=options]

Description
Displays an overview of all command line options. When you specify the
suboption options, you receive extended information.

Example
The following invocations all display a list of the available command line
options:
cctc -?
cctc

Related information
-

• • • • • • • •
 5-154 TriCore Reference Manual

-A (--language)
Command line syntax
-A[flags]

--language[=flags]

You can set the following flags:

p/P (+/-comments) Allow C++ style comments in ISO C90

x/X (+/-strings) Relaxed const check for string literals

Default
-Apx

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

-A (--language) is the equivalent of -APX and disables all language

extensions.

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.

With -Ax you tell the compiler not to check for assignments of a constant
string to a non-constant string pointer. With this option the following
TOOL OPTIONS

example does not produces a warning:

char *p;
void main( void ) { p = "hello"; }

Example
ctc -APx test.c
ctc --language=-comments,+strings test.c

The control program calls the compiler in such a way that it accepts
assignments of a constant string to a non-constant string pointer but
ignores C++ style comments.
 Tool Options - Control Program 5-155

Related information
Compiler option -A (Control language extensions)

• • • • • • • •
 5-156 TriCore Reference Manual

--address-size
Command line syntax
--address-size=addr_size

Description
If you specify IHEX or SREC with the control option --format, you can
additionally specify the record length and the address space to be emitted
in the output files.

With this option you can specify the size of addresses in bytes (record
length). For Intel Hex you can use the values: 1, 2, and 4 (default). For
Motorola S-records you can specify: 2 (S1 records), 3 (S2 records, default)
or 4 bytes (S3 records).

If you do not specify addr_size, the default address size is generated.

Example
To create the SREC file test.s with S1 records, type:
cctc --format=SREC --address-size=2

Related information
Control program option --format (Set linker output format)
Control program option --space (Set linker output space name)

Linker option -o (Specify an output object file)

TOOL OPTIONS
 Tool Options - Control Program 5-157

-C (--cpu)
Command line syntax
-Ccpu

Description
With this option you define the target processor for which you create your
application. Default the control program generates an object file for the
TC11IB.

Based on the specified target processor it is automatically detected

whether a MMU or FPU-unit is present and whether the architecture is a
TriCore2. This means you do not have to specify the assembler options
--mmu-present, --fpu-present and --is-tricore2 explicitly when one
of the supported derivatives is selected.

Based on the specified target processor the control program always

includes the correct register files, unless you specify control program
option --no-tasking-sfr.

Example
To generate the file test.elf for the TC11IB processor:
cctc -Ctc11ib test.c
cctc --cpu=tc11ib test.c

Related information
Compiler option -C (Use SFR definitions for CPU)

Assembler option -C (Select CPU)

Section 5.4, Calling the Compiler, in Chapter Using the Compiler of the
User's Manual.

• • • • • • • •
 5-158 TriCore Reference Manual

--case-insensitive
Command line syntax
--case-insensitive

Description
With this option you tell the control progam not to distinguish between
upper and lower case characters. By default upper and lower case
characters are considered as different characters. Note that in assembly
instruction mnemonics, register names, directives and controls are always
treated case insensitive.

Assembly source files that are generated by the compiler must always be
assembled and linked case sensitive. When you are writing your own
assembly code, you may want to specify the case insensitive mode.

Example
To create the file test.elf with case insensitive assembling and linking:
cctc -c test.c
cctc --case-insensitive test.c

The assembler and linker now consider upper and lower case characters
as being the same. So, for example, the label LabelName is the same label
as labelname.

Related information
TOOL OPTIONS

Assembler option --case-sensitive (Assemble case insensitive)

Linker option --case-sensitive (Link case insensitive)
 Tool Options - Control Program 5-159

-cc/-cs/-co/-cl
Command line syntax
-cc
--create=c

-cs
--create=assembly

-co
--create=object

-cl
--create=relocatable

Description
Normally the control program generates an absolute object file of the
specified output format from the file you supplied as input.

With this option you tell the control program to stop after a certain
number of phases.

-cc Stop after C++ files are compiled to intermediate C files (.ic)
-cs Stop after C files are compiled to assembly (.src)
-co Stop after the files are assembled to object files (.obj)
-cl Stop after the files are linked to a linker object file (.eln)

To generate the object file test.o:

cctc -c test.c
cctc --create=object test.c

The control program stops after the file is assembled. It does not link nor
locate the generated output.

Related information
-

• • • • • • • •
 5-160 TriCore Reference Manual

--check
Command line syntax
--check

Description
With this option you can check the source code for syntax errors, without
generating code. This saves time in developing your application.

The compiler/assembler reports any warnings and/or errors.

Example
To check for syntax errors, without generating code:
cctc --check test.c

Related information
Compiler option --check (Check syntax)

Assembler option --check (Check syntax)

TOOL OPTIONS
 Tool Options - Control Program 5-161

-D (--define)
Command line syntax
-Dmacro_name[=macro_definition]

--define=macro_name[=macro_definition]

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. On the command line, use
the option -D multiple times. If the command line exceeds the length limit
of the operating system, you can define the macros in an option file which
you then must specify to the control program with the option -f file.

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

The control program passes the option -D (--define) to the compiler and
the assembler.

Example
Consider the following C program with conditional code to compile a
demo program and a real program:
void main( void )
{
#if DEMO == 1
demo_func(); /* compile for the demo program */
#else
real_func(); /* compile for the real program */
#endif
}

You can now use a macro definition to set the DEMO flag. With the
control program this looks as follows:
cctc -DDEMO test.c
cctc -DDEMO=1 test.c

• • • • • • • •
 5-162 TriCore Reference Manual

cctc --define=DEMO test.c

cctc --define=DEMO=1 test.c

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.
cctc -D"MAX(A,B)=((A) > (B) ? (A) : (B))"
cctc --define="MAX(A,B)=((A) > (B) ? (A) : (B))"

Related information
Control program option -U (Undefine preprocessor macro)
Control program option -f (Read options from file)
TOOL OPTIONS
 Tool Options - Control Program 5-163

-d (--lsl-file)
Command line syntax
-dfile

--lsl-file=file

Description
A linker script file contains vital information about the core for the locating
phase of the linker. A linker script file is coded in LSL and contains the
following types of information:
• the architecture and derivative definition describe the core's hardware
architecture and its internal memory.
• the board specification describes the physical memory available in the
system.
• the section layout definition describes how to locate sections in
memory.
With this option you specify a linker script file via the control program to
the linker. If you do not specify this option, the linker does not use a
script file. You can specify the existing file tctarget.lsl or the name of
a manually written linker script file. You can use this option multiple
times. The linker processes the LSL files in the order in which they appear
on the command line.

Example
To read linker script file information from file mylslfile.lsl :
cctc -dmylslfile.lsl test.obj
cctc --lsl-file=mylslfile.lsl test.obj

Related information
Section 7.7, Controlling the Linker with a Script, in the User's Manual.

• • • • • • • •
 5-164 TriCore Reference Manual

--diag
Command line syntax
--diag=[format:]{all|nr,...]

Description
With this option you can ask for an extended description of error
messages in the format you choose. The output is directed to stdout
(normally your screen) and in the format you specify. You can specify the
following formats: html, rtf or text (default). To create a file with the
descriptions, you must redirect the output.

With the suboption all, the descriptions of all error messages are given. If
you want the description of one or more selected error messages, you can
specify the error message numbers, separated by commas.

With this option the control program does not process any files.

Example
To display an explanation of message number 103 , enter:
cctc --diag=103

This results in message 103 with explanation.

To write an explanation of all errors and warnings in HTML format to file

ccerrors.html , enter:
TOOL OPTIONS

cctc --diag=html:all > ccerrors.html

Related information
-
 Tool Options - Control Program 5-165

-E (--preprocess)
Command line syntax
-E[flags]

--preprocess=[flags]

You can set the following flags:

c/C (+/-comments) Keep comments

p/P (+/-noline) Strip #line source position info

Description
With this option you tell the control program to preprocess the C source.

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
cctc -EcP test.c -o test.pre
cctc --preprocess +comments,-noline test.c
--output=test.pre

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
-

• • • • • • • •
 5-166 TriCore Reference Manual

--error-file
Command line syntax
--error-file[=file]

Description
With this option the control program 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:
cctc --error-file=errors.err test.c

Related information
Control program option --warnings-as-errors (Warnings as errors)
TOOL OPTIONS
 Tool Options - Control Program 5-167

--exceptions
Command line syntax
--exceptions

Description
With this option you enable support for exception handling in the C++
compiler.

Example
To enable exception handling, enter:
cctc --exceptions test.cc

Related information
-

• • • • • • • •
 5-168 TriCore Reference Manual

-F (--no-double)
Command line syntax
-F
--no-double

Description
With this option you tell the control program 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
cctc -F test.c
cctc --no-double test.c

The file test.c is processed where variables of the type double are
treated as float in the compilation phase.

Related information
-
TOOL OPTIONS
 Tool Options - Control Program 5-169

-f (--option-file)
Command line syntax
-f file

--option-file=file

Description
Instead of typing all options on the command line, you can create a option
file which contains all options and file you want to specify. With this
option you specify the option file to the control program.

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

• Multiple command line arguments on one line in the option file are
allowed.
• To include whitespace in an argument, surround the argument with
single or double quotes.
• If you want to use single quotes as part of the argument, surround the
argument by double quotes and vise versa:
"This has a single quote ' embedded"

'This has a double quote " embedded'

'This has a double quote " and \

a single quote '"' embedded"

Note that adjacent strings are concatenated.

• When a text line reaches its length limit, use a '\' to continue the line.
Whitespace between quotes is preserved.
"This is a continuation \
line"
-> "This is a continuation line"
• It is possible to nest command line files up to 25 levels.

• • • • • • • •
 5-170 TriCore Reference Manual

Example
Suppose the file myoptions contains the following lines:
-g
-k
test.c

Specify the option file to the control program:

ctc -f myoptions
ctc --option-file=myoptions

This is equivalent to the following command line:

ctc -g -k test.c

Related information
-
TOOL OPTIONS
 Tool Options - Control Program 5-171

--force-c
Command line syntax
--force-c

Description
With this option you tell the control program to treat all .cc files as C files
instead of C++ files. This means that the control program does not call the
C++ compiler and forces the linker to link C libraries.

Example
cctc --force-c test.cc

The C++ file test.cc is considered to be a normal C file.

Related information
Control program option --force-c++ (Force C++ compilation and linking)

• • • • • • • •
 5-172 TriCore Reference Manual

--force-c++
Command line syntax
--force-c++

Description
With this option you tell the control program to treat all .c files as C++
files instead of C files. This means that the control program calls the C++
compiler prior to the C compiler and forces the linker to link C++ libraries.

Example
cctc --force-c++ test.c

The file test.c is considered to be a C++ file.

Related information
Control program option --force-c (Treat C++ files as C files)
TOOL OPTIONS
 Tool Options - Control Program 5-173

--force-munch
Command line syntax
--force-munch

Description
With this option you force the control program to activate the muncher in
the pre-locate phase.

Example
To force the muncher phase in the pre-locate phase, type:
cctc --force-munch test.cc

Related information
-

• • • • • • • •
 5-174 TriCore Reference Manual

--force-prelink
Command line syntax
--force-prelink

Description
With this option you force the control program to invoke the C++
pre-linker.

Example
cctc --force-prelink test.cc

The control program always invokes the C++ pre-linker when generating
test.elf.

Related information
-
TOOL OPTIONS
 Tool Options - Control Program 5-175

--format
Command line syntax
--format=format

You can specify the following formats:

ELF ELF/DWARF
IEEE IEEE-695
IHEX Intel Hex
SREC Motorola S-records

Description
With this option you specify the output format for the resulting (absolute)
object file. The default output format is ELF/DWARF, which can directly be
used by the CrossView Pro debugger.

If you choose IHEX or SREC, you can additionally specify the address size
of the chosen format (option --address-size) and the address space to
be emitted (option --space).

Example
To generate an IEEE output file:
cctc --format=IEEE test1.c test2.c --output=test.abs

Related information
Control program option --address-size (For linker IHEX./SREC files)
Control program option --space (Set linker output space name)

Linker option -o (output file)

Linker option -C (generate hex file)

Section 7.1, ELF/DWARF Object Format, in Chapter Object File Formats.

• • • • • • • •
 5-176 TriCore Reference Manual

--fp-trap
Command line syntax
--fp-trap

Description
Default the control program uses the non-trapping floating-point library
(libfp.a). With this option you tell the control program to use the
trapping floating-point library (libfpt.a).

If you use the trapping floating-point library, exceptional floating-point

cases are intercepted and can be handled separately by an application
defined exception handler. Using this library decreases the execution
speed of your application.

Example
cctc --fp-trap test.c

Link the trapping floating-point library when generating the object file
test.elf.

Related information
-
TOOL OPTIONS
 Tool Options - Control Program 5-177

--fpu-present
Command line syntax
--fpu-present

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.

If you choose a valid target processor (command line option -C (--cpu)),

this option is automatically set, based on the chosen target processor.

Example
To allow the use of floating-point unit (FPU) instructions in the assembly
code, enter:
ctc --fpu-present test.c

Related information
Compiler option -C (Use SFR definitions for CPU)

• • • • • • • •
 5-178 TriCore Reference Manual

-g (--debug-info)
Command line syntax
-g

--debug-info

Description
With this option you tell the control program to include debug information
in the generated object file.

Example
cctc -g test.c
cctc --debug-info test.c

The control program includes symbolic debug information in the

generated object file test.elf.

Related information
-
TOOL OPTIONS
 Tool Options - Control Program 5-179

-I (--include-directory)
Command line syntax
-Ipath

--include-directory=path

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.

Example
Suppose that the C source file test.c contains the following lines:
#include <stdio.h>
#include "myinc.h"

You can call the control program as follows:

cctc -Imyinclude test.c
cctc --include-directory=myinclude

First the compiler looks for the file stdio.h in the directory myinclude
relative to the current directory. If it was not found, the compiler searches
in the environment variable and then in the default include directory.

The compiler now looks for the file myinc.h in the directory where
test.c is located. If the file is not there the compiler searches in the
directory myinclude. If it was still not found, the compiler searches in the
environment variable and then in the default include directory.

Related information
Compiler option -I (Add directory to include file search path)
Compiler option -H (Include file at the start of a compilation)

• • • • • • • •
 5-180 TriCore Reference Manual

--instantiate
Command line syntax
--instantiate=mode

Description
Normally, when a file is compiled, no template entities are instantiated
(except those assigned to the file by automatic instantiation). The overall
instantiation mode can, however, be changed with this option. You can
specify the following modes:

none Do not automatically create instantiations of any template

entities. This is the default. It is also the usually appropriate
mode when automatic instantiation is done.

used Instantiate those template entities that were used in the

compilation. This will include all static data members for which
there are template definitions.

all Instantiate all template entities declared or referenced in the

compilation unit. For each fully instantiated template class, all of
its member functions and static data members will be
instantiated whether or not they were used. Non-member
template functions will be instantiated even if the only reference
was a declaration.

local Similar to --instantiate=used except that the functions are

given internal linkage. This is intended to provide a very simple
TOOL OPTIONS

mechanism for those getting started with templates. The

compiler will instantiate the functions that are used in each
compilation unit as local functions, and the program will link
and run correctly (barring problems due to multiple copies of
local static variables). However, one may end up with many
copies of the instantiated functions, so this is not suitable for
production use.

You cannot use --instantiate=local in conjunction with automatic

template instantiation.

Example
To specify instantiation mode used, type
cctc --instantiate=used test.cc
 Tool Options - Control Program 5-181

Related information
-

• • • • • • • •
 5-182 TriCore Reference Manual

--instantiation-dir
Command line syntax
--instantiation-dir=dir

Description
With this option the C++ compiler generates additional files for template
instantiations in the specified directory.

If you do not specify this option, files are created in the current directory.

If you specify the control program option

--no-one-instantiation-per-object, this option remains without effect.

Example
To specify the directory for instantiation files, type
cctc --instantiation-dir=instant test.cc

Related information
Control program option --no-one-instantiation-per-object
TOOL OPTIONS
 Tool Options - Control Program 5-183

--instantiation-file
Command line syntax
--instantiation-file=file

Description
With this option the C++ compiler generates a list of all generated template
instantiation files and writes it to the specified file. You can use this file for
example to use as an option file for the archiver artc.

Example
To create a file with a list of all generated instantiation files, type
cctc --instantiation-file=instlist.ii test.cc

Related information
-

• • • • • • • •
 5-184 TriCore Reference Manual

--is-tricore2
Command line syntax
--is-tricore2

Description
With this option you allow the control program to use TriCore 2
instructions in the generated output file.

If you choose a valid target processor (command line option -C (--cpu)),

this option is automatically set, based on the chosen target processor.

Example
To allow the use of TriCore 2 instructions in the assembly code, enter:
cctc --is-tricore2 test.c

Related information
Compiler option -C (Use SFR definitions for CPU)
TOOL OPTIONS
 Tool Options - Control Program 5-185

--iso
Command line syntax
--iso={90|99}

Description
With this option you specify to the control program against which ISO
standard it should check your C source. C90 is also referred to as the
"ANSI C standard". C99 refers to the newer ISO/IEC 9899:1999 (E) standard
and is the default.

Independent of the chosen ISO standard, the control program always links
libraries with C99 support.

Example
To compile the file test.c conform the ISO C90 standard:
cctc --iso=90 test.c

Related information
Compiler option -c (ISO C standard)

• • • • • • • •
 5-186 TriCore Reference Manual

-k (--keep-output-files)
Command line syntax
-k

--keep-output-files

Description
If an error occurs during the compilation, assembling or linking process,
the resulting output file may be incomplete or incorrect. With this option
you keep the generated output files when an error occurs.

By default the control program removes generated output files when an

error occurs. This is useful when you use the make utility. 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 use the generated files. For
example when you know that a particular error does not result in a
corrupt file, or when you want to inspect the output file, or send it to
Altium support.

Example
cctc -k test.c
cctc --keep-output-files test.c

When an error occurs during compiling, assembling or linking, the

TOOL OPTIONS

erroneous generated output files will not be removed.

Related information
-
 Tool Options - Control Program 5-187

-L (--library-directory /
--ignore-default-library-path)
Command line syntax
-Lpath
--library-directory=path

-L
--ignore-default-library-path

Description
With this option you can specify the path(s) where your system libraries,
specified with the -l option, are located. If you want to specify multiple
paths, use the option -L for each separate path.

The default path is $(PRODDIR)\lib\tc1 .

If you specify only -L (without a pathname) or the long option

--ignore-default-library-path, the linker will not search the default
path and also not in the paths specified in the environment variables
LIBTC1V1_2, LIBTC1V1_3 or LIBTC2. So, the linker ignores steps 2 and 3
as listed below.

The priority order in which the linker searches for system libraries
specified with the -l option is:

1. The path that is specified with the -L option.

2. The path that is specified in the environment variables LIBTC1V1_2,

LIBTC1V1_3 or LIBTC2 when the product was installed.

3. The default directory $(PRODDIR)\lib\tc1 or

$(PRODDIR)\lib\tc2 .

Example
Suppose you call the control program as follows:
cctc test.c -Lc:\mylibs -lcs
cctc test.c --library-directory=c:\mylibs -lcs

First the linker looks in the directory c:\mylibs for library libc.a (this
option).

• • • • • • • •
 5-188 TriCore Reference Manual

If it does not find the requested libraries, it looks in the directory that is set
with the environment variables LIBTC1V1_2, LIBTC1V1_3 or LIBTC2.

Then the linker looks in the default directory $(PRODDIR)\lib\tc1 or

$(PRODDIR)\lib\tc2 for libraries.

Related information
Linker option -l (Search also in system library libname)
TOOL OPTIONS
 Tool Options - Control Program 5-189

-l (--library)
Command line syntax
-lname

--library=name

Description
With this option you tell the linker via the control program to search also
in system library libname.a, where name is a string. The linker first
searches for system libraries in any directories specified with -Lpath, then
in the directories specified with the environment variables LIBTC1V1_2,
LIBTC1V1_3 or LIBTC2, unless you used the option -L without a directory.

Example
To search in the system library libfp.a (floating-point library):
cctc test.obj mylib.a -lfp
cctc test.obj mylib.a --library=fp

The linker links the file test.obj and first looks in mylib.a (in the
current directory only), then in the system library libfp.a to resolve
unresolved symbols.

Related information
Control program option -L (Add library directory)

Section 7.4, Linking with Libraries, in the User's Manual.

• • • • • • • •
 5-190 TriCore Reference Manual

--list-object-files
Command line syntax
--list-object-files

Description
With this option the list of object files that are handled by the prelinker, is
displayed at stdout. The list is shown when it is changed by the
prelinker.

Example
To show the list of object files handled by the prelinker, enter:
cctc --list-object-files test.cc

Related information
-
TOOL OPTIONS
 Tool Options - Control Program 5-191

--mmu-present
Command line syntax
--mmu-present

Description
With this option you can use memory management instructions in the
assembly code. When you select this option, the define __MMU__ is set
to 1.

Example
To allow the use of memory management unit (MMU) instructions in the
assembly code, enter:
cctc --mmu-present test.c

Related information
Assembler option -C (Select CPU)

• • • • • • • •
 5-192 TriCore Reference Manual

-n (--dry-run)
Command line syntax
-n
--dry-run

Description
With this option you put the control program verbose mode. The control
program prints the invocations of the tools it would use to process the
files.

Example
To see how the control program will invoke the tools it needs to process
the file test.c:
cctc -n test.c
cctc --dry-run test.c

The control program only displays the invocations of the tools it would
use to create the final object file but does not actually perform the steps.

Related information
Control program option -v (Verbose output)
TOOL OPTIONS
 Tool Options - Control Program 5-193

--no-auto-instantiation
Command line syntax
--no-auto-instantiation

Description
Default, the c++ compiler automatically instantiates templates. With this
option automatic instantiation of templates is disabled.

Example
To disable automatic instantiation, type
cctc --no-auto-instantiation test.cc

Related information
For an extensive description of automatic insantiation, refer to section
2.6.1, Automatic Instantiation, in the TriCore C++ Compiler User's Manual.

• • • • • • • •
 5-194 TriCore Reference Manual

--no-default-libraries
Command line syntax
--no-default-libraries

Description
Default the control program specifies the standard C libraries and run-time
library to the linker.

With this option you tell the control program not to specify the standard C
libraries and run-time library to the linker.

In this case you must specify the libraries you want to link to the linker
with the option -llibrary_name. The control program recognizes the
option -l as an option for the linker.

Example
cctc --no-default-libraries test.c

The control program does not specify any libraries to the linker. In normal
cases this would result in unresoved externals.

To specify your own libraries (libmy.a) and avoid unresolved externals:

cctc --no-default-libraries -lmy test.c

Related information
TOOL OPTIONS

Linker option -l (Search also in system library libx.a)

 Tool Options - Control Program 5-195

--no-map-file
Command line syntax
--no-map-file

Description
By default the control program generates a linker map file (.map).

A linker map file is a text file that shows how the linker has mapped the
sections and symbols from the various object files (.obj) to the linked
object file. A locate part shows the absolute position of each section.
External symbols are listed per space with their absolute address, both
sorted on symbol and sorted on address.

With this option you prevent the generation of a map file.

Example
To prevent the generation of the linker map file test.map:
cctc --no-map-file test.c

Related information
Linker option -M (Generate map file)

• • • • • • • •
 5-196 TriCore Reference Manual

--no-one-instantiation-per-object
Command line syntax
--no-one-instantiation-per-object

Description
With this option, the C++ compiler writes template instantiations into a
single object file. If you do not specify this option, the C++ compiler
creates multiple files. In that case you can specify a directory for those files
with the control program option --instantiation-dir.

Example
To create a file with a list of all generated instantiation files, type
cctc --no-one-instantiation-per-object test.cc

Related information
Control program option --instantiation-dir
TOOL OPTIONS
 Tool Options - Control Program 5-197

--no-tasking-sfr
Command line syntax
--no-tasking-sfr

Description
Normally, the compiler and assembler include a special function register
(SFR) file before compiling. This file is automatically selected based on the
target you select on the Processor definition page of the Processor
options (compiler option -C).

With this option the compiler and assembler do not automatically include
a register file.

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

Example
cctc -Ctc11ib --no-tasking-sfr test.c

The register file regtc11ib.sfr is not included.

Related information
Compiler option -C (Use SFR definitions for CPU)

• • • • • • • •
 5-198 TriCore Reference Manual

-o (--output)
Command line syntax
-ofile

--output=file

Description
By default, the control program generates a file with the same basename
as the first specified input file. With this option you specify another name
for the resulting absolute object file.

Example
cctc test.c prog.c

The control program generates an ELF/DWARF object file (default) with

the name test.elf.

To generate the file result.elf:

cctc -oresult.elf test.c prog.c
cctc --output=result.elf test.c prog.c

Related information
-
TOOL OPTIONS
 Tool Options - Control Program 5-199

--prelink-copy-if-non-local
Command line syntax
--prelink-copy-if-non-local

Description
If a file must be recompiled and it is not in the current directory, with this
option the C++ prelinker copies the prelink file (.ii) to the current
directory and rewrites that .ii file so it can find its associated .cc file. As a
result, the .cc file is recompiled in the current directory.

With this option you prevent that previously compiled files are overwritten
during recompilation.

Example
To copy all files for recompilation to the current directory:
cctc --prelink-copy-if-non-local test.cc

Related information
-

• • • • • • • •
 5-200 TriCore Reference Manual

--prelink-local-only
Command line syntax
--prelink-local-only

Description
With this option the C++ prelinker ignores all files that are outside the
current directory.

Example
To prelink only files in the current directory:
cctc --prelink-local-only test.cc

Related information
-
TOOL OPTIONS
 Tool Options - Control Program 5-201

--prelink-remove-instantiation-flags
Command line syntax
--prelink-remove-instantiation-flags

Description
With this option the C++ prelinker removes all instantiation flags from the
generated object files.

Example
To remove instantiation flags from the generated object files:
cctc --prelink-remove-instantiation-flags test.cc

Related information
-

• • • • • • • •
 5-202 TriCore Reference Manual

--show-c++-warnings
Command line syntax
--show-c++-warnings

Description
The C++ compiler may generate a compiled C++ file (.ic) that causes
warnings during compilation or assembling. With this option you tell the
control program to show these warnings. Default C++ warnings are
suppressed.

Example
cctc --show-c++-warnings test.cc

The control program calls the C++ compiler which generates the C file
(test.ic). If this file causes warnings during compilation or assembling,
these warnings are shown.

Related information
-
TOOL OPTIONS
 Tool Options - Control Program 5-203

--silicon-bug
EDE
1. From the Project menu, select Project Options...

The Project Options dialog appears.

2. Expand the Processor entry and select Bypasses.

3. Select the bypasses you want to enable.

Command line syntax

--silicon-bug=arg,...

You can give one or more of the following arguments (corresponding

pragmas are listed to be complete):

all-tc112 All TriCore 1 v1.2 (TC112) workarounds

all-tc113 All TriCore 1 v1.3 (TC113) workarounds

cor1 workaround for TC112 COR1 (#pragma TC112_COR1 )

cor4 workaround for TC112 COR4 (#pragma TC112_COR4 )
cor7 workaround for TC112 COR7 (#pragma TC112_COR7 )
cor10 workaround for TC112 COR10 (#pragma TC112_COR10)
cor13 workaround for TC112 COR13 (#pragma TC112_COR13)
cor14 workaround for TC112 COR14 (#pragma TC112_COR14)
cor16 workaround for TC112 COR16 (#pragma TC112_COR16)
cor17 workaround for TC112 COR17 (#pragma TC112_COR17)

cpu-tc013 workaround for CPU_TC.013 (#pragma CPU_TC013)

cpu-tc030 workaround for CPU_TC.030 (#pragma CPU_TC030)
cpu-tc031 workaround for CPU_TC.031 (#pragma CPU_TC031)
cpu-tc034 workaround for CPU_TC.034 (#pragma CPU_TC034)
cpu-tc048 workaround for CPU_TC.048 (#pragma CPU_TC048)
cpu-tc050 workaround for CPU_TC.050 (#pragma CPU_TC050)
cpu-tc060 workaround for CPU_TC.060 (#pragma CPU_TC060)

• • • • • • • •
 5-204 TriCore Reference Manual

cpu5 workaround for TC113 CPU5 (#pragma TC113_CPU5 )

cpu9 workaround for TC113 CPU9 (#pragma TC113_CPU9 )
cpu11 workaround for TC113 CPU11 (#pragma TC113_CPU11)
cpu14 workaround for TC113 CPU14 (#pragma TC113_CPU14)
cpu15 workaround for TC113 CPU15 (#pragma TC113_CPU15)
cpu16 workaround for TC113 CPU16 (#pragma TC113_CPU16)
dmu1 workaround for TC113 DMU1 (#pragma TC113_DMU1)
lfi2 workaround for TC113 LFI2 (#pragma TC113_LFI2 )
lfi3 workaround for TC113 LFI3 (#pragma TC113_LFI3 )

Description
With this option the control program tells the compiler/assembler/linker to
use software workarounds for some CPU functional problems.

Example
cctc --silicon-bug=cpu5,cpu9 test.c

The compiler uses workarounds for TC113 problems CPU5 and CPU9.

Related information
See Chapter 9, CPU Functional Problems, for more information about the
individual problems and workarounds.
TOOL OPTIONS
 Tool Options - Control Program 5-205

--space
Command line syntax
--space=space_name

Description
If you specify IHEX or SREC with the control option --format, you can
additionally specify the record length and the address space to be emitted
in the output files.

With this option you can specify which address space must be emitted.
With the argument space_name you can specify the name of the address
space. The name of the output file will be filename with the extension
.hex or .s.

If you do not specify space_name, the default address space is emitted. In

this case the name of the output file will be filename_spacename with the
extension .hex or .s.

Example
To create the IHEX file test.hex, type:
cctc --format=IHEX --space=far test.c

If the specified memory space does not exist, the control program emits
the default space name and reflects this in the output file name.

Related information
Control program option --format (Set linker output format)

Linker option -o (Specify an output object file)

• • • • • • • •
 5-206 TriCore Reference Manual

--static
Command line syntax
--static

Description
This option is directly passed to the compiler.

With this option, the compiler treats external definitions at file scope
(except for main) as if they were declared static. As a result, unused
functions will be eliminated, and the alias checking algorithm assumes that
objects with static storage cannot be referenced from functions outside the
current module.

This option only makes sense when you specify all modules of an
application on the command line.

Example
cctc --static module1.c module2.c module3.c

Related information
-
TOOL OPTIONS
 Tool Options - Control Program 5-207

-t (--keep-temporary-files)
Command line syntax
-t

--keep-temporary-files

Description
By default, the control program removes intermediate files like the .src
file (result of the compiler phase) and the .eln file (result of the linking
phase).

With this option you tell the control program to keep temporary files it
generates during the creation of the absolute object file.

Example
To keep all temporary files:
cctc -t test.c
cctc --keep-temporary-files test.c

The control program keeps all intermediate files it generates while creating
the absolute object file test.elf.

Related information
-

• • • • • • • •
 5-208 TriCore Reference Manual

-U (--undefine)
Command line syntax
-Umacro_name
--undefine=macro_name

Description
With this option you can undefine an earlier defined macro as with
#undef.

This option is for example useful to undefine predefined macros.

However, the following predefined ISO C standard macros cannot be

undefined:

__FILE__ current source filename

__LINE__ current source line number (int type)
__TIME__ hh:mm:ss
__DATE__ mmm dd yyyy
__STDC__ level of ANSI standard

The control program passes the option -U (--undefine) to the compiler.

Example
To undefine the predefined macro __TASKING__:
cctc -U__TASKING__ test.c
TOOL OPTIONS

cctc --undefine=__TASKING__ test.c

Related information
Control Pogram option -D (Define preprocessor macro)
 Tool Options - Control Program 5-209

-V (--version)
Command line syntax
-V
--version

Description
Display version information. The control program ignores all other options
or input files.

Example
cctc -V
cctc --version

The control program does not call any tools but displays the following
version information:
TASKING TriCore VX-toolset control program vx.yrz Build nnn
Copyright 2003-year Altium BV Serial# 00000000

Related information
-

• • • • • • • •
 5-210 TriCore Reference Manual

-v (--verbose)
Command line syntax
-v
--verbose

Description
With this option you put the control program in verbose mode. With the
option -v the control program performs it tasks while it prints the steps it
performs to stdout.

Example
cctc -v test.c
cctc --verbose test.c

The control program processes the file test.c and displays the
invocations of the tools it uses to create the final object file

Related information
Control program option -n (Verbose output and suppress execution)
TOOL OPTIONS
 Tool Options - Control Program 5-211

-Wtool (--pass)
Command line syntax

-Wcpoption --pass-c++=option Pass option directly to the

C++ compiler
-Wcoption --pass-c=option Pass option directly to the
C compiler
-Waoption --pass-assembler=option Pass option directly to the
assembler
-Wploption --pass-prelinker=option Pass option directly to the
C++ prelinker
-Wloption --pass-linker=option Pass option directly to the
linker

Description
With this option you tell the control program to call a tool with the
specified option. The control program does not use the option itself, but
specifies it directly to the tool which the control program calls.

Example
cctc -Wl-r test.c

The control program does not use the option -r but calls the linker with
the option -r (ltc -r).

Related information
-

• • • • • • • •
 5-212 TriCore Reference Manual

-w (--no-warnings)
Command line syntax
-w[nr]
--no-warnings[=nr]

Description
With this option suppresses all warning messages or a specific warning. If
you do not specify this option, all warnings are reported.

Example
To suppress all warnings:
cctc -w test.c
cctc --no-warnings test.c

To suppress warnings 100:

cctc -w100 test.c
cctc --no-warnings=100 test.c

Related information
Control program option --warnings-as-errors (Warnings as errors)
TOOL OPTIONS
 Tool Options - Control Program 5-213

--warnings-as-errors
Command line syntax
--warnings-as-errors

Description
With this option you tell the control program to treat warnings as errors.

Example
cctc --warnings-as-errors test.c

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

Related information
Control program option -w (Suppress all warnings)

• • • • • • • •
 5-214 TriCore Reference Manual

5.5 MAKE UTILITY OPTIONS

When you build a project in EDE, EDE generates a makefile and uses the
graphical make utility wmk to build all your files. However, you can also
use the make utility mktc from the command line to build your project.

The invocation syntax is:

mktc [option...] [target...] [macro=def]

This section describes all options for the make utility. The make utility is a
command line tool so there are no equivalent options in EDE.
TOOL OPTIONS
 Tool Options - Make Utility 5-215

Defining Macros
Command line syntax
macro=definition

Description
With this argument you can define a macro and specify it to the make
utility.

A macro definition remains in existence during the execution of the

makefile, even when the makefile recursively calls the make utility again.
In the recursive call, the macro acts as an environment variable. This
means that it is overruled by definitions in the recursive call. Use the
option -e to prevent this.

You can specify as many macros as you like. 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 -m file.

Defining macros on the command line is, for example, useful in

combination with conditional processing as shown in the example below.

Example
Consider the following makefile with conditional rules to build a demo
program and a real program:
ifdef DEMO # the value of DEMO is of no importance
real.out : demo.o
ltc demo.o main.o -lc -lfp -lrt
else
real.out : real.o
ltc real.o main.o -lc -lfp -lrt
endif

real.elf : real.out
ltc -FELF -oreal.elf real.out

You can now use a macro definition to set the DEMO flag:
mktc real.elf DEMO=1

In both cases the absolute obect file real.elf is created but depending
on the DEMO flag it is linked with demo.o or with real.o.

• • • • • • • •
 5-216 TriCore Reference Manual

Related information
Make utility option -e (Environment variables override macro definitions)
Make utility option -m (Name of invocation file)
TOOL OPTIONS
 Tool Options - Make Utility 5-217

-?
Command line syntax
-?

Description
Displays an overview of all command line options.

Example
The following invocation displays a list of the available command line
options:
mktc -?

Related information
-

• • • • • • • •
 5-218 TriCore Reference Manual

-a
Command line syntax
-a

Description
Normally the make utility rebuilds only those files that are out of date.
With this option you tell the make utility to rebuild all files, without
checking whether they are out of date.

Example
mktc -a

Rebuilds all your files, regardless of whether they are out of date or not.

Related information
-
TOOL OPTIONS
 Tool Options - Make Utility 5-219

-c
Command line syntax
-c

Description
EDE uses this option for the graphical version of make when you create
sub-projects. In this case make calls another instance of make for the
sub-project. With the option -c, the make utility runs as a child process of
the current make.

The option -c overrules the option -err.

Example
The following command runs the make utility as a child process:
mktc -c

Related information
Make utility option -err (Redirect error message to file)

• • • • • • • •
 5-220 TriCore Reference Manual

-D/-DD
Command line syntax
-D
-DD

Description
With the option -D the make utility prints every line of the makefile to
standard output as it is read by mktc.

With the option -DD not only the lines of the makefile are printed but
also the lines of the mktc.mk file (implicit rules).

Example
mktc -D

Each line of the makefile that is read by the make utility is printed to
standard output (usually your screen).

Related information
-
TOOL OPTIONS
 Tool Options - Make Utility 5-221

-d/-dd
Command line syntax
-d
-dd

Description
With the option -d the make utility shows which files are out of date and
thus need to be rebuild. The option -dd gives more detail than the option
-d.

Example
mktc -d

Shows which files are out of date and rebuilds them.

Related information
-

• • • • • • • •
 5-222 TriCore Reference Manual

-e
Command line syntax
-e

Description
If you use macro definitions, they may overrule the settings of the
environment variables.

With the option -e, the settings of the environment variables are used
even if macros define otherwise.

Example
mktc -e

The make utility uses the settings of the environment variables regardless
of macro definitions.

Related information
-
TOOL OPTIONS
 Tool Options - Make Utility 5-223

-err
Command line syntax
-err file

Description
With this option the make utility redirects error messages and verbose
messages to a specified file.

With the option -s the make utility only displays error messages.

Example
mktc -err error.txt

The make utility writes messages to the file error.txt.

Related information
Make utility option -s (Do not print commands before execution)

• • • • • • • •
 5-224 TriCore Reference Manual

-f
Command line syntax
-f my_makefile

Description
Default the make utility uses the file makefile to build your files.

With this option you tell the make utility to use the specified file instead of
the file makefile. Multiple -f options act as if all the makefiles were
concatenated in a left-to-right order.

Example
mktc mymake

The make utility uses the file mymake to build your files.

Related information
-
TOOL OPTIONS
 Tool Options - Make Utility 5-225

-G
Command line syntax
-G path

Description
Normally you must call the make utility mktc from the directory where
your makefile and other files are stored.

With the option -G you can call the make utility from within another
directory. The path is the path to the directory where your makefile and
other files are stored and can be absolute or relative to your current
directory.

Example
Suppose your makefile and other files are stored in the directory
\currdir\myfiles . When your current directory is \currdir, you can
call the make utility as follows:
mktc -G myfiles

Related information
-

• • • • • • • •
 5-226 TriCore Reference Manual

-i
Command line syntax
-i

Description
When an error occurs during the make process, the make utility exits with
a certain exit code.

With the option -i, the make utility exits without an error code, even
when errors occurred.

Example
mktc -i

The make utility exits without an error code, even when an error occurs.

Related information
-
TOOL OPTIONS
 Tool Options - Make Utility 5-227

-K
Command line syntax
-K

Description
With this option the make utility keeps temporary files it creates during the
make process. The make utility stores temporary files in the directory that
you have specified with the environment variable TMPDIR or in the
default 'temp' directory of your system when the TMPDIR variable is not
specified.

Example
mktc -K

The make utility preserves all temporary files.

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

• • • • • • • •
 5-228 TriCore Reference Manual

-k
Command line syntax
-k

Description
When during the make process the make utility encounters an error, it
stops rebuilding your files.

With the option -k, the make utility only stops building the target that
produced the error. All other targets defined in the makefile are built.

Example
mktc -k

If the make utility encounters an error, it stops building the current target
but proceeds with the other targets that are defined in the makefile.

Related information
Make utility option -S (Undo the effect of -k)
TOOL OPTIONS
 Tool Options - Make Utility 5-229

-m
Command line syntax
-m file

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

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 -m multiple times.

Format of an option file

• Multiple command line arguments on one line in the option file are
allowed.
• To include whitespace in an argument, surround the argument with
single or double quotes.
• If you want to use single quotes as part of the argument, surround the
argument by double quotes and vise versa:
"This has a single quote ' embedded"

'This has a double quote " embedded'

'This has a double quote " and \

a single quote '"' embedded"

Note that adjacent strings are concatenated.

• When a text line reaches its length limit, use a '\' to continue the line.
Whitespace between quotes is preserved.
"This is a continuation \
line"
-> "This is a continuation line"
• It is possible to nest command line files up to 25 levels.

• • • • • • • •
 5-230 TriCore Reference Manual

Example
Suppose the file myoptions contains the following lines:
-k
-err errors.txt
test.elf

Specify the option file to the make utility:

mktc -m myoptions

This is equivalent to the following command line:

mktc -k -err errors.txt test.elf

Related information
-
TOOL OPTIONS
 Tool Options - Make Utility 5-231

-n
Command line syntax
-n

Description
With this option you tell the make utility to perform a dry run. The make
utility shows what it would do but does not actually perform these tasks.

This option is for example useful to quickly inspect what would happen if
you call the make utility.

Example
mktc -n

The make utility does not perform any tasks but displays what it would do
if called without the option -n.

Related information
Make utility option -s (Do not print commands before execution)

• • • • • • • •
 5-232 TriCore Reference Manual

-p
Command line syntax
-p

Description
Normally, if a command in a target rule in a makefile returns an error or
when the target construction is interrupted, the make utility removes that
target file. With this option you tell the make utility to make all target files
precious. This means that all dependency files are never removed.

Example
mktc -p

The make utility never removes target dependency files.

Related information
Special target .PRECIOUS in section 8.3.2, Writing a Makefile in Chapter
Using the Utilities of the Reference Manual.
TOOL OPTIONS
 Tool Options - Make Utility 5-233

-q
Command line syntax
-q

Description
With this option the make utility does not perform any tasks but only
returns an error code. A zero status indicates that all target files are up to
date, a non-zero status indicates that some or all target files are out of
date.

Example
mktc -q

The make utility only returns an error code that indicates whether all target
files are up to date or not. It does not rebuild any files.

Related information
-

• • • • • • • •
 5-234 TriCore Reference Manual

-r
Command line syntax
-r

Description
When you call the make utility, it first reads the implicit rules from the file
mktc.mk, then it reads the makefile with the rules to build your files. (The
file mktc.mk is located in the \etc directory of the TriCore toolchain.)

With this option you tell the make utility not to read mktc.mk and to rely
fully on the make rules in the makefile.

Example
mktc -r

The make utility does not read the implicit make rules in mktc.mk.

Related information
-
TOOL OPTIONS
 Tool Options - Make Utility 5-235

-S
Command line syntax
-S

Description
With this option you cancel the effect of the option -k. This is never
necessary except in a recursive make where the option -k might be
inherited from the top-level make via MAKEFLAGS or if you set the option
-k in the environment variable MAKEFLAGS.

Example
mktc -S

The effect of the option -k is cancelled so the make utility stops with the
make process after it encounters an error.

The option -k in this example may have been set with the environment
variable MAKEFLAGS or in a recursive call to mktc in the makefile.

Related information
Make utility option -k (On error, abandon the work for the current target
only)

• • • • • • • •
 5-236 TriCore Reference Manual

-s
Command line syntax
-s

Description
With this option you tell the make utility to perform its tasks without
printing the commands it executes. Error messages are normally printed.

Example
mktc -s

The make utility rebuilds your files but does not print the commands it
executes during the make process.

Related information
Make utility option -n (Perform a dry run)
TOOL OPTIONS
 Tool Options - Make Utility 5-237

-t
Command line syntax
-t

Description
With this option you tell the make utility to touch the target files, bringing
them up to date, rather than performing the rules to rebuild them.

Example
mktc -t

The make utility updates out-of-date files by giving them a new date and
time stamp. The files are not actually rebuild.

Related information
-

• • • • • • • •
 5-238 TriCore Reference Manual

-time
Command line syntax
-time

Description
With this option you tell the make utility to display the current date and
time on standard output.

Example
mktc -time

The make utility displays the current date and time and updates
out-of-date files.

Related information
-
TOOL OPTIONS
 Tool Options - Make Utility 5-239

-V
Command line syntax
-V

Description
Display version information. The make utility ignores all other options or
input files.

Example
mktc -v

The make utility does not perform any tasks but displays the following
version information:
TASKING TriCore VX-toolset program builder vxx.yrz Build nnn
Copyright year Altium BV Serial# 00000000

Related information
-

• • • • • • • •
 5-240 TriCore Reference Manual

-W
Command line syntax
-W target

Description
With this option the make utility considers the specified target file always
as up to date and will not rebuild it.

Example
mktc -W test.elf

The make utility rebuilds out of date targets in the makefile except the file
test.elf which is considered now as up to date.

Related information
-
TOOL OPTIONS
 Tool Options - Make Utility 5-241

-w
Command line syntax
-w

Description
With this option the make utility sends error messages and verbose
messages to standard out. Without this option, the make utility sends these
messages to standard error.

This option is only useful on UNIX systems.

Example
mktc -w

The make utility sends messages to standard out instead of standard error.

Related information
-

• • • • • • • •
 5-242 TriCore Reference Manual

-x
Command line syntax
-x

Description
With this option the make utility shows extended error messages.
Extended error messages give more detailed information about the exit
status of the make utility after errors. EDE uses this option for the
graphical version of make.

Example
mktc -x

If errors occur, the make utility gives extended information.

Related information
-
TOOL OPTIONS
 Tool Options - Archiver 5-243

5.6 ARCHIVER OPTIONS

The archiver and library maintainer artc is a tool to build library files and
it offers the possibility to replace, extract and remove modules from an
existing library.

The invocation syntax is:

artc key_option [sub_option...] library [object_file]

This section describes all options for the archiver. Some suboptions can
only be used in combination with certain key options. They are described
together. Suboptions that can always be used are described separately.

The archiver is a command line tool so there are no equivalent options in

EDE.

Description Option Suboption

Display an overview of all options -?
Display version information -V
Print object module to standard output -p
Main functions
Delete object module from library -d -v
Move object module to another position -m -a -b -v
Replace or add an object module -r -a -b -c -u -v
Print a table of contents of the library -t -s0 -s1
Extract an object module from the library -x -v

Table 5-1: Overview of archiver options and suboptions

• • • • • • • •
 5-244 TriCore Reference Manual

-?
Command line syntax
-?

Description
Displays an overview of all command line options.

Example
The following invocations display a list of the available command line
options:
artc -?
artc

Related information
-
TOOL OPTIONS
 Tool Options - Archiver 5-245

-d
Command line syntax
-d [-v]

Description
Delete the specified object modules from a library. With the suboption -v
the archiver shows which files are removed.

-v Verbose: the archiver shows which files are removed.

Example
artc -d lib.a obj1.o obj2.o

The archiver deletes obj1.o and obj2.o from the library lib.a.
artc -d -v lib.a obj1.o obj2.o

The archiver deletes obj1.o and obj2.o from the library lib.a and
displays which files are removed.

Related information
-

• • • • • • • •
 5-246 TriCore Reference Manual

-m
Command line syntax
-m [-a posname] [-b posname]

Description
Move the specified object modules to another position in the library.

The ordering of members in a library can make a difference in how

programs are linked if a symbol is defined in more than one member.

Default, the specified members are moved to the end of the archive. Use
the suboptions -a or -b to move them to a specified place instead.

-a posname Move the specified object module(s) after

the existing module posname.

-b posname Move the specified object module(s) before

the existing module posname.

Example
Suppose the library lib.a contains the following objects (see option -t):
obj1.o
obj2.o
obj3.o

To move obj1.o to the end of lib.a:

TOOL OPTIONS

artc -m lib.a obj1.o

To move obj3.o just before obj2.o:

artc -m -b obj3.o lib.a obj2.o

The library lib.a after these two invocations now looks like:
obj3.o
obj2.o
obj1.o

Related information
Archiver option -t (Print library contents)
 Tool Options - Archiver 5-247

-p
Command line syntax
-p

Description
Print the specified object module(s) in the library to standard output.

This option is only useful when you redirect or pipe the output to other
files or tools that serve your own purposes. Normally you do not need this
option.

Example
artc -p lib.a obj1.o > file.o

The archiver prints the file obj1.o to standard output where it is

redirected to the file file.o. The effect of this example is very similar to
extracting a file from the library but in this case the 'extracted' file gets
another nam.

Related information
-

• • • • • • • •
 5-248 TriCore Reference Manual

-r
Command line syntax
-r [-a posname] [-b posname] [-c] [-u] [-v]

Description
You can use the option -r for several purposes:
• Adding new objects to the library
• Replacing objects in the library with the same object of a newer date
• Creating a new library
The option -r normally adds a new module to the library. However, if the
library already contains a module with the specified name, the existing
module is replaced. If you specify a library that does not exist, the archiver
creates a new library with the specified name.

If you add a module to the library without specifying the suboption -a or

-b, the specified module is added at the end of the archive. Use the
suboptions -a or -b to insert them to a specified place instead.

-a posname Add the specified object module(s) after the

existing module posname.

-b posname Add the specified object module(s) before

the existing module posname.

-c Create a new library without checking

TOOL OPTIONS

whether it already exists. If the library

already exists, it is overwritten.

-u Insert the specified object module only if it

is newer than the module in the library.

-v Verbose: the archiver shows which files are

removed.

The suboptions -a or -b have no effect when an object is added to the

library.
 Tool Options - Archiver 5-249

Examples
Suppose the library lib.a contains the following objects (see option -t):
obj1.o

To add obj2.o to the end of lib.a:

artc -r lib.a obj2.o

To insert obj3.o just before obj2.o:

artc -r -b obj2.o lib.a obj3.o

The library lib.a after these two invocations now looks like:
obj1.o
obj3.o
obj2.o

Creating a new library

To create a new library file, add an object file and specify a library that
does not yet exist:
artc -r obj1.o newlib.a

The archiver creates the library newlib.a and adds the object obj1.o to
it.

To create a new library file and overwrite an existing library, add an object
file and specify an existing library with the supoption -c:
artc -r -c obj1.o lib.a

The archiver overwrites the library lib.a and adds the object obj1.o to
it. The new library lib.a only contains obj1.o.

Related information
Archiver option -t (Print library contents)

• • • • • • • •
 5-250 TriCore Reference Manual

-t
Command line syntax
-t [-s0|-s1]

Description
Print a table of contents of the library to standard out. With the
suboption -s you the archiver displays all symbols per object file.

-s0 Displays per object the library in which it resides, the

name of the object itself and all symbols in the object.

-s1 Displays only the symbols of all object files in the

library.

Example
artc -t lib.a

The archiver prints a list of all object modules in the library lib.a.
artc -t -s0 lib.a

The archiver prints per object all symbols in the library. This looks like:
prolog.o
symbols:
lib.a:prolog.o:___Qabi_callee_save
lib.a:prolog.o:___Qabi_callee_restore
TOOL OPTIONS

div16.o
symbols:
lib.a:div16.o:___udiv16
lib.a:div16.o:___div16
lib.a:div16.o:___urem16
lib.a:div16.o:___rem16

Related information
-
 Tool Options - Archiver 5-251

-V
Command line syntax
-V

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

Example
artc -V

The archiver does not perform any tasks but displays the following version
information:
TASKING TriCore VX-toolset ELF archiver vxx.yrz Build nnn
Copyright year Altium BV Serial# 00000000

Related information
-

• • • • • • • •
 5-252 TriCore Reference Manual

-x
Command line syntax
-x [-o] [-v]

Description
Extract an existing module from the library.

-o Give the extracted object module the same date as the

last-modified date that was recorded in the library.

Without this suboption it receives the last-modified

date of the moment it is extracted.

-v Verbose: the archiver shows which files are extracted.

Example
To extract the file obj.o from the library lib.a:
artc -x lib.a obj1.o

If you do not specify an object module, all object modules are extracted:
artc -x lib.a

Related information
-
TOOL OPTIONS
 Tool Options - Archiver 5-253

-w
Command line syntax
-wlevel

Description
With this suboption you tell the archiver to suppress all warnings above
the specified level. The level is a number between 0 - 9.

The level of a message is printed between parentheses after the warning

number. If you do not use the -w option, the default warning level is 8.

Example
To suppresses warnings above level 5:
artc -x -w5 lib.a obj1.o

Related information
-

• • • • • • • •
 5-254 TriCore Reference Manual
TOOL OPTIONS
CHAPTER

LIST FILE FORMATS

6
 6-2 TriCore Reference Manual

CHAPTER
6
LIST FILE FORMATS
 List File Formats 6-3

6.1 ASSEMBLER LIST FILE FORMAT

The assembler list file is an additional output file of the assembler that
contains information about the generated code.

The list file consists of a page header and a source listing.

Page header
The page header consists of four lines:
TASKING TriCore VX-toolset Assembler vx.yrz Build nnn SN 00000000
This is the page header title Page 1

ADDR CODE CYCLES LINE SOURCE LINE

The first line contains information about the assembler name, version
number and serial number. The second line contains a title specified by
the TITLE (first page) assembler directive and a page number. The third
line is empty. The fourth line contains the heading of the source listing.

Source listing
The following is a sample part of a listing. An explanation of the different
columns follows below.
ADDR CODE CYCLES LINE SOURCE LINE
.
.
0002 85rFrrrr 1 2 27 ld.a a15,world
0006 F4AF 1 3 28 st16.a [a10],a15
0008 91r0rr4r 1 4 29 movh.a a4,#@his(_2_ini)
000C D944rrrr 1 5 30 lea a4,[a4]@los(_2_ini)
0010 1Drrrrrr 1 6 31 j printf
.
.
0000 44 buf: .space 4
| RESERVED
0003

The meaning of the different columns is:

ADDR This column contains the memory address. The

address is a hexadecimal number that represents the
offset from the beginning of a relocatable section or
the absolute address for an absolute section. The
address only appears on lines that generate object
code.

• • • • • • • •
 6-4 TriCore Reference Manual

CODE This is the object code generated by the assembler for

this source line, displayed in hexadecimal format. The
displayed code need not be the same as the generated
code that is entered in the object module. The code
can also be relocatable code. In this case the letter 'r'
is printed for the relocatable code part in the listing.
For lines that allocate space, the code field contains
the text "RESERVED".

CYCLES The first number in this column is the number of

instruction cycles needed to execute the instruction(s)
as generated in the CODE field. The second number is
the accumulated cycle count of this section.

LINE This column contains the line number. This is a

decimal number indicating each input line, starting
from 1 and incrementing with each source line.

SOURCE LINE This column contains the source text. This is a copy of
the source line from the assembly source file.

For the .SET and .EQU directives the ADDR and CODE columns do not
apply. The symbol value is listed instead.
LIST FILE FORMATS

Related information
See section 6.6, Generating a List File, in Chapter Using the Assembler of
the User's Manual for more information on how to generate a list file and
specify the amount of list file information.
 List File Formats 6-5

6.2 LINKER MAP FILE FORMAT

The linker map file is an additional output file of the linker that shows
how the link phase has mapped the sections and symbols from the various
object files (.o) to output sections. The locate part shows the absolute
position of each section. External symbols are listed per space with their
absolute address, both sorted on symbol and sorted on address.

With the linker option -m (map file formatting) you can specify which
parts of the map file you want to see.

Example (part of) linker map file

TriCore VX-toolset object linker - mapfile (task: task1)
Options: -o hello.elf -m2 -mq -ms --map-file
-----------------------------------------------------------------------------------------

**************************************** File Part ************************************

* Processed files:
==================

File | From archive | Symbol causing the extraction

---------------------------------------------------------
cstart.o | libc.a | _START
hello.o | |
printf.o | libc.a | printf

************************************* Call Graph Part *********************************

**************************************** Link Part ************************************

* Section translation:
======================

[in] File | [in] Section | [in] Size | [out] Offset | [out] Section
---------------------------------------------------------------------------------------
hello.o | .text.hello.main | 0x00000014 | 0x00000000 | .text.hello.main
---------------------------------------------------------------------------------------
cstart.o | .text.libc | 0x000001fc | 0x00000000 | .text.libc
strcpy.o | .text.libc | 0x00000024 | 0x000001fc |
printf.o | .text.libc | 0x00000024 | 0x00000700 |
cinit.o | .text.libc | 0x0000004e | 0x00000d68 |
---------------------------------------------------------------------------------------
cstart.o | .text.libc.reset | 0x00000008 | 0x00000000 | .text.libc.reset

• • • • • • • •
 6-6 TriCore Reference Manual

********************************* Module Local Symbols Part ***************************

* Local symbol translation (sorted on symbol):

==============================================

+ File "hello.o"
+ Scope "./hello.o"

Symbol | Address | Space

----------------------------------------------------------
hello.src | 0x00000000 |
----------------------------------------------------------
.zdata.hello.world | 0xd0000000 | spe:tc:abs18
.zrodata.hello..1.ini | 0xa0000008 |
_1_ini | 0xa0000008 |
----------------------------------------------------------
.rodata.hello..2.ini | 0xa00000dc | spe:tc:linear
.text.hello.main | 0xa00000f4 |
_2_ini | 0xa00000dc |
main_function_end | 0xa0000108 |

*********************************** Cross Reference Part ******************************

* Defined symbols:
==================

Definition file | Definition section | Symbol | Referenced in

---------------------------------------------------------------------------------------
_doprint_int.o | .text.libc | __printf_int2 | printf_int.o
LIST FILE FORMATS

_doprint_int.o | .text.libc | _doprint | printf.o

cstart.o | .text.libc | _Exit | exit.o
cstart.o | .text.libc | _start | hello.o
hello.o | .text.hello.main | main | cstart.o

* Undefined symbols:
====================

Symbol | Referenced in
---------------------------------------------------------------------------------------
_LITERAL_DATA_ | cstart.o
_SMALL_DATA_ | cstart.o
_lc_cp | cinit.o

*************************************** Overlay Part **********************************

 List File Formats 6-7

*************************************** Locate Part ***********************************

* Task entry address:

=====================

symbol : _START
absolute: 0xa0000000

* Section translation:
======================

+ Space spe:tc:abs18

Chip | Group | Section | Size (MAU) | Space addr | Chip addr

------------------------------------------------------------------------------------
ext_c | | .zrodata.hello..1.ini | 0x00000006 | 0xa0000008 | 0x00000008
spe:dsram | | .zdata.hello.world | 0x00000004 | 0xd0000000 | 0x00000000

+ Space spe:tc:csa

Chip | Group | Section | Size (MAU) | Space addr | Chip addr

------------------------------------------------------------------------------------
spe:dsram | | csa.01 | 0x00001000 | 0xd0000040 | 0x00000040

+ Space spe:tc:linear

Chip | Group | Section | Size (MAU) | Space addr | Chip addr

------------------------------------------------------------------------------------
ext_c | | .text.libc.reset | 0x00000008 | 0xa0000000 | 0x00000000
| | [.data.libc] | 0x000000c8 | 0xa0000010 | 0x00000010
| | [.zdata.hello.world] | 0x00000004 | 0xa00000d8 | 0x000000d8
| libraries | .text.libc | 0x00000db6 | 0xa0004000 | 0x00004000

* Symbol translation (sorted on symbol):

========================================

Symbol | Address | Space

-----------------------------------------------
world | 0xd0000000 | spe:tc:abs18
-----------------------------------------------
_A8_DATA_ | 0x00000000 | spe:tc:linear
_A9_DATA_ | 0x00000000 |
_Exit | 0xa000416a |

* Symbol translation (sorted on address):

=========================================

Address | Symbol | Space

-----------------------------------------------
0xd0000000 | world | spe:tc:abs18
-----------------------------------------------
0x00000000 | _LITERAL_DATA_ | spe:tc:linear
0x00000000 | _A9_DATA_ |

• • • • • • • •
 6-8 TriCore Reference Manual

*************************************** Memory Part ***********************************

* Address range usage at space level:

=====================================

Name | Total | Used % | Free % | > free gap %

------------------------------------------------------------------------------------
spe:tc:abs18 | 0x30004000 | 0x00001146 1 | 0x30002eba 99| 0x2ffffebc 99
spe:tc:abs24 | 0x50024000 | 0x00071f98 1 | 0x4ffb2068 99| 0x2ff0df0a 59
spe:tc:csa | 0x00006000 | 0x00001004 17 | 0x00004ffc 83| 0x00004fc0 83
spe:tc:linear | 0x50024000 | 0x00071f98 1 | 0x4ffb2068 99| 0x2ff0df0a 59
spe:tc:pcp_code | 0x00002000 | 0x00000000 0 | 0x00002000 100| 0x00002000 100
spe:tc:pcp_data | 0x00000400 | 0x00000000 0 | 0x00000400 100| 0x00000400 100

* Address range usage at memory level:

======================================

Name | Total | Used % | Free % | > free gap %

------------------------------------------------------------------------------------
ext_c | 0x00080000 | 0x00000ef8 1 | 0x0007f108 99| 0x0007b24a 96
ext_d | 0x00070000 | 0x0006fff8 100 | 0x00000008 0| 0x00000008 0
spe:dsram | 0x00006000 | 0x00001004 17 | 0x00004ffc 83| 0x00004fc0 83

********************************* Linker Script File Part *****************************

************************************ Locate Rule Part *********************************

Address space | Type | Properties | Sections

LIST FILE FORMATS

------------------------------------------------------------------------------------
spe:tc:abs18 | unrestricted | | .zrodata.hello..1.ini
spe:tc:abs18 | clustered | gaps(protected, not filled) | .zdata.hello.world
spe:tc:linear | post-action | ballooning | istack ustack
spe:tc:linear | absolute | 0xa0004000 | .text.libc

The meaning of the different parts is:

File Part
This part of the map file shows all processed files. This also includes
object files that are extracted from a library, with the symbol that led to the
extraction

Call Graph Part

This part of the map file contains a schematic overview that shows how
(library) functions call each other. To obtain call graph information, the
assembly file must contain .CALLS directives which you must manually
add to the assembly source.

By default this part is not shown in the map file. You have to turn this part
on manually with linker option -mc (call graph info).
 List File Formats 6-9

Link Part: Section translation

This part of the map file shows per object file how the link phase has
mapped the sections from the various object files (.o) to output sections.

[in] File The name of an input object file.

[in] Section A section name from the input object file.

[in] Size The size of the input section.

[out] Offset The offset relative to the start of the output section.

[out] Section The resulting output section name.

The input sections .text.libc in the object modules cstart.o,

strcpy.o, printf.o and cinit.o in the example above are all mapped
on the output section .text.libc on succeeding offsets.

Module Local Symbols Part

This part of the map file shows a table for each local scope within an
object file. Each table has three columns, 1 the symbol name, 2 the
address of the symbol and 3 the space where the symbol resides in. The
table is sorted on symbol name within each space.

By default this part is not shown in the map file. You have to turn this part
on manually with linker option -mq (module local symbols).

Cross Reference Part

This part of the map file lists all symbols defined in the object modules
and for each symbol the object modules that contain a reference to the
symbol are shown. Also, symbols that remain undefined are shown.

By default this part is not shown in the map file. You have to turn this part
on manually with linker option -mr (cross references info).

Overlay Part
This part of the map file shows how the static stack is organized. This part
is empty for the TriCore. This part also shows the locate overlay
information if you used overlay groups in the linker script file.

By default this part is not shown in the map file. You have to turn this part
on manually with linker option -mo (overlay info).

• • • • • • • •
 6-10 TriCore Reference Manual

Locate Part: Section translation

This part of the map file shows the absolute position of each section in the
absolute object file. It is organized per address space, memory chip and
group.

+ Space The names of the address spaces as defined in the

linker script file (tc*.lsl). The names are
constructed of the derivative name followed by a
colon ':', the core name, another colon ':' and the
space name. For example: spe:tc:linear

Chip The names of the memory chips as defined in the

linker script file (*.lsl) in the memory definitions.

Group Sections can be ordered in groups. These are the

names of the groups as defined in the linker script file
(*.lsl) with the keyword group in the
section_layout definition. The name that is
displayed is the name of the deepest nested group.

Section The name of the section. Names within square

brackets [ ] will be copied during initialization from
ROM to the corresponding section name in RAM.
LIST FILE FORMATS

Size (MAU) The size of the section in minimum addressable units.

Space addr The absolute address of the section in the address

space.

Chip addr The absolute offset of the section from the start of a
memory chip.

Locator Part: Symbol translation

This part of the map file lists all external symbols per address space name,
both sorted on symbol name and sorted on address.

Symbol The name of the symbol.

Address The absolute address of the symbol in the address

space.
 List File Formats 6-11

Space The names of the address spaces as defined in the

linker script file (tc*.lsl). The names are
constructed of the derivative name followed by a
colon ':', the core name, another colon ':' and the
space name. For example: spe:tc:linear

Memory Part
This part of the map file shows the memory usage in totals and
percentages for spaces and chips. The largest free block of memory per
space and per chip is also shown.

By default this part is not shown in the map file. You have to turn this part
on manually with linker option -mm (memory usage info).

Linker Script File Part

This part of the map file shows the processor and memory information of
the linker script file.

By default this part is not shown in the map file. You have to turn this part
on manually with linker option -ms (processor and memory info). You
can print this information to a separate file with linker option
--lsl-dump.

Locate Rule Part

This part of the map file shows the rules the linker uses to locate sections.

Address space The names of the address spaces as defined in the

linker script file (*.lsl). The names are constructed
of the derivative name followed by a colon ':', the
core name, another colon ':' and the space name.
For example: spe:tc:linear

Type The rule type:

ordered/contiguous/clustered Specifies how sections are

grouped.

absolute address The section must be located at the address

shown in the Properties column

address range The section must be located in the union of

the address ranges shown in the Properties
column; end addreses are not included in
the range.

• • • • • • • •
 6-12 TriCore Reference Manual

address range size The sections must be located in some

address range with size not larger than
shown in the Properties column; the second
number in that field is the alignment
requirement for the address range.

Properties The contents depends on the Type column.

Sections The sections to which the rule applies;

restrictions between sections are shown in this
column:
< ordered
| contiguous
+ clustered
For contiguous sections, the linker uses the section
order as shown here. Clustered sections can be located
in any relative order.

By default this part is not shown in the map file. You have to turn this part
on manually with linker option -mu (locate rules).

Related information
Section 7.9, Generating a Map File, in Chapter Using the Linker of the
User's Manual.
LIST FILE FORMATS

Linker option -M (Generate map file)

CHAPTER
OBJECT FILE
FORMATS

7
 7-2 TriCore Reference Manual

CHAPTER
7
OBJECT FORMATS
 Object File Formats 7-3

7.1 ELF/DWARF OBJECT FORMAT

The TriCore toolchain by default produces objects in the ELF/DWARF 2
(.elf) format.

The ELF/DWARF 2 Object Format for the TriCore toolchain follows the
convention as described in the TriCore Embedded Application Binary
Interface [2000, Infineon].

For a complete description of the ELF and DWARF formats, please refer to
the Tool Interface Standard (TIS).

• • • • • • • •
 7-4 TriCore Reference Manual

7.2 MOTOROLA S-RECORD FORMAT

With the linker option -ofilename:SREC option the linker produces output
in Motorola S-record format with three types of S-records: S0, S2 and S8.
With the options -ofilename:SREC:2 or -ofilename:SREC:4 option you
can force other types of S-records. They have the following layout:

S0 - record
'S' '0' <length_byte> <2 bytes 0> <comment> <checksum_byte>

A linker generated S-record file starts with a S0 record with the following
contents:

length_byte : 0x6
comment : ltc (TriCore linker)
checksum : 0xB6
l t c
S00600006C7463B6

The S0 record is a comment record and does not contain relevant

information for program execution.

The length_byte represents the number of bytes in the record, not

including the record type and length byte.
OBJECT FORMATS

The checksum is calculated by first adding the binary representation of the

bytes following the record type (starting with the length_byte) to just
before the checksum. Then the one's complement is calculated of this
sum. The least significant byte of the result is the checksum. The sum of
all bytes following the record type is 0xFF.

S1 - record
With the linker option -ofilename:SREC:2, the actual program code and
data is supplied with S1 records, with the following layout:

'S' '1' <length_byte> <address> <code bytes> <checksum_byte>

This record is used for 2-byte addresses.

 Object File Formats 7-5

Example:
S1130250F03EF04DF0ACE8A408A2A013EDFCDB00E6
| | | |_ checksum
| | |_ code
| |_ address
|_ length

The linker has an option that controls the length of the output buffer for
generating S1 records. The default buffer length is 32 code bytes.

The checksum calculation of S1 records is identical to S0.

S2 - record
With the linker option -ofilename:SREC:3, which is the default, the actual
program code and data is supplied with S2 records, with the following
layout:

'S' '2' <length_byte> <address> <code bytes> <checksum_byte>

For the TriCore the linker generates 3-byte addresses.

Example:
S213FF002000232222754E00754F04AF4FAE4E22BF
| | | |_ checksum
| | |_ code
| |_ address
|_ length

The linker has an option that controls the length of the output buffer for
generating S2 records. The default buffer length is 32 code bytes.

The checksum calculation of S2 records is identical to S0.

S3 - record
With the linker option -ofilename:SREC:4, the actual program code and
data is supplied with S3 records, with the following layout:

'S' '3' <length_byte> <address> <code bytes> <checksum_byte>

This record is used for 4-byte addresses.

• • • • • • • •
 7-6 TriCore Reference Manual

Example:
S3070000FFFE6E6825
| | | |_ checksum
| | |_ code
| |_ address
|_ length

The linker has an option that controls the length of the output buffer for
generating S3 records.

The checksum calculation of S3 records is identical to S0.

S7 - record
With the linker option -ofilename:SREC:4, at the end of an S-record file,
the linker generates an S7 record, which contains the program start
address. S7 is the corresponding termination record for S3 records.

Layout:

'S' '7' <length_byte> <address> <checksum_byte>

Example:
S70500006E6824
| | |_checksum
OBJECT FORMATS

| |_ address
|_ length

The checksum calculation of S7 records is identical to S0.

S8 - record
With the linker option -ofilename:SREC:3, which is the default, at the end
of an S-record file, the linker generates an S8 record, which contains the
program start address.

Layout:

'S' '8' <length_byte> <address> <checksum_byte>

Example:
S804FF0003F9
| | |_checksum
| |_ address
|_ length
 Object File Formats 7-7

The checksum calculation of S8 records is identical to S0.

S9 - record
With the linker option -ofilename:SREC:4, at the end of an S-record file,
the linker generates an S9 record, which contains the program start
address. S9 is the corresponding termination record for S1 records.

Layout:

'S' '9' <length_byte> <address> <checksum_byte>

Example:
S9030210EA
| | |_checksum
| |_ address
|_ length

The checksum calculation of S9 records is identical to S0.

• • • • • • • •
 7-8 TriCore Reference Manual

7.3 INTEL HEX RECORD FORMAT

Intel Hex records describe the hexadecimal object file format for 8-bit,
16-bit and 32-bit microprocessors. The hexadecimal object file is an ASCII
representation of an absolute binary object file. There are six different
types of records:
• Data Record (8-, 16, or 32-bit formats)
• End of File Record (8-, 16, or 32-bit formats)
• Extended Segment Address Record (16, or 32-bit formats)
• Start Segment Address Record (16, or 32-bit formats)
• Extended Linear Address Record (32-bit format only)
• Start Linear Address Record (32-bit format only)
For the TriCore the linker generates records in the 32-bit format (4-byte
addresses with linker option -ofilename:IHEX).

General Record Format

In the output file, the record format is:

ÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁ
ÁÁÁÁ
ÁÁÁ
:
ÁÁÁÁ
ÁÁÁÁ ÁÁÁ
ÁÁÁÁ ÁÁÁÁÁ
ÁÁÁ ÁÁÁÁÁ
length

ÁÁÁÁÁ
ÁÁÁÁÁ
offset type content checksum
OBJECT FORMATS

Where:

: is the record header.

length is the record length which specifies the number of bytes of

the content field. This value occupies one byte (two
hexadecimal digits). The linker outputs records of 255 bytes
(32 hexadecimal digits) or less; that is, length is never greater
than 0xFF.

offset is the starting load offset specifying an absolute address in

memory where the data is to be located when loaded by a
tool. This field is two bytes long. This field is only used for
Data Records. In other records this field is coded as four
ASCII zero characters ('0000').

type is the record type. This value occupies one byte (two
hexadecimal digits). The record types are:
 Object File Formats 7-9

Byte Type Record type

00 Data
01 End of File
02 Extended segment address (not used)
03 Start segment address (not used)
04 Extended linear address (32-bit)
05 Start linear address (32-bit)

content is the information contained in the record. This depends on

the record type.

checksum is the record checksum. The linker computes the checksum

by first adding the binary representation of the previous
bytes (from length to content). The linker then computes the
result of sum modulo 256 and subtracts the remainder from
256 (two's complement). Therefore, the sum of all bytes
following the header is zero.

Extended Linear Address Record

The Extended Linear Address Record specifies the two most significant
bytes (bits 16-31) of the absolute address of the first data byte in a
subsequent Data Record:

ÁÁÁ
ÁÁÁ
ÁÁÁÁ
ÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁ
ÁÁÁ
ÁÁÁ ÁÁÁÁ
ÁÁÁ
:
ÁÁÁ
ÁÁÁÁ ÁÁÁÁÁÁÁ
ÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁÁÁ
02

ÁÁÁÁÁ
0000 04 upper_address checksum

The 32-bit absolute address of a byte in a Data Record is calculated as:

( address + offset + index ) modulo 4G

where:

address is the base address, where the two most significant bytes are
the upper_address and the two least significant bytes are
zero.

offset is the 16-bit offset from the Data Record.

index is the index of the data byte within the Data Record (0 for
the first byte).

• • • • • • • •
 7-10 TriCore Reference Manual

Example:
:0200000400FFFB
| | | | |_ checksum
| | | |_ upper_address
| | |_ type
| |_ offset
|_ length

Data Record
The Data Record specifies the actual program code and data.

ÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁ
ÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁ
ÁÁÁÁ
ÁÁÁ
: ÁÁÁÁ
ÁÁÁÁ ÁÁÁ
ÁÁÁÁ ÁÁÁÁ
ÁÁÁ ÁÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁÁ
length offset 00 data checksum

The length byte specifies the number of data bytes. The linker has an
option that controls the length of the output buffer for generating Data
records. The default buffer length is 32 bytes.

The offset is the 16-bit starting load offset. Together with the address
specified in the Extended Address Record it specifies an absolute address
in memory where the data is to be located when loaded by a tool.

Example:
OBJECT FORMATS

:0F00200000232222754E00754F04AF4FAE4E22C3
| | | | |_ checksum
| | | |_ data
| | |_ type
| |_ offset
|_ length
 Object File Formats 7-11

Start Linear Address Record

The Start Linear Address Record contains the 32-bit program execution
start address.

Layout:

ÁÁÁ
ÁÁÁ
ÁÁÁÁ
ÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁ
ÁÁÁ
ÁÁÁ ÁÁÁÁ
ÁÁÁ
:
ÁÁÁ
ÁÁÁÁ ÁÁÁÁÁ
ÁÁÁ ÁÁÁÁÁ
04

ÁÁÁÁÁ
ÁÁÁÁÁ
0000 05 address checksum

Example:
:0400000500FF0003F5
| | | | |_ checksum
| | | |_ address
| | |_ type
| |_ offset
|_ length

End of File Record

The hexadecimal file always ends with the following end-of-file record:
:00000001FF
| | | |_ checksum
| | |_ type
| |_ offset
|_ length

• • • • • • • •
 7-12 TriCore Reference Manual
OBJECT FORMATS
CHAPTER
LINKER SCRIPT
LANGUAGE

8
 8-2
LINKER SCRIPT LANGUAGE

8
CHAPTER
TriCore Reference Manual
 Linker Script Language 8-3

8.1 INTRODUCTION
To make full use of the linker, you can write a script with information
about the architecture of the target processor and locating information.
The language for the script is called the Linker Script Language (LSL). This
chapter first describes the structure of an LSL file. The next section
contains a summary of the LSL syntax. Finally, in the remaining sections,
the semantics of the Linker Script Language is explained.

The TASKING linker is a target independent linker/locator that can

simultaneously link and locate all programs for all cores available on a
target board. The target board may be of arbitrary complexity. A simple
target board may contain one standard processor with some external
memory that executes one task. A complex target board may contain
multiple standard processors and DSPs combined with configurable
IP-cores loaded in an FPGA. Each core may execute a different program,
and external memory may be shared by multiple cores.

LSL serves two purposes. First it enables you to specify the characteristics
(that are of interest to the linker) of your specific target board and of the
cores installed on the board. Second it enables you to specify how
sections should be located in memory.

8.2 STRUCTURE OF A LINKER SCRIPT FILE

A script file consists of several definitions. The definitions can appear in
any order.

The architecture definition (required)

In essence an architecture definition describes how the linker should
convert logical addresses into physical addresses for a given type of core.
If the core supports multiple address spaces, then for each space the linker
must know how to perform this conversion. In this context a physical
address is an offset on a given internal or external bus. Additionally the
architecture definition contains information about items such as the
(hardware) stack and the interrupt vector table.

This specification is normally written by Altium. The architecture definition

of the LSL file should not be changed by you unless you also modify the
core's hardware architecture. If the LSL file describes a multi-core system
an architecture definition must be available for each different type of core.

• • • • • • • •
 8-4 TriCore Reference Manual

See section 8.5, Semantics of the Architecture Definition for detailed

descriptions of LSL in the architecture definition.

The derivative definition (required)

The derivative definition describes the configuration of the internal
(on-chip) bus and memory system. Basically it tells the linker how to
convert offsets on the buses specified in the architecture definition into
offsets in internal memory. A derivative definition must be present in an
LSL file. Microcontrollers and DSPs often have internal memory and I/O
sub-systems apart from one or more cores. The design of such a chip is
called a derivative.

Altium provides LSL descriptions of supported derivatives, along with "SFR

files", which provide easy access to registers in I/O sub-systems from C
and assembly programs. When you build an ASIC or use a derivative that
LINKER SCRIPT LANGUAGE

is not (yet) supported by the TASKING tools, you may have to write a
derivative definition.

When you want to use multiple cores of the same type, you must
instantiate the cores in a derivative definition, since the linker
automatically instantiates only a single core for an unused architecture.

See section 8.6, Semantics of the Derivative Definition for a detailed

description of LSL in the derivative definition.

The processor definition

The processor definition describes an instance of a derivative. A processor
definition is only needed in a multi-processor embedded system. It allows
you to define multiple processors of the same type.

See section 8.7, Semantics of the Board Specification for a detailed

description of LSL in the processor definition.

The memory and bus definitions (optional)

Memory and bus definition are used within the context of a derivative
definition to specify internal memory and on-chip buses. In the context of
a board specification the memory and bus definitions are used to define
external (off-chip) memory and buses. Given the above definitions the
linker can convert a logical address into an offset into an on-chip or
off-chip memory device.
 Linker Script Language 8-5

See section 8.7.3, Defining External Memory and Buses, for more
information on how to specify the external physical memory layout.
Internal memory for a processor should be defined in the derivative
definition for that processor.

The board specification

The processor definition and memory and bus definitions together form a
board specification. LSL provides language constructs to easily describe
single-core and heterogeneous or homogeneous multi-core systems. The
board specification describes all characteristics of your target board's
system buses, memory devices, I/O sub-systems, and cores that are of
interest to the linker. Based on the information provided in the board
specification the linker can for each core:
• convert a logical address to a physical addresses (offsets within a
memory device)
• locate sections in physical memory
• maintain an overall view of the used and free physical memory within
the whole system while locating

The section layout definition (optional)

The optional section layout definition enables you to exactly control
where input sections are located. Features are provided such as: the
ability to place sections at a given load-address or run-time address, to
place sections in a given order, and to overlay code and/or data sections.

Which object files (sections) constitute the task that will run on a given
core is specified on the command line when you invoke the linker. The
linker will link and locate all sections of all tasks simultaneously. From the
section layout definition the linker can deduce where a given section may
be located in memory, form the board specification the linker can deduce
which physical memory is (still) available while locating the section.

See section 8.8, Semantics of the Section Layout Definition,, for more
information on how to locate a section at a specific place in memory.

Skeleton of a Linker Script File

The skeleton of a linker script file now looks as follows:
architecture architecture_name
{
architecture definition
}

• • • • • • • •
 8-6 TriCore Reference Manual

derivative derivative_name
{
derivative definition
}

processor processor_name
{
processor definition
}

memory definitions and/or bus definitions

section_layout space_name
{
section placement statements
}
LINKER SCRIPT LANGUAGE

8.3 SYNTAX OF THE LINKER SCRIPT LANGUAGE

8.3.1 PREPROCESSING
When the linker loads an LSL file, the linker processes it with a C-style
prepocessor. As such, it strips C and C++ comments. You can use the
standard ISO C preprocessor directives, such as #include, #define,
#if/#else/#endif .

For example:
#include "arch.lsl"

Preprocess and include the file arch.lsl at this point in the LSL file.
 Linker Script Language 8-7

8.3.2 LEXICAL SYNTAX

The following lexicon is used to describe the syntax of the Linker Script
Language:

A ::= B = A is defined as B
A ::= B C = A is defined as B and C; B is followed by C
A ::= B | C = A is defined as B or C
<B>0|1 = zero or one occurrence of B
<B>>=0 = zero of more occurrences of B
<B>>=1 = one of more occurrences of B

IDENTIFIER = a character sequence starting with 'a'-'z', 'A'-'Z' or '_'

Following characters may also be digits and dots '.'
STRING = sequence of characters not starting with \n, \r or \t
DQSTRING = " STRING " (double quoted string)
OCT_NUM = octal number, starting with a zero (06, 045)
DEC_NUM = decimal number, not starting with a zero (14, 1024)
HEX_NUM = hexadecimal number, starting with '0x' (0x0023, 0xFF00)

OCT_NUM, DEC_NUM and HEX_NUM can be followed by a k (kilo), M

(mega), or G (giga).

Characters in bold are characters that occur literally. Words in italics are
higher order terms that are defined in the same or in one of the other
sections.

To write comments in LSL file, you can use the C style '/* */' or C++
style '//'.

8.3.3 IDENTIFIERS
arch_name ::= IDENTIFIER
bus_name ::= IDENTIFIER
core_name ::= IDENTIFIER
derivative_name ::= IDENTIFIER
file_name ::= DQSTRING
group_name ::= IDENTIFIER
mem_name ::= IDENTIFIER
proc_name ::= IDENTIFIER
section_name ::= DQSTRING
space_name ::= IDENTIFIER
stack_name ::= section_name
symbol_name ::= DQSTRING

• • • • • • • •
 8-8 TriCore Reference Manual

8.3.4 EXPRESSIONS
The expressions and operators in this section work the same as in ANSI C.
number ::= OCT_NUM
| DEC_NUM
| HEX_NUM

expr ::= number

| symbol_name
| unary_op expr
| expr binary_op expr
| expr ? expr : expr
| ( expr )
| function_call

unary_op ::= ! // logical NOT

LINKER SCRIPT LANGUAGE

| ~ // bitwise complement
| - // negative value

binary_op ::= ^ // exclusive OR

| * // multiplication
| / // division
| % // modulus
| + // addition
| - // subtraction
| >> // right shift
| << // left shift
| == // equal to
| != // not equal to
| > // greater than
| < // less than
| >= // greater than or equal to
| <= // less than or equal to
| & // bitwise AND
| | // bitwise OR
| && // logical AND
| || // logical OR
 Linker Script Language 8-9

8.3.5 BUILT-IN FUNCTIONS

function_call ::= absolute ( expr )
| addressof ( addr_id )
| exists ( section_name )
| max ( expr , expr )
| min ( expr , expr )
| sizeof ( size_id )

addr_id ::= sect : section_name

| group : group_name

size_id ::= group : group_name

| mem : mem_name
| sect : section_name
• Every space, bus, memory, section or group your refer to, must be
defined in the LSL file.
• The addressof() and sizeof() functions with the group or
sect argument can only be used in the right hand side of an
assignment. The sizeof() function with the mem argument can be
used anywhere in section layouts.
You can use the following built-in functions in expressions. All functions
return a numerical value. This value is a 64-bit signed integer.

absolute()

int absolute( expr )

Converts the value of expr to a positive integer.

absolute( "labelA"-"labelB" )

addressof()

int addressof( addr_id )

Returns the address of addr_id, which is a named section or group. To get

the offset of the section with the name asect:
addressof( sect: "asect")

This function only works in assignments.

• • • • • • • •
 8-10 TriCore Reference Manual

exists()

int exists( section_name )

The function returns 1 if the section section_name exists in one or more

object file, 0 otherwise. If the section is not present in input object files,
but generated from LSL, the result of this function is undefined.

To check whether the section mysection exists in one of the object files
that is specified to the linker:
exists( "mysection" )

max()
LINKER SCRIPT LANGUAGE

int max( expr, expr )

Returns the value of the expression that has the largest value. To get the
highest value of two symbols:
max( "sym1" , "sym2")

min()

int min( expr, expr )

Returns the value of the expression hat has the smallest value. To get the
lowest value of two symbols:
min( "sym1" , "sym2")

sizeof()

int sizeof( size_id )

Returns the size of the object (group, section or memory) the identifier
refers to. To get the size of the section "asection":
sizeof( sect: "asection" )

The group and sect arguments only works in assignments. The mem
argument can be used anywhere in section layouts.
 Linker Script Language 8-11

8.3.6 LSL DEFINITIONS IN THE LINKER SCRIPT FILE

description ::= <definition>>=1

definition ::= architecture_definition

| derivative_definition
| board_spec
| section_definition
• At least one architecture_definition must be present in the
LSL file.

8.3.7 MEMORY AND BUS DEFINITIONS

mem_def ::= memory mem_name { <mem_descr ;>>=0 }
• A mem_def defines a memory with the mem_name as a unique
name.
mem_descr ::= type = <reserved>0|1 mem_type
| mau = expr
| size = expr
| speed = number
| mapping
• A mem_def contains exactly one type statement.
• A mem_def contains exactly one mau statement (non-zero size).
• A mem_def contains exactly one size statement.
• A mem_def contains zero or one speed statement
(default value is 1).
• A mem_def contains at least one mapping.
mem_type ::= rom // attrs = rx
| ram // attrs = rw
| nvram // attrs = rwx

bus_def ::= bus bus_name { <bus_descr ;>>=0 }

• A bus_def statement defines a bus with the given bus_name as a
unique name within a core architecture.
bus_descr ::= mau = expr
| width = expr // bus width, nr
| // of data bits
| mapping // legal destination
// 'bus' only

• • • • • • • •
 8-12 TriCore Reference Manual

• The mau and width statements appear exactly once in a

bus_descr. The default value for width is the mau size.
• The bus width must be an integer times the bus MAU size.
• The MAU size must be non-zero.
• A bus can only have a mapping on a destination bus (through
dest = bus: ).
mapping ::= map ( map_descr <, map_descr>>=0 )

map_descr ::= dest = destination

| dest_dbits = range
| dest_offset = expr
| size = expr
| src_dbits = range
| src_offset = expr
LINKER SCRIPT LANGUAGE

• A mapping requires at least the size and dest statements.

• Each map_descr can occur only once.
• You can define multiple mappings from a single source.
• Overlap between source ranges or destination ranges is not allowed.
• If the src_dbits or dest_dbits statement is not present, its value
defaults to the width value if the source/destination is a bus, and to
the mau size otherwise.
destination ::= space : space_name
| bus : <proc_name |
core_name :>0|1 bus_name
• A space_name refers to a defined address space.
• A proc_name refers to a defined processor.
• A core_name refers to a defined core.
• A bus_name refers to a defined bus.
• The following mappings are allowed (source to destination)
- space => space
- space => bus
- bus => bus
- memory => bus

range ::= number .. number

 Linker Script Language 8-13

8.3.8 ARCHITECTURE DEFINITION

architecture_definition
::= architecture arch_name
<( parameter_list )>0|1
<extends arch_name
<( argument_list )>0|1 >0|1
{ arch_spec>=0 }
• An architecture_definition defines a core architecture with
the given arch_name as a unique name.
• At least one space_def and at least one bus_def have to be
present in an architecture_definition .
• An architecture_definition that uses the extends construct
defines an architecture that inherits all elements of the architecture
defined by the second arch_name. The parent architecture must
be defined in the LSL file as well.
parameter_list ::= parameter <, parameter>>=0

parameter ::= IDENTIFIER <= expr>0|1

argument_list ::= expr <, expr>>=0

arch_spec ::= bus_def

| space_def
| endianness_def

space_def ::= space space_name { <space_descr;>>=0 }

• A space_def defines an address space with the given
space_name as a unique name within an architecture.
space_descr ::= space_property ;
| section_definition //no space ref

space_property ::= id = number // as used in object

| mau = expr
| align = expr
| page_size = expr
| stack_def
| heap_def
| copy_table_def
| start_address
| mapping
• A space_def contains exactly one id and one mau statement.

• • • • • • • •
 8-14 TriCore Reference Manual

• A space_def contains at most one align statement.

• A space_def contains at most one page_size statement.
• A space_def contains at least one mapping.
stack_def ::= stack stack_name ( stack_heap_descr
<, stack_heap_descr >>=0 )
• A stack_def defines a stack with the stack_name as a unique
name.
heap_def ::= heap heap_name ( stack_heap_descr
<, stack_heap_descr >>=0 )
• A heap_def defines a heap with the heap_name as a unique
name.
copy_table_def ::= copytable ( copy_table_descr
<, copy_table_descr>>=0 )
LINKER SCRIPT LANGUAGE

• A space_def contains at most one copytable statement.

• If the architecture definition contains more than one address space,
exactly one copy table must be defined in one of the spaces. If the
the architecture definition contains only one address space, a copy
table definition is optional (it will be generated in the space).
stack_heap_descr ::= min_size = expr
| grows = direction
| align = expr
| fixed
• The min_size statement must be present.
• You can specify at most one align statement and one grows
statement.
direction ::= low_to_high
| high_to_low
• If you do not specify the grows statement, the stack and grow
low-to-high .
copy_table_descr ::= align = expr
| copy_unit = expr
| dest <space_name>0|1 = space_name
• The copy_unit is defined by the size in MAUs in which the startup
code moves data.
• The dest statement is only required when the startup code
initializes memory used by another processor that has no access to
ROM.
 Linker Script Language 8-15

• A space_name refers to a defined address space.

start_addr ::= start_address ( start_addr_descr
<, start_addr_descr>>=0 )

start_addr_descr ::= run_addr = expr

| symbol = symbol_name
• A symbol_name refers to the section that contains the startup code.
endianness_def ::= endianness { <endianness_type;>>=1 }

endianness_type ::= big

| little

8.3.9 DERIVATIVE DEFINITION

derivative_definition
::= derivative derivative_name
<( parameter_list )>0|1
<extends derivative_name
<( argument_list )>0|1 >0|1
{ <derivative_spec>>=0 }
• A derivative_definition defines a derivative with the given
derivative_name as a unique name.
• At least one core_def must be present in a
derivative_definition .
derivative_spec ::= core_def
| bus_def
| mem_def
| section_definition // no processor
// name

core_def ::= core core_name { <core_descr ;>>=0 }

• A core_def defines a core with the given core_name as a unique
name.
core_descr ::= architecture = arch_name
<( argument_list )>0|1
| endianness = ( endianness_type
<, endianness_type>>=0 )
• An arch_name refers to a defined core architecture.

• • • • • • • •
 8-16 TriCore Reference Manual

• Exactly one architecture statement must be present in a

core_def.

8.3.10 PROCESSOR DEFINITION AND BOARD

SPECIFICATION
board_spec ::= proc_def
| bus_def
| mem_def

proc_def ::= processor proc_name

{ proc_descr ; }

proc_descr ::= derivative = derivative_name

<( argument_list )>0|1
LINKER SCRIPT LANGUAGE

• A proc_def defines a processor with the proc_name as a unique

name.
• If you do not explicitly define a processor for a derivative in an LSL
file, the linker defines a processor with the same name as that
derivative.
• A derivative_name refers to a defined derivative.
• A proc_def contains exactly one derivative statement.

8.3.11 SECTION PLACEMENT DEFINITION

section_definition ::= section_layout <space_ref>0|1
<( locate_direction )>0|1
{ <section_statement>>=0 }
• A section definition inside a space definition does not have a
space_ref.
• All global section definitions have a space_ref.
space_ref ::= <proc_name>0|1 : <core_name>0|1
: space_name

• If more than one processor is present, the proc_name must be

given for a global section layout.
• If the section layout refers to a processor that has more than one
core, the core_name must be given in the space_ref.
• A proc_name refers to a defined processor.
 Linker Script Language 8-17

• A core_name refers to a defined core.

• A space_name refers to a defined address space.
locate_direction ::= direction = direction

direction ::= low_to_high

| high_to_low
• A section layout contains at most one direction statement.
• If you do not specify the direction statement, the locate direction
of the section layout is low-to-high.
section_statement
::= simple_section_statement ;
| aggregate_section_statement

simple_section_statement
::= assignment
| select_section_statement
| special_section_statement

assignment ::= symbol_name assign_op expr

assign_op ::= =
| :=

select_section_statement
::= select <section_name>0|1
<section_selections>0|1
• Either a section_name or at least one section_selection must
be defined.
section_selections
::= ( section_selection
<, section_selection>>=0 )

section_selection
::= attributes = < <+|-> attribute>>0
• +attribute means: select all sections that have this attribute.
• -attribute means: select all sections that do not have this
attribute.

• • • • • • • •
 8-18 TriCore Reference Manual

special_section_statement
::= heap stack_name <size_spec>0|1
| stack stack_name <size_spec>0|1
| copytable
| reserved <section_name>0|1
<reserved_specs>0|1
• Special sections cannot be selected in load-time groups.
size_spec ::= ( size = expr )

reserved_specs ::= ( reserved_spec

<, reserved_spec>>=0 )

reserved_spec ::= attributes

| fill_spec
| size = expr
LINKER SCRIPT LANGUAGE

| alloc_allowed = absolute
• If a reserved section has attributes r, rw, x, rx or rwx, and no fill
pattern is defined, the section is filled with zeros. If no attributes are
set, the section is created as a scratch section (attributes ws, no
image).
aggregate_section_statement
::= { <section_statement>>=0 }
| group_descr
| if_statement
| section_creation_statement

group_descr ::= group <group_name>0|1

<( group_specs )>0|1
section_statement
• No two groups for an address space can have the same
group_name.
group_specs ::= group_spec <, group_spec >>=0

group_spec ::= group_alignment

| attributes
| group_load_address
| fill <= fill_values>0|1
| group_page
| group_run_address
| group_type
| allow_cross_references
 Linker Script Language 8-19

• The allow-cross-references property is only allowed for

overlay groups.
• Sub groups inherit all properties from a parent group.
group_alignment ::= align = expr

attributes ::= attributes = <attribute>>=1

group_load_address
::= load_addr <= load_or_run_addr>0|1

fill_spec ::= fill = fill_values

fill_values ::= expr

| [ expr <, expr>>=0 ]

group_page ::= page <= expr>0|1

group_run_address ::= run_addr <= load_or_run_addr>0|1

group_type ::= clustered

| contiguous
| ordered
| overlay
• For non-contiguous groups, you can only specify
group_alignment and attributes.
• The overlay keyword also sets the contiguous property.
• The clustered property cannot be set together with contiguous
or ordered on a single group.
attribute ::= r // read-only sections
| w // read/write sections
| x // executable code sections
| i // initialized sections
| s // scratch sections
| b // blanked (cleared) sections

load_or_run_addr ::= addr_absolute

| addr_range <| addr_range>>=0

addr_absolute ::= expr

| memory_reference [ expr ]
• An absolute address can only be set on ordered groups.
addr_range ::= [ expr .. expr ]
| memory_reference
| memory_reference [ expr .. expr ]

• • • • • • • •
 8-20 TriCore Reference Manual

• The parent of a group with an addr_range or page restriction

cannot be ordered, contiguous or clustered.
memory_reference ::= mem : <proc_name :>0|1
<core_name :>0|1 mem_name
• A proc_name refers to a defined processor.
• A core_name refers to a defined core.
• A mem_name refers to a defined memory.
if_statement ::= if ( expr ) section_statement
<else section_statement>0|1

section_creation_statement
::= section section_name
( <section_spec>0|1 )
{ <select_section_statement ;>>=0 }
LINKER SCRIPT LANGUAGE

section_spec ::= attributes

| fill_spec
| size = expr

8.4 EXPRESSION EVALUATION

Only constant expressions are allowed, including sizes, but not addresses,
of sections in object files.

All expressions are evaluated with 64-bit precision integer arithmetic. The
result of an expression can be absolute or relocatable. A symbol you
assign is created as an absolute symbol.
 Linker Script Language 8-21

8.5 SEMANTICS OF THE ARCHITECTURE DEFINITION

Keywords in the architecture definition

architecture
extends
endianness big little
bus
mau
width
map
space
id
mau
align
page_size
stack
min_size
grows low_to_high high_to_low
align
fixed
heap
min_size
grows low_to_high high_to_low
align
fixed
copytable
align
copy_unit
dest
start_address
run_addr
symbol
map

map
dest bus space
dest_dbits
dest_offset
size
src_dbits
src_offset

• • • • • • • •
 8-22 TriCore Reference Manual

8.5.1 DEFINING AN ARCHITECTURE

With the keyword architecture you define an architecture and assign a
unique name to it. The name is used to refer to it at other places in the
LSL file:
architecture name
{
definitions
}

If you are defining multiple core architectures that show great

resemblance, you can define the common features in a parent core
architecture and extend this with a child core architecture that contains
specific features. The child inherits all features of the parent. With the
keyword extends you create a child core architecture:
LINKER SCRIPT LANGUAGE

architecture name_child_arch extends name_parent_arch

{
definitions
}

A core architecture can have any number of parameters. These are

identifiers which get values assigned on instantiation or extension of the
architecture. You can use them in any expression within the core
architecture. Parameters can have default values, which are used when the
core architecture is instantiated with less arguments than there are
parameters defined for it. When you extend a core architecture you can
pass arguments to the parent architecture. Arguments are expressions that
set the value of the parameters of the sub-architecture.
architecture name_child_arch (parm1,parm2=1)
extends name_parent_arch (arguments)
{
definitions
}
 Linker Script Language 8-23

8.5.2 DEFINING INTERNAL BUSES

With the bus keyword you define a bus (the combination of data and
corresponding address bus). The bus name is used to identify a bus and
does not conflict with other identifiers. Bus descriptions in an architecture
definition or derivative definition define internal buses. Some internal
buses are used to communicate with the components outside the core or
processor. Such buses on a processor have physical pins reserved for the
number of bits specified with the width statements.
• The mau field specifies the MAU size (Minimum Addressable Unit) of
the data bus. This field is required.
• The width field specifies the width (number of address lines) of the
data bus. The default value is the MAU size.
• The map keyword specifies how this bus maps onto another bus (if so).
Mappings are described in section 8.5.4, Mappings.
bus bus_name
{
mau = 8;
width = 8;
map ( map_description );
}

8.5.3 DEFINING ADDRESS SPACES

With the space keyword you define a logical address space. The space
name is used to identify the address space and does not conflict with other
identifiers.
• The id field defines how the addressing space is identified in object
files. In general, each address space has a unique ID. The linker locates
sections with a certain ID in the address space with the same ID. This
field is required. In IEEE this ID is specified explicitly for sections and
symbols, ELF sections map by default to the address space with ID 1.
Sections with one of the special names defined in the ABI (Application
Binary Interface) may map to different address spaces.
• The mau field specifies the MAU size (Minimum Addressable Unit) of
the space. This field is required.
• The align value must be a power of two. The linker uses this value to
compute the start addresses when sections are concatenated. An align
value of n means that objects in the address space have to be aligned
on n MAUs.

• • • • • • • •
 8-24 TriCore Reference Manual

• The page_size field sets the page size in MAUs for the address space.
It must be a power of 2. The default page size is 1. See also the page
keyword in subsection Locating a group in section 8.8.2, Creating and
Locating Groups of Sections.
• The map keyword specifies how this address space maps onto an
internal bus or onto another address space. Mappings are described in
section 8.5.4, Mappings.

Stacks and heaps

• The stack keyword defines a stack in the address space and assigns a
name to it. The architecture definition must contain at least one stack
definition. Each stack of a core architecture must have a unique name.
See also the stack keyword in section 8.8.3, Creating or Modifying
Special Sections.
The stack is described in terms of a minimum size (min_size) and the
LINKER SCRIPT LANGUAGE

direction in which the stack grows (grows). This can be either from
low_to_high addresses (stack grows upwards, this is the default) or
from high_to_low addresses (stack grows downwards). The
min_size is required.

By default, the linker tries to maximize the size of the stacks and heaps.
After locating all sections, the largest remaining gap in the space is
used completely for the stacks and heaps. If you specify the keyword
fixed, you can disable this so-called 'balloon behavior'. The size is
also fixed if you used a stack or heap in the software layout definition
in a restricted way. For example when you override a stack with
another size or select a stack in an ordered group with other sections.

Optionally you can specify an alignment for the stack with the
argument align. This alignment must be equal or larger than the
alignment that you specify for the address space itself.
• The heap keyword defines a heap in the address space and assigns a
name to it. The definition of a heap is similar to the definition of a
stack. See also the heap keyword in section 8.8.3, Creating or
Modifying Special Sections.

See section 8.8, Semantics of the Section Layout Definition for

information on creating and placing stack sections.
 Linker Script Language 8-25

Copy tables
• The copytable keyword defines a copy table in the address space.
The content of the copy table is created by the linker and contains the
start address and size of all sections that should be initialized by the
startup code. If the architecture definition contains more than one
address space, you must define exactly one copy table in one of the
address spaces. If the architecture definition contains only one address
space, the copy table definition is optional.
Optionally you can specify an alignment for the copy table with the
argument align. This alignment must be equal or larger than the
alignment that you specify for the address space itself. If smaller, the
alignment for the address space is used.

The copy_unit argument specifies the size in MAUs of information

chunks that are copied. If you do not specify the copy unit, the MAU
size of the address space itself is used.

The dest argument specifies the destination address space that the
code uses for the copy table. The linker uses this information to
generate the correct addresses in the copy table. The memory into
where the sections must be copied at run-time, must be accessible
from this destination space.

Start address
• The start_address keyword specifies the start address for the
position where the C startup code is located. When a processor is reset,
it initializes its program counter to a certain start address, sometimes
called the reset vector. In the architecture definition, you must specify
this start address in the correct address space in combination with the
name of the label in the application code which must be located here.
The run_addr argument specifies the start address (reset vector). If the
core starts executing using an entry from a vector table, and directly
jumps to the start label, you should omit this argument.

The symbol argument specifies the name of the label in the

application code that should be located at the specified start address.
The symbol argument is required. The linker will resolve the start
symbol and use its value after locating for the start address field in
IEEE-695 files and Intel Hex files. If you also specified the run_addr
argument, the start symbol (label) must point to a section. The linker
locates this section such that the start symbol ends up on the start
address.

• • • • • • • •
 8-26 TriCore Reference Manual

space space_name
{
id = 1;
mau = 8;
align = 8;
page_size = 1;
stack name (min_size = 1k, grows = low_to_high);
start_address ( run_addr = 0x0000,
symbol = "start_label" )
map ( map_description );
}

8.5.4 MAPPINGS
You can use a mapping when you define a space, bus or memory. With
LINKER SCRIPT LANGUAGE

the map field you specify how addresses from the source (space, bus or
memory) are translated to addresses of a destination (space, bus). The
following mappings are possible:
• space => space
• space => bus
• bus => bus
• memory => bus
With a mapping you specify a range of source addresses you want to map
(specified by a source offset and a size), the destination to which you
want to map them (a bus or another address space), and the offset address
in the destination.
• The dest argument specifies the destination. This can be a bus or
another address space (only for a space to space mapping). This
argument is required.
• The src_offset argument specifies the offset of the source addresses.
In combination with size, this specifies the range of address that are
mapped. Default the source offset is 0x0000.
• The size argument specifies the number of addresses that are
mapped. This argument is required.
• The dest_offset argument specifies the position in the destination to
which the specified range of addresses is mapped. Default the
destination offset is 0x0000.
 Linker Script Language 8-27

If you are mapping a bus to another bus, the number of data lines of each
bus may differ. In this case you have to specify a range of source data
lines you want to map (src_dbits = begin..end) and the range of
destination data lines you want to map them to (dest_dbits =
first..last).
• The src_dbits argument specifies a range of data lines of the source
bus. Default all data lines are mapped.
• The dest_dbits argument specifies a range of data lines of the
destination bus. Default, all data lines from the source bus are mapped
on the data lines of the destination bus (starting with line 0).

From space to space

If you map an address space to another address space (nesting), you can
do this by mapping the subspace to the containing larger space. In this
example a small space of 64k is mapped on a large space of 16M.
space small
{
id = 2;
mau = 4;
map (src_offset = 0, dest_offset = 0,
dest = space : large, size = 64k);
}

From space to bus

All spaces that are not mapped to another space must map to a bus in the
architecture:
space large
{
id = 1;
mau = 4;
map (src_offset = 0, dest_offset = 0,
dest = bus:bus_name, size = 16M );
}

From bus to bus

The next example maps an external bus called e_bus to an internal bus
called i_bus. This internal bus resides on a core called mycore. The
source bus has 16 data lines whereas the destination bus has only 8 data
lines. Therefore, the keywords src_dbits and dest_dbits specify
which source data lines are mapped on which destination data lines.

• • • • • • • •
 8-28 TriCore Reference Manual

architecture mycore
{
bus i_bus
{
mau = 4;
}

space i_space
{
map (dest=bus:i_bus, size=256);
}
}

bus e_bus
{
mau = 16;
LINKER SCRIPT LANGUAGE

width = 16;
map (dest = bus:mycore:i_bus,
src_dbits = 0..7, dest_dbits = 0..7 )
}

It is not possible to map an internal bus to an external bus.

 Linker Script Language 8-29

8.6 SEMANTICS OF THE DERIVATIVE DEFINITION

Keywords in the derivative definition

derivative
extends
core
architecture
bus
mau
width
map
memory
type rom ram nvram
mau
size
speed
map

map
dest bus space
dest_dbits
dest_offset
size
src_dbits
src_offset

8.6.1 DEFINING A DERIVATIVE

With the keyword derivative you define a derivative and assign a
unique name to it. The name is used to refer to it at other places in the
LSL file:
derivative name
{
definitions
}

• • • • • • • •
 8-30 TriCore Reference Manual

If you are defining multiple derivatives that show great resemblance, you
can define the common features in a parent derivative and extend this
with a child derivative that contains specific features. The child inherits all
features of the parent (cores and memories). With the keyword extends
you create a child derivative:
derivative name_child_deriv extends name_parent_deriv
{
definitions
}

As with a core architecture, a derivative can have any number of

parameters. These are identifiers which get values assigned on
instantiation or extension of the derivative. You can use them in any
expression within the derivative definition.
LINKER SCRIPT LANGUAGE

derivative name_child_deriv (parm1,parm2=1)

extends name_parent_derivh (arguments)
{
definitions
}

8.6.2 INSTANTIATING CORE ARCHITECTURES

With the keyword core you instantiate a core architecture in a derivative.
• With the keyword architecture you tell the linker that the given
core has a certain architecture. The architecture name refers to an
existing architecture definition in the same LSL file.
For example, if you have two cores (called mycore_1 and mycore_2)
that have the same architecture (called mycorearch), you must
instantiate both cores as follows:
core mycore_1
{
architecture = mycorearch;
}

core mycore_2
{
architecture = mycorearch;
}
 Linker Script Language 8-31

If the architecture definition has parameters you must specify the

arguments that correspond with the parameters. For example
mycorearch1 expects two parameters which are used in the
architecture definition:
core mycore
{
architecture = mycorearch1 (1,2);
}

8.6.3 DEFINING INTERNAL MEMORY AND BUSES

With the memory keyword you define physical memory that is present on
the target board. The memory name is used to identify the memory and
does not conflict with other identifiers. It is common to define internal
memory (on-chip) in the derivative definition. External memory (off-chip
memory) is usually defined in the board specification (See section 8.7.3,
Defining External Memory and Buses).
• The type field specifies a memory type:
- rom: read only memory
- ram: random access memory
- nvram: non volatile ram
The optional reserved qualifier before the memory type, tells the
linker not to locate any section in the memory by default. You can
locate sections in such memories using an absolute address or range
restriction (see subsection Locating a group in section 8.8.2, Creating
and Locating Groups of Sections).
• The mau field specifies the MAU size (Minimum Addressable Unit) of
the memory. This field is required.
• The size field specifies the size in MAU of the memory. This field is
required.
• The speed field specifies a symbolic speed for the memory (0..4): 0 is
the fastest, 4 the slowest. The linker uses the relative speed of the
memories in such a way, that optimal speed is achieved. The default
speed is 1.
• The map field specifies how this memory maps onto an (internal) bus.
Mappings are described in section 8.5.4, Mappings.

• • • • • • • •
 8-32 TriCore Reference Manual

memory mem_name
{
type = rom;
mau = 8;
size = 64k;
speed = 2;
map ( map_description );
}

With the bus keyword you define a bus in a derivative definition. Buses
are described in section 8.5.2, Defining Internal Buses.
LINKER SCRIPT LANGUAGE
 Linker Script Language 8-33

8.7 SEMANTICS OF THE BOARD SPECIFICATION

Keywords in the board specification

processor
derivative
bus
mau
width
map
memory
type reserved rom ram nvram
mau
size
speed
map

map
dest bus space
dest_dbits
dest_offset
size
src_dbits
src_offset

8.7.1 DEFINING A PROCESSOR

If you have a target board with multiple processors that have the same
derivative, you need to instantiate each individual processor in a processor
definition. This information tells the linker which processor has which
derivative and enables the linker to distinguish between the present
processors.

If you use processors that all have a unique derivative, you may omit the
processor definitions. In this case the linker assumes that for each
derivative definition in the LSL file there is one processor. The linker uses
the derivative name also for the processor.

• • • • • • • •
 8-34 TriCore Reference Manual

With the keyword processor you define a processor. You can freely
choose the processor name. The name is used to refer to it at other places
in the LSL file:
processor proc_name
{
processor definition
}

8.7.2 INSTANTIATING DERIVATIVES

With the keyword derivative you tell the linker that the given processor
has a certain derivative. The derivative name refers to an existing
derivative definition in the same LSL file.
LINKER SCRIPT LANGUAGE

For examples, if you have two processors on your target board (called
myproc_1 and myproc_2) that have the same derivative (called
myderiv), you must instantiate both processors as follows:

processor myproc_1
{
derivative = myderiv;
}

processor myproc_2
{
derivative = myderiv;
}

If the derivative definition has parameters you must specify the

arguments that correspond with the parameters. For example
myderiv1 expects two parameters which are used in the derivative
definition:
processor myproc
{
derivative = myderiv1 (2,4);
}
 Linker Script Language 8-35

8.7.3 DEFINING EXTERNAL MEMORY AND BUSES

It is common to define external memory (off-chip) and external buses at
the global scope (outside any enclosing definition). Internal memory
(on-chip memory) is usually defined in the scope of a derivative
definition.

With the keyword memory you define physical memory that is present on
the target board. The memory name is used to identify the memory and
does not conflict with other identifiers. If you define memory parts in the
LSL file, only the memory defined in these parts is used for placing
sections.

If no external memory is defined in the LSL file and if the linker option to
allocate memory on demand is set then the linker will assume that all
virtual addresses are mapped on physical memory. You can override this
behavior by specifying one or more memory definitions.
memory mem_name
{
type = rom;
mau = 8;
size = 64k;
speed = 2;
map ( map_description );
}

For a description of the keywords, see section 8.6.3, Defining Internal

Memory and Buses.

With the keyword bus you define a bus (the combination of data and
corresponding address bus). The bus name is used to identify a bus and
does not conflict with other identifiers. Bus descriptions at the global
scope (outside any definition) define external buses. These are buses that
are present on the target board.
bus bus_name
{
mau = 8;
width = 8;
map ( map_description );
}

For a description of the keywords, see section 8.5.2, Defining Internal

Buses.

• • • • • • • •
 8-36 TriCore Reference Manual

You can connect off-chip memory to any derivative: you need to map the
off-chip memory to a bus and map that bus on the internal bus of the
derivative you want to connect it to.
LINKER SCRIPT LANGUAGE
 Linker Script Language 8-37

8.8 SEMANTICS OF THE SECTION LAYOUT DEFINITION

Keywords in the section layout definition

section_layout
direction low_to_high high_to_low
group
align
attributes + - r w x b i s
fill
ordered
clustered
contiguous
overlay
allow_cross_references
load_addr
mem
run_addr
mem
page
select
heap
size
stack
size
reserved
size
attributes r w x
fill
alloc_allowed absolute
copytable
section
size
attributes r w x
fill

if
else

• • • • • • • •
 8-38 TriCore Reference Manual

8.8.1 DEFINING A SECTION LAYOUT

With the keyword section_layout you define a section layout for
exactly one address space. In the section layout you can specify how input
sections are placed in the address space, relative to each other, and what
the absolute run and load addresses of each section will be.

You can define one or more section definitions. Each section definition
arranges the sections in one address space. You can precede the address
space name with a processor name and/or core name, separated by
colons. You can omit the processor name and/or the core name if only
one processor is defined and/or only one core is present in the processor.
A reference to a space in the only core of the only processor in the system
would look like "::my_space". A reference to a space of the only core
on a specific processor in the system could be "my_chip::my_space ".
The next example shows a section definition for sections in the my_space
LINKER SCRIPT LANGUAGE

address space of the processor called my_chip:

section_layout my_chip::my_space ( locate_direction )
{
section statements
}

With the optional keyword direction you specify whether the linker
starts locating sections from low_to_high (default) or from
high_to_low . In the second case the linker starts locating sections at the
highest addresses in the address space but preserves the order of sections
when necessary (one processor and core in this example).
section_layout ::my_space ( direction = high_to_low )
{
section statements
}

If you do not explicitly tell the linker how to locate a section, the linker
decides on the basis of the section attributes in the object file and the
information in the architecture definition and memory parts where to
locate the section.
 Linker Script Language 8-39

8.8.2 CREATING AND LOCATING GROUPS OF

SECTIONS
Sections are located per group. A group can contain one or more (sets of)
input sections as well as other groups. Per group you can assign a mutual
order to the sets of sections and locate them into a specific memory part.
group ( group_specifications )
{
section_statements
}

With the section_statements you generally select sets of sections to form

the group. This is described in subsection Selecting sections for a group.

Instead of selecting sections, you can also modify special sections like
stack and heap or create a reserved section. This is described in section
8.8.3, Creating or Modifying Special Sections.

With the group_specifications you actually locate the sections in the group.
This is described in subsection Locating a group.

Selecting sections for a group

With the select keyword you can select one or more sections for the
group. You can select a section by name or by attributes. If you select a
section by name, you can use a wildcard pattern:

"*" matches with all section names

"?" matches with a single character in the section name
"\" takes the next character literally
"[abc]" matches with a single 'a', 'b' or 'c' character
"[a-z]" matches with any single character in the range 'a' to 'z'
group ( ... )
{
select ".mysection";
select "*";
}

The first select statement selects the section with the name ".mysection".
The second select statement selects all sections that were not selected
yet.

• • • • • • • •
 8-40 TriCore Reference Manual

A section is selected by the first select statement that matches, in the

union of all section layouts for the address space. Global section layouts
are processed in the order in which they appear in the LSL file. Internal
core architecture section layouts always take precedence over global
section layouts.
• The attributes field selects all sections that carry (or do not carry)
the given attribute. With +attribute you select sections that have the
specified attribute set. With -attribute you select sections that do not
have the specified attribute set. You can specify one or more of the
following attributes:
- r readable sections
- w readable/writable sections
- x executable sections
- i initialized sections
LINKER SCRIPT LANGUAGE

- b sections that should be cleared at program startup

- s scratch sections (not cleared and not initialized)
To select all read-only sections:
group ( ... )
{
select (attributes = +r);
}

Keep in mind that all section selections are restricted to the address space
of the section layout in which this group definition occurs.

Locating a group
group group_name ( group_specifications )
{
section_statements
}

With the group_specifications you actually define how the linker must
locate the group. You can roughly define three things: 1) assign properties
to the group like alignment and read/write attributes, 2) define the mutual
order in the address space for sections in the group and 3) restrict the
possible addresses for the sections in a group.
 Linker Script Language 8-41

The linker creates labels that allow you to refer to the begin and end
address of a group from within the application software. Labels
_lc_gb_group_name and _lc_ge_group_name mark the begin and end
of the group respectively, where the begin is the lowest address used
within this group and the end is the highest address used. Notice that a
group not necessarily occupies all memory between begin and end
address. The given label refers to where the section is located at run-time
(versus load-time).

1. Assign properties to the group like alignment and read/write attributes.

These properties are assigned to all sections in the group (and subgroups)
and override the attributes of the input sections.
• The align field tells the linker to align all sections in the group and
the group as a whole according to the align value. Default the linker
uses the largest alignment constraint of either the input sections or the
alignment of the address space.
• The attributes field tells the linker to assign one or more attributes
to the sections in the group. Default the linker uses the attributes of the
input sections. The list of available attributes is the same as described
above for the selection of sections.
2. Define the mutual order of the sections in the group.
By default, a group is unrestricted which means that the linker has total
freedom to place the sections of the group in the address space.
• The ordered keyword tells the linker to locate the sections in the
same order in the address space as they appear in the group (but not
necessarily adjacent).
Suppose you have an ordered group that contains the sections 'A', 'B'
and 'C'. Default the linker places the sections in the address space like
'A' - 'B' - 'C', where section 'A' gets the lowest possible address. With
direction=high_to_low in the section_layout space properties,
the linker places the sections in the address space like 'C' - 'B' - 'A',
where section 'A' gets the highest possible address.
• The contiguous keyword tells the linker to locate the sections in the
group in a single address range. Within a contiguous group the input
sections are located in arbitrary order, however the group occupies one
contigous range of memory. Due to alignment of sections there can be
'alignment gaps' between the sections.

• • • • • • • •
 8-42 TriCore Reference Manual

When you define a group that is both ordered and contiguous, this
is called a sequential group. In a sequential group the linker places
sections in the same order in the address space as they appear in the
group and it occupies a contiguous range of memory.
• The clustered keyword tells the linker to locate the sections in the
group in a number of contiguous blocks. It tries to keep the number of
these blocks to a minimum. If enough memory is available, the group
will be located as if it was specified as contiguous. Otherwise, it gets
split into two or more blocks.
If a contiguous or clustered group contains alignment gaps, the linker
can locate sections that are not part of the group in these gaps. To
prevent this, you can use the fill keyword. If the group is located in
RAM, the gaps are treated as reserved (scratch) space. If the group is
located in ROM, the alignment gaps are filled with zeros by default.
LINKER SCRIPT LANGUAGE

You can however change the fill pattern by specifying a bit pattern.
The result of the expression, or list of expressions, is used as values to
write to memory, each in MAU.
• The overlay keyword tells the linker to overlay the sections in the
group. The linker places all sections in the address space using a
contiguous range of addresses. (Thus an overlay group is automatically
also a contiguous group.) To overlay the sections, all sections in the
overlay group share the same run-time address.
For each input section within the overlay the linker automatically
defines two symbols. The symbol _lc_cb_section_name is defined
as the load-time start address of the section. The symbol
_lc_ce_section_name is defined as the load-time end address of
the section. C (or assembly) code may be used to copy the overlaid
sections.

If sections in the overlay group contain references between groups, the

linker reports an error. The keyword allow_cross_references tells
the linker to accept cross-references. Normally, it does not make sense
to have references between sections that are overlaid.
 Linker Script Language 8-43

group ovl (overlay)

{
group a
{
select "my_ovl_p1";
select "my_ovl_p2";
}
group b
{
select "my_ovl_q1";
}
}

It may be possible that one of the sections in the overlay group already
has been defined in another group where it received a load-time
address. In this case the linker does not overrule this load-time address
and excludes the section from the overlay group.

3. Restrict the possible addresses for the sections in a group.

The load-time address specifies where the group's elements are loaded in
at download time. The run-time address specifies where sections are
located at run-time, that is when the program is executing. If you do not
explicitly restrict the address in the LSL file, the linker assigns addresses to
the sections based on the restrictions relative to other sections in the LSL
file and section alignments. The program is responsible for copying
overlay sections at appropriate moment from its load-time location to its
run-time location (this is typically done by the startup code).
• The run_addr keyword defines the run-time address. If the run-time
location of a group is set explicitly, the given order between groups
specify whether the run-time address propagates to the parent group
or not. The location of the sections a group can be restricted either to a
single absolute address, or to a number of address ranges. With an
expression you can specify that the group should be located at the
absolute address specified by the expression:
group (run_addr = 0xa00f0000)

You can use the '[offset]' variant to locate the group at the given
absolute offset in memory:
group (run_addr = mem:A[0x1000])

A range can be an absolute space address range, written as [ expr ..

expr ], a complete memory device, written as mem:mem_name, or a
memory address range, mem:mem_name[ expr .. expr ]

• • • • • • • •
 8-44 TriCore Reference Manual

group (run_addr = mem:my_dram)

You can use the '|' to specify an address range of more than one
physical memory device:
group (run_addr = mem:A | mem:B)
• The load_addr keyword changes the meaning of the section selection
in the group: the linker selects the load-time ROM copy of the named
section(s) instead of the regular sections. Just like run_addr you can
specify an absolute address or an address range.
The load_addr keyword itself (without an assignment) specifies that
the group's position in the LSL file defines its load-time address.
group (load_addr)
select "mydata"; // select ROM copy of mydata:
LINKER SCRIPT LANGUAGE

// "[mydata]"

The load-time and run-time addresses of a group cannot be set at the

same time. If the load-time property is set for a group, the group (only)
restricts the positioning at load-time of the group's sections. It is not
possible to set the address of a group that has a not-unrestricted parent
group.

The properties of the load-time and run-time start address are:

• At run-time, before using an element in an overlay group, the
application copies the sections from their load location to their
run-time location, but only if these two addresses are different. For
non-overlay sections this happens at program start-up.
• The start addresses cannot be set to absolute values for unrestricted
groups.
• For non-overlay groups that do not have an overlay parent, the
load-time start address equals the run-time start address.
• For any group, if the run-time start address is not set, the linker
selects an appropriate address.
For overlays, the linker reserves memory at the run-time start address as
large as the largest element in the overlay group.
• The page keyword tells the linker to place the group in one page.
Instead of specifying a run-time address, you can specify a page and
optional a page number. Page numbers start from zero. If you omit the
page number, the linker chooses a page.
 Linker Script Language 8-45

The page keyword refers to pages in the address space as defined in

the architecture definition. See also the page keyword in section 8.5.3,
Defining Address Spaces.
group (page, ... )
group (page = 3, ...)

8.8.3 CREATING OR MODIFYING SPECIAL SECTIONS

Instead of selecting sections, you can also create a reserved section or an
output section or modify special sections like a stack or a heap. Because
you cannot define these sections in the input files, you must use the linker
to create them.

Stack
• The stack keyword tells the linker to reserve memory for the stack.
The name for the stack section refers to the stack as defined in the
architecture definition. If no name was specified in the architecture
definition, the default name is stack.
With the keyword size you can specify the size for the stack. If the
size is not specified, the linker uses the size given by the min_size
argument as defined for the stack in the architecture definition.
Normally the linker automatically tries to maximize the size, unless you
specified the fixed keyword.
group ( ... )
{
stack "mystack" ( size = 2k );
}

The linker creates two labels to mark the begin and end of the stack,
_lc_ub_stack_name for the begin of the stack and
_lc_ue_stack_name for the end of the stack. The linker allocates
space for the stack when there is a reference to either of the labels.

See also the stack keyword in section 8.5.3, Defining Address Spaces.

• • • • • • • •
 8-46 TriCore Reference Manual

Heap
• The heap keyword tells the linker to reserve a dynamic memory range
for the malloc() function. Optionally you can assign a name to the
heap section. With the keyword size you can change the size for the
heap. If the size is not specified, the linker uses the size given by the
min_size argument as defined for the heap in the architecture
definition. Normally the linker automatically tries to maximize the size,
unless you specified the fixed keyword.
group ( ... )
{
heap "myheap" ( size = 2k );
}

The linker creates two labels to mark the begin and end of the heap,
_lc_ub_heap_name for the begin of the heap and
LINKER SCRIPT LANGUAGE

_lc_ue_heap_name for the end of the heap. The linker allocates

space for the heap when a reference to either of the section labels
exists in one of the input object files.

Reserved section
• The reserved keyword tells the linker to create an area or section of
a given size. The linker will not locate any other sections in the
memory occupied by a reserved section, with some exceptions.
Optionally you can assign a name to a reserved section. With the
keyword size you can specify a size for a given reserved area or
section.
group ( ... )
{
reserved "myreserved" ( size = 2k );
}

The optional fill field contains a bit pattern that the linker writes to
all memory addresses that remain unoccupied during the locate
process. The result of the expression, or list of expressions, is used as
values to write to memory, each in MAU. The first MAU of the fill
pattern is always the first MAU in the section.

By default, no sections can overlap with a reserved section. With

alloc_allowed=absolute sections that are located at an absolute
address due to an absolute group restriction can overlap a reserved
section.
 Linker Script Language 8-47

With the attributes field you can set the access type of the reserved
section. The linker locates the reserved section in its space with the
restrictions that follow from the used attributes, r, w or x or a valid
combination of them. The allowed attributes are shown in the
following table. A value between < and > in the table means this value
is set automatically by the linker.

Properties set in LSL Resulting section properties

attributes filled access memory content
x yes <rom> executable
r yes r <rom> data
r no r <rom> scratch
rx yes r <rom> executable
rw yes rw <ram> data
rw no rw <ram> scratch
rwx yes rw <ram> executable

group ( ... )
{
reserved "myreserved" ( size = 2k,
attributes = rw, fill = 0xaa );
}

If you do not specify any attributes, the linker will reserve the given
number of maus, no matter what type of memory lies beneath. If you
do not specify a fill pattern, no section is generated.

The linker creates two labels to mark the begin and end of the section,
_lc_ub_name for the start, and __lc_ue_name for the end of the
reserved section.

Output sections
• The section keyword tells the linker to accumulate sections obtained
from object files ("input sections") into an output section of a fixed size
in the locate phase. You can select the input sections with select
statements. With the keyword size you specify the size of the output
section.

• • • • • • • •
 8-48 TriCore Reference Manual

The fill field contains a bit pattern that the linker writes to all unused
space in the output section. When all input sections have an image
(code/data) you must specify a fill pattern. If you do not specify a fill
pattern, all input sections must be scratch sections. The fill pattern is
aligned at the start of the output section.

As with a reserved section you can use the attributes field to set the
access type of the output section.
group ( ... )
{
section "myoutput" ( size = 4k, attributes = rw,
fill = 0xaa )
{
select "myinput1";
select "myinput2";
LINKER SCRIPT LANGUAGE

}
}

The linker creates two labels to mark the begin and end of the section,
_lc_ub_name for the start, and __lc_ue_name for the end of the
output section.

Copy table
• The copytable keyword tells the linker to select a section that is used
as copy-table. The content of the copy-table is created by the linker. It
contains the start address and length of all sections that should be
initialized by the startup code.
The linker creates two labels to mark the begin and end of the section,
_lc_ub_table for the start, and __lc_ue_table for the end of the
copy table. The linker generates a copy table when a reference to
either of the section labels exists in one of the input object files.

8.8.4 CREATING SYMBOLS

You can tell the linker to create symbols before locating by putting
assignments in the section layout definition. Symbol names are
represented by double-quoted strings. Any string is allowed, but object
files may not support all characters for symbol names. You can use two
different assignment operators. With the simple assignment operator '=',
the symbol is created unconditionally. With the ':=' operator, the symbol is
only created if it already exists as an undefined reference in an object file.
 Linker Script Language 8-49

The expression that represents the value to assign to the symbol may
contain references to other symbols. If such a referred symbol is a special
section symbol, creation of the symbol in the left hand side of the
assignment will cause creation of the special section.
section_layout
{
"_lc_bs" := "_lc_ub_stack";
// when the symbol _lc_bs occurs in the object
// file, the linker allocates space for the stack
}

8.8.5 CONDITIONAL GROUP STATEMENTS

Within a group, you can conditionally select sections or create special
sections.
• With the if keyword you can specify a condition. The succeeding
section statement is executed if the condition evaluates to TRUE (1).
• The optional else keyword is followed by a section statement which
is executed in case the if-condition evaluates to FALSE (0).
group ( ... )
{
if ( size_of ( sect:.mysection ) < 2k )
select ".mysection";
else
select ".othersection";
}

• • • • • • • •
 8-50 TriCore Reference Manual
LINKER SCRIPT LANGUAGE
CHAPTER
CPU FUNCTIONAL
PROBLEMS

9
 9-2
CPU FUNCTIONAL PROBLEMS

9
CHAPTER
TriCore Reference Manual
 CPU Functional Problems 9-3

9.1 INTRODUCTION
Infineon Technologies regularly publishes microcontroller errata sheets
reporting functional problems and deviations from the electrical
specifications and timing specifications.

The TASKING TriCore software development tools provide solutions for a

number of these functional problems in the TriCore architecture.

Support to deal with CPU functional problem is provided in three areas:

• Whenever possible and relevant, compiler bypasses will modify the
code in order to avoid the identified erroneous code sequences;
• The TriCore assembler gives warnings for suspicious or erroneous code
sequences;
• Ready-built, 'protected' standard C libraries with bypasses for all
identified TriCore CPU functional problems are included in the
toolchain.
This chapters lists a summary of identified functional problems which can
be bypassed by the TASKING TriCore tool kit.

Please refer to the Infineon errata sheets for the TriCore architecture
revision-step of your particular device, to check the need for applying any
of these bypasses. Also refer to the Infineon errata sheets for a complete
description of the CPU functional problems, as the workarounds listed
below do not describe the functional problem itself.

With the TASKING C compiler and assembler command line options,

pragmas and macro definitions you can enable or disable specific CPU
functional problem bypasses.

To enable the compiler bypasses and assembler checks for all TriCore CPU
TC112 problems (respectively TC113 problems) at once, use the command
line option --silicon-bug=all-tc112 (respectively
--silicon-bug=all-tc113)

To enable the bypasses from the embedded development environment

(EDE):

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

2. Expand the Processor entry.

3. Select Bypasses. Depending on the target processor you have selected,

this shows the bypasses for the TC1 v1.2 or TC1 v1.3.

• • • • • • • •
 9-4 TriCore Reference Manual

9.2 CPU FUNCTIONAL PROBLEM BYPASSES

CPU_TC.013
Compiler and assembler option:
--silicon-bug=cpu-tc013

Assembler control:
$CPU_TC013 {on|off}
CPU FUNCTIONAL PROBLEMS

Assembler macro:
The assembler macro __CPU_TC013__ is defined if you specify option
--silicon-bug=cpu-tc013.

Protected libraries to link:

lib\p\tc112\*.a

Compiler bypass:
To bypass this CPU functional problem, the C compiler generates a NOP16
instruction if a 16-bit load/store address register instruction (instructions:
LD16.A en ST16.A) is followed by a lower context load/store instruction
(instructions: LDLCX and STLCX).

Assembler check:
The assembler gives a warning if a 16-bit load/store address register
instruction (instructions: LD16.A en ST16.A) is followed by a lower context
load/store instruction (instructions: LDLCX and STLCX).
Wnum: suspicious instruction concerning CPU functional
defect TC013

You can suppress this warning with the option -wnum.

 CPU Functional Problems 9-5

CPU_TC.030
Compiler and assembler option:
--silicon-bug=cpu-tc030

Assembler control:
$CPU_TC030 {on|off}

Assembler macro:
The assembler macro __CPU_TC030__ is defined if you specify option
--silicon-bug=cpu-tc030.

Protected libraries to link:

lib\p\tc112\*.a

Compiler bypass:
To bypass this CPU functional problem, the C compiler generates an
ISYNC instruction prior to the LOOP instruction if the last instruction in the
loop is a DVSTEP or a DVSTEP.U.

Assembler check:
The assembler gives a warning for loops where the last instruction is a
DVSTEP or a DVSTEP.U:
Wnum: suspicious instruction concerning CPU functional
defect TC030

You can suppress this warning with the option -wnum.

• • • • • • • •
 9-6 TriCore Reference Manual

CPU_TC.031
Compiler and assembler option:
--silicon-bug=cpu-tc031

Assembler control:
$CPU_TC031 {on|off}

Assembler macro:
The assembler macro __CPU_TC031__ is defined if you specify option
--silicon-bug=cpu-tc031.
CPU FUNCTIONAL PROBLEMS

Protected libraries to link:

lib\p\tc112\*.a

Compiler bypass:
To bypass this CPU functional problem, the C compiler generates an
ISYNC instruction prior to the LOOP instruction.

Assembler check:
The assembler gives a warning if the LOOP instruction is not preceded by
an ISYNC instruction:
Wnum: suspicious instruction concerning CPU functional
defect TC031

You can suppress this warning with the option -wnum.

 CPU Functional Problems 9-7

CPU_TC.034
Compiler and assembler option:
--silicon-bug=cpu-tc034

Assembler control:
$CPU_TC034 {on|off}

Assembler macro:
The assembler macro __CPU_TC034__ is defined if you specify option
--silicon-bug=cpu-tc034.

Protected libraries to link:

lib\p\tc112\*.a

Compiler bypass:
To bypass this CPU functional problem, the C compiler generates an
ISYNC instruction after each DSYNC instruction.

Assembler check:
The assembler gives a warning if a DSYNC instruction is not followed by
an ISYNC instruction:
Wnum: suspicious instruction concerning CPU functional
defect TC034

You can suppress this warning with the option -wnum.

• • • • • • • •
 9-8 TriCore Reference Manual

CPU_TC.043
Linker option:
-D__CPU_TC043__

Linker bypass:
To bypass this CPU functional problem, a preprocessor define is used in
the tc*.lsl linker script files. The linker will not use the last 16 bytes of
a segment.
CPU FUNCTIONAL PROBLEMS
 CPU Functional Problems 9-9

CPU_TC.048
Compiler and assembler option:
--silicon-bug=cpu-tc048

Assembler control:
$CPU_TC048 {on|off}

Assembler macro:
The assembler macro __CPU_TC048__ is defined if you specify option
--silicon-bug=cpu-tc048.

Protected libraries to link:

lib\p\tc112\*.a

Compiler bypass:
To bypass this CPU functional problem, the C compiler generates a NOP
instruction before a JI or CALLI instruction when this instruction is not
directly preceded by either a NOP instruction or an integer instruction or a
MAC instruction. The compiler also generates a NOP instruction before a
RET and RET16 instruction if there is no or just one instruction before RET,
starting from the function entry point.

Assembler check:
The assembler gives a warning when a JI or CALLI instruction is not
directly preceded by a NOP instruction. The assembler also gives a
warning when there is no or just one instruction (not a NOP instruction)
between label and RET or RET16:
Wnum: suspicious instruction concerning CPU functional
defect TC048

You can suppress this warning with the option -wnum.

• • • • • • • •
 9-10 TriCore Reference Manual

CPU_TC.050
Compiler and assembler option:
--silicon-bug=cpu-tc050

Assembler control:
$CPU_TC050 {on|off}

Assembler macro:
The assembler macro __CPU_TC050__ is defined if you specify option
--silicon-bug=cpu-tc050.
CPU FUNCTIONAL PROBLEMS

Protected libraries to link:

lib\p\tc112\*.a

Compiler bypass:
To bypass this CPU functional problem, the C compiler generates a NOP
instruction between a multi-cycle integer instruction and a load
instruction.

Assembler check:
The assembler gives a warning if a multi-cycle integer instruction is
directly followed by a load instruction.:
Wnum: suspicious instruction concerning CPU functional
defect TC050

You can suppress this warning with the option -wnum.

 CPU Functional Problems 9-11

CPU_TC051
Linker option:
-D__CPU_TC051__

Linker bypass:
To bypass this CPU functional problem, a preprocessor define is used in
the tc*.lsl linker script files. The linker will use more than one section
for context stores if the required CSA area exceeds the 4k. Each section
will have a maximum size of 4k and will start on an 8k boundary.

• • • • • • • •
 9-12 TriCore Reference Manual

CPU_TC.060
Compiler and assembler option:
--silicon-bug=cpu-tc060

Assembler control:
$CPU_TC060 {on|off}

Assembler macro:
The assembler macro __CPU_TC060__ is defined if you specify option
--silicon-bug=cpu-tc060.
CPU FUNCTIONAL PROBLEMS

Protected libraries to link:

lib\p\tc112\*.a or lib\p\tc113\*.a

Compiler bypass:
To bypass this CPU functional problem, the C compiler generates a NOP
instruction between an LD.A / LD.DA instruction and a following LD.W /
LD.D instruction, even if an integer instruction occurs in between.

Assembler check:
The assembler gives a warning when an LD.A / LD.DA instruction is
directly followed by an LD.W / LD.D instruction, or when only an integer
instruction is in between.
Wnum: suspicious instruction concerning CPU functional
defect TC060

You can suppress this warning with the option -wnum.

 CPU Functional Problems 9-13

TC112_COR1
Compiler and assembler option:
--silicon-bug=cor1

Assembler control:
$TC112_COR1 {on|off}

Assembler macro:
The assembler macro __TC112_COR1__ is defined if you specify the
option --silicon-bug=cor1.

Protected libraries to link:

lib\p\tc112\*.a

Compiler bypass:
To bypass this CPU functional problem, the C compiler generates an
ISYNC instruction before each LOOP, LOOP16 and LOOPU instruction.

Assembler check:
The assembler gives a warning when the preceding instruction of a LOOP,
LOOP16 or LOOPU instruction is not an ISYNC instruction:
Wnum: suspicious instruction concerning CPU functional
defect TC112_COR1

You can suppress this warning with the option -wnum.

• • • • • • • •
 9-14 TriCore Reference Manual

TC112_COR3
Linker option:
-D__TC112_COR3__

Linker bypass:
To bypass this CPU functional problem, a preprocessor define is used in
the tc*.lsl linker script files to restrict the size in the CSA absolute
address mapping to 32Kb scratch pad RAM on the DMU.
CPU FUNCTIONAL PROBLEMS
 CPU Functional Problems 9-15

TC112_COR4
Compiler and assembler option:
--silicon-bug=cor4

Assembler control:
$TC112_COR4 {on|off}

Assembler macro:
The assembler macro __TC112_COR4__ is defined if you specify the
option --silicon-bug=cor4.

Protected libraries to link:

lib\p\tc112\*.a

Compiler bypass:
To bypass this CPU functional problem, the C compiler generates a NOP
instruction between a (target) label and the instruction following it This is
done when the instruction directly uses an An register for either an
effective address calculation or as the target of an indirect branch.
Optionally an integer instruction may directly follow the label.

For example, a NOP will be inserted after the following labels:

A_label:
ji a4

B_label:
add d0, d1 ; integer instruction
ji a4

Assembler check:
The assembler gives a warning for an instruction using an An register for
either an effective address calculation or as the target of an indirect branch
that is located directly after a (target) label, optionally with an integer
instruction in between:
Wnum: suspicious instruction concerning CPU functional
defect TC112_COR4

You can suppress this warning with the option -wnum.

• • • • • • • •
 9-16 TriCore Reference Manual

TC112_COR6
Assembler option:
--silicon-bug=cor6

Assembler control:
$TC112_COR6 {on|off}

Assembler macro:
The assembler macro __TC112_COR6__ is defined if you specify the
option --silicon-bug=cor6.
CPU FUNCTIONAL PROBLEMS

Protected libraries to link:

lib\p\tc112\*.a

Compiler bypass:
There is no C compiler workaround required for this CPU functional
problem, because the compiler does not generate CALLI instructions with
a target address in register A11.

Assembler check:
The assembler generates an error for instruction CALLI A11.
 CPU Functional Problems 9-17

TC112_COR7
Compiler and assembler option:
--silicon-bug=cor7

Assembler control:
$TC112_COR7 {on|off}

Assembler macro:
The assembler macro __TC112_COR7__ is defined if you specify the
option --silicon-bug=cor7.

Protected libraries to link:

lib\p\tc112\*.a

Compiler bypass:
To bypass this CPU functional problem, the C compiler generates a NOP
instruction at the very top of any subroutine that starts with a CALL
instruction or that starts with an integer instruction or MAC instruction
directly followed by a CALL instruction.

Assembler check:
The assembler gives a warning when the first instruction of a subroutine is
a CALL instruction or an integer instruction or MAC instruction directly
followed by a CALL instruction.
Wnum: suspicious instruction concerning CPU functional
defect TC112_COR7

You can suppress this warning with the option -wnum.

• • • • • • • •
 9-18 TriCore Reference Manual

TC112_COR10
Compiler and assembler option:
--silicon-bug=cor10

Assembler control:
$TC112_COR10 {on|off}

Assembler macro:
The assembler macro __TC112_COR10__ is defined if you specify the
option --silicon-bug=cor10.
CPU FUNCTIONAL PROBLEMS

Protected libraries to link:

lib\p\tc112\*.a

Compiler bypass:
To bypass this CPU functional problem, the C compiler avoids generation
of store instructions that use a circular addressing mode with an offset
value not equal to zero. An additional circular load instruction is generated
with the required offset to post-increment the circular buffer pointer.

For example:
st.w [a6/a7+c]0,d15
ld.w d15,[a6/a7+c]4

Instead of:
st.w [a6/a7+c]4,d15

Assembler check:
The assembler gives a warning for store operations that use a circular
addressing mode with an offset not equal to zero:
Wnum: suspicious instruction concerning CPU functional
defect TC112_COR10

You can suppress this warning with the option -wnum.

 CPU Functional Problems 9-19

TC112_COR13
Compiler and assembler option:
--silicon-bug=cor13

Assembler control:
$TC112_COR13 {on|off}

Assembler macro:
The assembler macro __TC112_COR13__ is defined if you specify option
--silicon-bug=cor13.

Protected libraries to link:

lib\p\tc112\*.a

Compiler bypass:
To bypass this CPU functional problem, the C compiler generates an
ISYNC instruction prior to the LOOP instruction if the loop contains a
single integer instruction that is a DVSTEP or a DVSTEP.U.

Assembler check:
The assembler gives a warning for loops that contain a single integer
instruction that is a DVSTEP or a DVSTEP.U:
Wnum: suspicious instruction concerning CPU functional
defect TC112_COR13

You can suppress this warning with the option -wnum.

• • • • • • • •
 9-20 TriCore Reference Manual

TC112_COR14
Compiler option:
--silicon-bug=cor14

Protected libraries to link:

lib\p\tc112\*.a

Compiler bypass:
To bypass this CPU functional problem, the C compiler uses code that
protects a divide instruction sequence against interrupts. Instead of
CPU FUNCTIONAL PROBLEMS

generating inline divide code, the C compiler generates calls to run-time

library functions that support divide operations with interrupt protection.
Next skeleton code demonstrates the protective code used in these
run-time library functions:
;;
;; Save interrupt state and disable interrupts
;;
mfcr d0,#0xfe2c ; save ICR in d0
disable ; disable interrupts

divide instructions:
;;
;; Restore interrupt state
;;
jz.t d0:8,disabled ; do not enable interrupts
enable ; when they were disabled
disabled:

The C run-time library modules involved are acircint.asm ,

dfrfr.asm, sdivmod.asm and udivmod.asm .

Assembler check:
An assembler check for this CPU functional problem is not available,
because global interrupt enable state cannot be checked at assembly level.
 CPU Functional Problems 9-21

TC112_COR15
Assembler option:
--silicon-bug=cor15

Assembler control:
$TC112_COR15 {on|off}

Assembler macro:
The assembler macro __TC112_COR15__ is if you specify the option
--silicon-bug=cor15.

Protected libraries to link:

lib\p\tc112\*.a (or add lib\src\cstart.asm to your project).

Compiler bypass:
There is no compiler bypass for this problem.

Assembler bypass:
To bypass this CPU functional problem, the assembler adds a macro to the
C startup code to disable the starvation protection by resetting the
BCUCON.SPE bit.

• • • • • • • •
 9-22 TriCore Reference Manual

TC112_COR16
Compiler and assembler option:
--silicon-bug=cor16

Linker option:
-D__TC112_COR16__

Assembler control:
$TC112_COR16 {on|off}
CPU FUNCTIONAL PROBLEMS

Assembler macro:
The assembler macro __TC112_COR16__ is defined if you specify the
option --silicon-bug=cor16.

Protected libraries to link:

lib\p\tc112\*.a (or add lib\src\cstart.asm to your project).

Compiler bypass:
To bypass this CPU functional problem, the C compiler aligns circular
qualified buffers to a quad-word boundary, and the compiler sizes all
stack frames to an integral number of quad-words. See section 3.4.1,
Circular Buffers in the User's Manual, for a description on how to declare
a circular buffer.

Assembler bypass:
To bypass this CPU functional problem, the assembler adds a macro to the
C startup code to enable initialization of the stack pointers to a quad-word
boundary.

Linker bypass:
A preprocessor define is used in the tc*.lsl linker script files to set the
alignment of the user stack and the interrupt stack to a quad-word
alignment.
 CPU Functional Problems 9-23

TC112_COR17
Compiler and assembler option:
--silicon-bug=cor17

Assembler control:
$TC112_COR17 {on|off}

Assembler macro:
The assembler macro __TC112_COR17__ is defined if you specify the
option --silicon-bug=cor17.

Protected libraries to link:

lib\p\tc112\*.a

Compiler bypass:
To bypass this CPU functional problem, the C compiler generates an
ISYNC instruction after a DSYNC instruction. The C compiler only
generates a DSYNC instruction when bypass TC113_CPU14 is enabled.

Assembler check:
The assembler gives a warning if a DSYNC is not followed by an ISYNC
instruction:
Wnum: suspicious instruction concerning CPU functional
defect TC112_COR17

You can suppress this warning with the option -wnum.

• • • • • • • •
 9-24 TriCore Reference Manual

TC113_CPU5
Compiler option:
--silicon-bug=cpu5

Protected libraries to link:

lib\p\tc113\*.a

Compiler bypass:
To bypass this CPU functional problem, the C compiler generates an
ISYNC instruction before a loop body.
CPU FUNCTIONAL PROBLEMS

Example:
isync
_loop_start:
..
..
loop a8, _loop_start

Assembler check:
This CPU functional problem does not cause a run-time problem, it is only
a performance issue. Therefor no assembler checking is required to warn
you for possible run-time problems.
 CPU Functional Problems 9-25

TC113_CPU9
Compiler and assembler option:
--silicon-bug=cpu9

Assembler control:
$TC113_CPU9 {on|off}

Assembler macro:
The assembler macro __TC113_CPU9__ is defined if you specify the
option --silicon-bug=cpu9.

Protected libraries to link:

lib\p\tc113\*.a

Compiler bypass:
To bypass this CPU functional problem, the C compiler generates two NOP
instructions after a DSYNC instruction. The C compiler only generates a
DSYNC instruction when CPU functional problem bypass TC113_CPU14 is
enabled.

Assembler check:
The assembler gives a warning if a DSYNC is not followed by two NOP
instructions:
Wnum: suspicious instruction concerning CPU functional
defect TC113_CPU9

You can suppress this warning with the option -wnum.

• • • • • • • •
 9-26 TriCore Reference Manual

TC113_CPU11
Compiler and assembler option:
--silicon-bug=cpu11

Pragma:
#pragma TC113_CPU11 [on|off|restore]

Assembler control:
$TC113_CPU11 {on|off}
CPU FUNCTIONAL PROBLEMS

Assembler macro:
The assembler macro __TC113_CPU11__ is defined if you specify the
option --silicon-bug=cpu11.

Protected libraries to link:

lib\p\tc113\*.a

Compiler bypass:
To bypass this CPU functional problem, the C compiler generates a NOP
instruction before a JI instruction. The compiler also generates a NOP
before a RET and RET16 instruction if there is no or just one instruction
before RET, starting from the function entry point.

Assembler check:
The assembler gives a warning when a JI instruction is not directly
preceded by a NOP instruction. The assembler also gives a warning when
there is no or just one instruction (not a NOP instruction) between label
and RET or RET16:
Wnum: suspicious instruction concerning CPU functional
defect TC113_CPU11

You can suppress this warning with the option -wnum.

 CPU Functional Problems 9-27

TC113_CPU13
Assembler option:
--silicon-bug=cpu13

Assembler macro:
The assembler macro __TC113_CPU13__ is defined if you specify the
option --silicon-bug=cpu13.

Protected libraries to link:

lib\p\tc113\*.a (or add lib\src\cstart.asm to your project).

Compiler bypass:
There is no compiler bypass for this problem.

Assembler bypass:
To bypass this CPU functional problem, the assembler adds a macro to the
C startup code to enable the 16Kb D-Cache. The DCSIZ bits are set to
16Kb in the SFR register DMU_CON.

• • • • • • • •
 9-28 TriCore Reference Manual

TC113_CPU14
Compiler and assembler option:
--silicon-bug=cpu14

Assembler control:
$TC113_CPU14 {on|off}

Assembler macro:
The assembler macro __TC113_CPU14__ is defined if you specify the
option --silicon-bug=cpu14.
CPU FUNCTIONAL PROBLEMS

Protected libraries to link:

lib\p\tc113\*.a

Compiler bypass:
To bypass this CPU functional problem, the C compiler generates a DSYNC
instruction directly after a (interrupt) function entry point label. Also an
assembler macro is added to the run-time library functions for optionally
adding a DSYNC instruction after a function entry point label.

Assembler check:
The assembler gives a warning when the first label in a code section is not
followed by a DSYNC instruction:
Wnum: suspicious instruction concerning CPU functional
defect TC113_CPU14

You can suppress this warning with the option -wnum.

 CPU Functional Problems 9-29

TC113_CPU15
Compiler and assembler option:
--silicon-bug=cpu15

Assembler control:
$TC113_CPU15 {on|off}

Assembler macro:
The assembler macro __TC113_CPU15__ is defined if you specify the
option --silicon-bug=cpu15.

Protected libraries to link:

lib\p\tc113\*.a

Compiler bypass:
To bypass this CPU functional problem, the C compiler avoids generation
of the ST.T, SWAP and LDMST instructions. For immediate __bit and
bit-field operations alternative instructions are used.

Assembler check:
The assembler gives a warning for ST.T, SWAP and LDMST instructions:
Wnum: suspicious instruction concerning CPU functional
defect TC113_CPU15

You can suppress this warning with the option -wnum.

• • • • • • • •
 9-30 TriCore Reference Manual

TC113_CPU16
Compiler and assembler option:
--silicon-bug=cpu16

Assembler control:
$TC113_CPU16 {on|off}

Assembler macro:
The assembler macro __TC113_CPU16__ is defined if you specify the
option --silicon-bug=cpu16.
CPU FUNCTIONAL PROBLEMS

Protected libraries to link:

lib\p\tc113\*.a

Compiler bypass:
To bypass this CPU functional problem, the C compiler generates a NOP
instruction before a JI, JLI or CALLI instruction when there is not one
already. The compiler also generates a NOP instruction before a RET and
RET16 instruction if there is no or just one instruction before RET, starting
from the function entry point.

Assembler check:
The assembler gives a warning when a JI, JLI or CALLI instruction is not
directly preceded by a NOP instruction. The assembler also gives a
warning when there is no or just one instruction (not a NOP instruction)
between label and RET or RET16:
Wnum: suspicious instruction concerning CPU functional
defect TC113_CPU16

You can suppress this warning with the option -wnum.

 CPU Functional Problems 9-31

TC113_DMU1
Compiler and assembler option:
--silicon-bug=dmu1

Assembler control:
$TC113_DMU1 {on|off}

Assembler macro:
The assembler macro __TC113_DMU1__ is defined if you specify the
option --silicon-bug=dmu1.

Protected libraries to link:

lib\p\tc113\*.a

Compiler bypass:
To bypass this CPU functional problem, the C compiler avoids generation
of the ST.T, SWAP and LDMST instructions. For direct __bit and bit-field
operations, alternative instructions are used.

Assembler check:
The assembler gives a warning for SWAP, LDMST and ST.T instructions:
Wnum: suspicious instruction concerning CPU functional
defect TC113_DMU1

You can suppress this warning with the option -wnum.

• • • • • • • •
 9-32 TriCore Reference Manual

TC113_LFI2
Compiler and assembler option:
--silicon-bug=lfi2

Assembler control:
$TC113_LFI2 {on|off}

Assembler macro:
The assembler macro __TC113_LFI2__ is defined if you specify the
option --silicon-bug=lfi2.
CPU FUNCTIONAL PROBLEMS

Protected libraries to link:

lib\p\tc113\*.a

Compiler bypass:
To bypass this CPU functional problem, the C compiler avoids generation
of ST.T, SWAP and LDMST instructions. For immediate __bit and bit-field
operations alternative instructions are used.

Assembler check:
The assembler gives a warning for SWAP, LDMST and ST.T instructions:
Wnum: suspicious instruction concerning CPU functional
defect TC113_LFI2

You can suppress this warning with the option -wnum.

 CPU Functional Problems 9-33

TC113_LFI3
Compiler and assembler option:
--silicon-bug=lfi3

Assembler control:
$TC113_LFI3 {on|off}

Assembler macro:
The assembler macro __TC113_LFI3__ is defined if you specify the
option --silicon-bug=lfi3.

Protected libraries to link:

lib\p\tc113\*.a

Compiler bypass:
To bypass this CPU functional problem, the compiler avoids generation of
the ST.T, SWAP and LDMST instructions. For direct __bit and bit-field
operations alternative instructions are used.

Assembler check:
The assembler gives a warning for SWAP, LDMST and ST.T instructions:
Wnum: suspicious instruction concerning CPU functional
defect TC113_LFI3

You can suppress this warning with the option -wnum.

• • • • • • • •
 9-34 TriCore Reference Manual

TC113_PMU1
Assembler option:
--silicon-bug=pmu1

Protected libraries to link:

lib\p\tc113\*.a , or add lib\src\cstart.asm to your project.

Assembler macro:
The assembler macro __TC113_PMU1__ is defined if you specify the
option --silicon-bug=pmu1.
CPU FUNCTIONAL PROBLEMS

Compiler bypass:
There is no compiler bypass for this problem.

Assembler bypass:
To bypass this CPU functional problem, the assembler adds a macro to the
C startup code to disable the split mode on the LMB bus. The SPLT bit of
the SFR register LFI_CON is set to zero.
 CPU Functional Problems 9-35

TC113_PMU3
Assembler option:
--silicon-bug=pmu3

Assembler macro:
The assembler macro __TC113_PMU3__ is defined if you specify the
option --silicon-bug=pmu3.

Protected libraries to link:

lib\p\tc113\*.a (or add lib\src\cstart.asm to your project).

Compiler bypass:
There is no compiler bypass for this problem.

Assembler bypass:
To bypass this CPU functional problem, the assembler adds a macro to the
C startup code to set the TLB-A and TLB-B mappings to a page size of 16
Kb. The SZA and SZB in the MMU_CON are set to 16 Kb.

• • • • • • • •
 9-36 TriCore Reference Manual
CPU FUNCTIONAL PROBLEMS
CHAPTER

MISRA C RULES

10
 10-2 TriCore Reference Manual

CHAPTER
10
MISRA C
 MISRA C Rules 10-3

Supported and unsupported MISRA C rules

A number of MISRA C rules leave room for interpretation. Other rules can
only be checked in a limited way. In such cases the implementation
decisions and possible restrictions for these rules are listed.

1. The code shall conform to standard C, without language extensions

* 2. Other languages should only be used with an interface standard

3. Inline assembly is only allowed in dedicated C functions

* 4. Provision should be made for appropriate run-time checking

5. Only use characters and escape sequences defined by ISO C

* 6. Character values shall be restricted to a subset of ISO 106460-1

7. Trigraphs shall not be used

8. Multibyte characters and wide string literals shall not be used

9. Comments shall not be nested

10. Sections of code should not be "commented out"

In general, it is not possible to decide whether a piece of comment

is C code that is commented out, or just some pseudo code. Instead,
the following heuristics are used to detect possible C code inside a
comment:

- a line ends with ';', or

- a line starts with '}', possibly preceded by white space

11. Identifiers shall not rely on significance of more than 31 characters

12. The same identifier shall not be used in multiple name spaces

13. Specific-length typedefs should be used instead of the basic types

14. Use 'unsigned char' or 'signed char' instead of plain 'char'

* 15. Floating point implementations should comply with a standard

16. The bit representation of floating point numbers shall not be used

A violation is reported when a pointer to a floating point type is

converted to a pointer to an integer type.

• • • • • • • •
 10-4 TriCore Reference Manual

17. "typedef" names shall not be reused

18. Numeric constants should be suffixed to indicate type

A violation is reported when the value of the constant is outside the

range indicated by the suffixes, if any.

19. Octal constants (other than zero) shall not be used

20. All object and function identifiers shall be declared before use

21. Identifiers shall not hide identifiers in an outer scope

22. Declarations should be at function scope where possible

* 23. All declarations at file scope should be static where possible

24. Identifiers shall not have both internal and external linkage

* 25. Identifiers with external linkage shall have exactly one definition

26. Multiple declarations for objects or functions shall be compatible

* 27. External objects should not be declared in more than one file

28. The "register" storage class specifier should not be used

29. The use of a tag shall agree with its declaration

30. All automatics shall be initialized before being used

This rule is checked using worst-case assumptions. This means that

violations are reported not only for variables that are guaranteed to
be uninitialized, but also for variables that are uninitialized on some
execution paths.

31. Braces shall be used in the initialization of arrays and structures

32. Only the first, or all enumeration constants may be initialized

MISRA C

33. The right hand operand of && or || shall not contain side effects

34. The operands of a logical && or || shall be primary expressions

35. Assignment operators shall not be used in Boolean expressions

36. Logical operators should not be confused with bitwise operators

37. Bitwise operations shall not be performed on signed integers

 MISRA C Rules 10-5

38. A shift count shall be between 0 and the operand width minus 1

This violation will only be checked when the shift count evaluates
to a constant value at compile time.

39. The unary minus shall not be applied to an unsigned expression

40. "sizeof" should not be used on expressions with side effects

* 41. The implementation of integer division should be documented

42. The comma operator shall only be used in a "for" condition

43. Don't use implicit conversions which may result in information loss

44. Redundant explicit casts should not be used

45. Type casting from any type to or from pointers shall not be used

46. The value of an expression shall be evaluation order independent

This rule is checked using worst-case assumptions. This means that

a violation will be reported when a possible alias may cause the
result of an expression to be evaluation order dependent.

47. No dependence should be placed on operator precedence rules

48. Mixed arithmetic should use explicit casting

49. Tests of a (non-Boolean) value against 0 should be made explicit

50. F.P. variables shall not be tested for exact equality or inequality

51. Constant unsigned integer expressions should not wrap-around

52. There shall be no unreachable code

53. All non-null statements shall have a side-effect

54. A null statement shall only occur on a line by itself

55. Labels should not be used

56. The "goto" statement shall not be used

57. The "continue" statement shall not be used

58. The "break" statement shall not be used (except in a "switch")

• • • • • • • •
 10-6 TriCore Reference Manual

59. An "if" or loop body shall always be enclosed in braces

60. All "if", "else if" constructs should contain a final "else"

61. Every non-empty "case" clause shall be terminated with a "break"

62. All "switch" statements should contain a final "default" case

63. A "switch" expression should not represent a Boolean case

64. Every "switch" shall have at least one "case"

65. Floating point variables shall not be used as loop counters

66. A "for" should only contain expressions concerning loop control

A violation is reported when the loop initialization or loop update

expression modifies an object that is not referenced in the loop test.

67. Iterator variables should not be modified in a "for" loop

68. Functions shall always be declared at file scope

69. Functions with variable number of arguments shall not be used

70. Functions shall not call themselves, either directly or indirectly

A violation will be reported for direct or indirect recursive function

calls in the source file being checked. Recursion via functions in
other source files, or recursion via function pointers is not detected.

71. Function prototypes shall be visible at the definition and call

72. The function prototype of the declaration shall match the definition

73. Identifiers shall be given for all prototype parameters or for none

74. Parameter identifiers shall be identical for declaration/definition

75. Every function shall have an explicit return type

MISRA C

76. Functions with no parameters shall have a "void" parameter list

77. An actual parameter type shall be compatible with the prototype

78. The number of actual parameters shall match the prototype

79. The values returned by "void" functions shall not be used

 MISRA C Rules 10-7

80. Void expressions shall not be passed as function parameters

81. "const" should be used for reference parameters not modified

82. A function should have a single point of exit

83. Every exit point shall have a "return" of the declared return type

84. For "void" functions, "return" shall not have an expression

85. Function calls with no parameters should have empty parentheses

86. If a function returns error information, it should be tested

A violation is reported when a the return value of a function is

ignored.

87. #include shall only be preceded by another directives or comments

88. Non-standard characters shall not occur in #include directives

89. #include shall be followed by either <filename> or "filename"

90. Plain macros shall only be used for constants/qualifiers/specifiers

91. Macros shall not be #define'd and #undef'd within a block

92. #undef should not be used

93. A function should be used in preference to a function-like macro

94. A function-like macro shall not be used without all arguments

95. Macro arguments shall not contain pre-preprocessing directives

A violation is reported when the first token of an actual macro

argument is '#'.

96. Macro definitions/parameters should be enclosed in parentheses

97. Don't use undefined identifiers in pre-processing directives

98. A macro definition shall contain at most one # or ## operator

99. All uses of the #pragma directive shall be documented

This rule is really a documentation issue. The compiler will flag all
#pragma directives as violations.

• • • • • • • •
 10-8 TriCore Reference Manual

100. "defined" shall only be used in one of the two standard forms

101. Pointer arithmetic should not be used

102. No more than 2 levels of pointer indirection should be used

A violation is reported when a pointer with three or more levels of

indirection is declared.

103. No relational operators between pointers to different objects

In general, checking whether two pointers point to the same object

is impossible. The compiler will only report a violation for a
relational operation with incompatible pointer types.

104. Non-constant pointers to functions shall not be used

105. Functions assigned to the same pointer shall be of identical type

106. Automatic address may not be assigned to a longer lived object

107. The null pointer shall not be de-referenced

A violation is reported for every pointer dereference that is not

guarded by a NULL pointer test.

108. All struct/union members shall be fully specified

109. Overlapping variable storage shall not be used

A violation is reported for every 'union' declaration.

110. Unions shall not be used to access the sub-parts of larger types

A violation is reported for a 'union' containing a 'struct' member.

111. Bit fields shall have type "unsigned int" or "signed int"

112. Bit fields of type "signed int" shall be at least 2 bits long
MISRA C

113. All struct/union members shall be named

114. Reserved and standard library names shall not be redefined

115. Standard library function names shall not be reused

* 116. Production libraries shall comply with the MISRA C restrictions

* 117. The validity of library function parameters shall be checked

 MISRA C Rules 10-9

118. Dynamic heap memory allocation shall not be used

119. The error indicator "errno" shall not be used

120. The macro "offsetof" shall not be used

121. <locale.h> and the "setlocale" function shall not be used

122. The "setjmp" and "longjmp" functions shall not be used

123. The signal handling facilities of <signal.h> shall not be used

124. The <stdio.h> library shall not be used in production code

125. The functions atof/atoi/atol shall not be used

126. The functions abort/exit/getenv/system shall not be used

127. The time handling functions of library <time.h> shall not be used

* = Not supported by the TASKING TriCore C compiler

See also section 5.7, C Code Checking: MISRA C, in Chapter Using the
Compiler of the User's Manual.

• • • • • • • •
 10-10 TriCore Reference Manual
MISRA C
INDEX

INDEX
Index-2 TriCore Reference Manual

INDEX
INDEX
 Index Index-3

Symbols align, 1-26, 3-23

Alignment gaps, 8-42
#define, 5-13, 5-112 architecture definition, 8-3, 8-21
#include, 5-26 archiver options
#undef, 5-56 -?, 5-244
__BUILD__, 1-31 -d, 5-245
__REVISION__, 1-31 -p, 5-247
__VERSION__, 1-31 -m, 5-246
_close, 2-24 -r, 5-248
_Complex, 2-4 -t, 5-250
_Exit, 2-36 -V, 5-251
_fp_get_exception_mask, 4-15 -w, 5-253
_fp_get_exception_status, 4-16 -x, 5-252
_fp_install_trap_handler, 4-16 add module, 5-248
_fp_set_exception_mask, 4-15 create library, 5-248
_fp_set_exception_status, 4-16 delete module, 5-245
_fss_break, 2-10 extract module, 5-252
_fss_init, 2-10 move module, 5-246
_Imaginary, 2-4 print list of objects, 5-250
_IOFBF, 2-25 print list of symbols, 5-250
_IOLBF, 2-25 print module, 5-247
_IONBF, 2-25 replace module, 5-248
_lseek, 2-24 arg, 3-7
_open, 2-24 Argument, 2-5
_read, 2-24 ascii, 3-24
_START, 4-3 asciiz, 3-24
_tolower, 2-7 asctime, 2-42
_unlink, 2-24 asin functions, 2-13
_write, 2-24 asinh functions, 2-13
asn, 3-7
aspcp, 3-7
assembler controls
A $case, 3-66
$debug, 3-67
abort, 2-36 $fpu, 3-68
abs, 2-37, 3-6 $hw_only, 3-69
access, 2-44 $ident, 3-70
accum, 3-22 $list, 3-73
acos functions, 2-13 $list on/off, 3-71
acosh functions, 2-14 $mmu, 3-75
acs, 3-7 $object, 3-76
address spaces, 8-23 $page, 3-77
alias, 1-26

• • • • • • • •
Index-4 TriCore Reference Manual

$prctl, 3-79 macros (overview), 3-21

$stitle, 3-80 message, 3-47
$tc, 3-81 org, 3-48
$tc2, 3-82 overview, 3-19
$title, 3-83 pmacro, 3-50
$warning off, 3-84 sdecl, 3-51
detailed description, 3-65 sect, 3-54
listing controls (overview), 3-64 set, 3-55
miscellaneous (overview), 3-64 sfract, 3-39
overview, 3-64 size, 3-56
assembler directives space, 3-57
accum, 3-22 storage allocation (overview), 3-20
align, 3-23 symbol definitions (overview), 3-20
ascii, 3-24 type, 3-58
asciiz, 3-24 undef, 3-59
assembly control (overview), 3-19 warning, 3-60
byte, 3-25 weak, 3-61
calls, 3-26 word, 3-62
comment, 3-27 assembler list file, 5-90
conditional assembly (overview), assembler options
3-21 -?, 5-68
data definition (overview), 3-20 --case-sensitive, 5-71
debug information (overview), 3-21 --check, 5-72
define, 3-28 --cpu, 5-69
detailed description, 3-21 --debug-info, 5-82
double, 3-38 --define, 5-73
dup/endm, 3-29 --diag, 5-75
dupa/endm, 3-30 --emit-locals, 5-77
dupc/endm, 3-31 --error-file, 5-78
dupf/endm, 3-32 --fpu-present, 5-81
end, 3-33 --help, 5-68
equ, 3-34 --include-directory, 5-85
exitm, 3-35 --include-file, 5-84
extern, 3-36 --is-tricore2, 5-88
fail, 3-37 --keep-output-files, 5-89
float, 3-38 --list-file, 5-92
fract, 3-39 --list-format, 5-90
global, 3-40 --mmu-present, 5-94
INDEX

half, 3-62 --no-tasking-sfr, 5-95

if, 3-41 --no-warnings, 5-103
include, 3-43 --optimize, 5-96
local, 3-44 --option-file, 5-79
macro/endm, 3-45 --output, 5-97
 Index Index-5

--preprocessor-type, 5-93 def, 3-10

--section-info, 5-100 exp, 3-10
--silicon-bug, 5-98 fld, 3-10
--symbol-scope, 5-87 flr, 3-11
--version, 5-102 hi, 3-11
--warnings-as-errors, 5-105 his, 3-11
-C, 5-69 int, 3-11
-c, 5-71 l10, 3-12
-D, 5-73 len, 3-12
-f, 5-79 lng, 3-12
-g, 5-82 lo, 3-12
-H, 5-84 log, 3-12
-I, 5-85 los, 3-13
-i, 5-87 lsb, 3-13
-k, 5-89 lst, 3-13
-L, 5-90 lun, 3-13
-l, 5-92 mac, 3-14
-m, 5-93 macros (overview), 3-5
-O, 5-96 mathematical (overview), 3-4
-o, 5-97 max, 3-14
-t, 5-100 min, 3-14
-V, 5-102 msb, 3-14
-w, 5-103 mxp, 3-14
assembly functions pos, 3-15
abs, 3-6 pow, 3-15
acs, 3-7 rnd, 3-15
address calculation (overview), 3-6 rvb, 3-15
arg, 3-7 scp, 3-16
asn, 3-7 sfract, 3-16
aspcp, 3-7 sgn, 3-16
assembler mode (overview), 3-6 sin, 3-16
astc, 3-7 snh, 3-16
at2, 3-8 sqt, 3-17
atn, 3-8 strings (overview), 3-5
fract, 3-8, 3-11 sub, 3-17
cel, 3-8 syntax, 3-3
cnt, 3-8 tan, 3-17
coh, 3-9 tnh, 3-17
conversions (overview), 3-5 unf, 3-17
cos, 3-9 xpn, 3-18
cpu, 3-9 astc, 3-7
cvf, 3-9 at2, 3-8
cvi, 3-9 atan functions, 2-13

• • • • • • • •
Index-6 TriCore Reference Manual

atan2 functions, 2-13 cexp, 2-5

atanh functions, 2-14 char type, treat as unsigned, 5-58
atexit, 2-36 chdir, 2-44
atn, 3-8 check source code, 5-11, 5-72, 5-160
atof, 2-34 cimag, 2-5
atoi, 2-34 clear/noclear, 1-26
atol, 2-34 clearerr, 2-33
atoll, 2-34 clock, 2-42
clock_t, 2-41
CLOCKS_PER_SEC, 2-42

B clog, 2-5
close, 2-44
bit handling, 1-23 cnt, 3-8
board specification, 8-5, 8-33 coh, 3-9
bsearch, 2-36 command file, 5-21, 5-79, 5-120,
btowc, 2-46 5-169, 5-229
BUFSIZ, 2-23 comment, 3-27
bus definition, 8-4 comments, 8-7
buses, 8-23 common subexpression elimination,
byte, 3-25 5-12
compiler options
-?, 5-4

C
--align, 5-7
--check, 5-11
--cpu, 5-8
C library, reentrancy, 2-48 --cse-all-addresses, 5-12
cabs, 2-5 --debug-info, 5-24
cacos, 2-5 --default-a0-size, 5-65
cacosh, 2-5 --default-a1-size, 5-63
calloc, 2-35 --default-near-size, 5-37
calls, 3-26 --define, 5-13
carg, 2-5 --diag, 5-15
case, 3-66 --error-file, 5-19
case sensitivity, 5-111 --fpu-present, 5-23
casin, 2-5 --help, 5-4
casinh, 2-5 --include-directory, 5-26
cat, 3-8 --include-file, 5-25
catan, 2-5 --indirect, 5-28
INDEX

catanh, 2-5 --indirect-runtime, 5-29

cbrt functions, 2-17 --inline, 5-30
ccos, 2-5 --inline-max-incr, 5-31
ccosh, 2-5 --inline-max-size, 5-31
ceil functions, 2-15 --integer-enumeration, 5-33
cel, 3-8
 Index Index-7

--is-tricore2, 5-34 -u, 5-58

--iso, 5-10 -V, 5-59
--keep-output-files, 5-35 -w, 5-60
--language, 5-5 -Y, 5-63
--misrac, 5-36 -Z, 5-65
--no-double, 5-20 complex, 2-4
--no-tasking-sfr, 5-40 conditional make rules, 5-215
--no-warnings, 5-60 conj, 2-5
--object-comment, 5-45 Conjugate value, 2-5
--option-file, 5-21 control program options
--output, 5-44 -?, 5-153
--preprocess, 5-17 --address-size, 5-156
--rename-sections, 5-46 --case-sensitive, 5-158
--section-per-data-object, 5-49 --check, 5-160
--silicon-bug, 5-50, 5-53 --cpu, 5-157
--source, 5-48 --create, 5-159
--static, 5-52 --d, 5-163
--stdout, 5-39 --debug-info, 5-178
--tradeoff, 5-55 --define, 5-161
--uchar, 5-58 --diag, 5-164
--undefine, 5-56 --dry-run, 5-192
--version, 5-59 --error-file, 5-166
--warnings-as-errors, 5-62 --exeptions, 5-167
-A, 5-5 --force-c, 5-171
-C, 5-8 --force-c++, 5-172
-c, 5-10 --force-munch, 5-173
-D, 5-13 --force-prelink, 5-174
-E, 5-17 --format, 5-175
-F, 5-20 --fptrap, 5-176
-f, 5-21 --fpu-present, 5-177
-g, 5-24 --help, 5-153
-H, 5-25 --ignore-default-library-path,
-I, 5-26 5-187
-k, 5-35 --include-directory, 5-179
-N, 5-37 --instantiate, 5-180
-n, 5-39 --instantiation-dir, 5-182
--optimize, 5-41 --instantiation-file, 5-183
-O, 5-41 --is-tricore2, 5-184
-o, 5-44 --iso, 5-185
-R, 5-46 --keep-output-files, 5-186
-s, 5-48 --keep-temporary-files, 5-207
-t, 5-55 --language, 5-154
-U, 5-56 --library, 5-189

• • • • • • • •
Index-8 TriCore Reference Manual

--library-directory, 5-187 -g, 5-178

--list-object-files, 5-190 -I, 5-179
--lsl-file, 5-163 -k, 5-186
--mmu-present, 5-191 -L, 5-187
--no-auto-instantiation, 5-193 -l, 5-189
--no-default-libraries, 5-194 -n, 5-192
--no-double, 5-168 -o, 5-198
--no-map-file, 5-195 -t, 5-207
--no-one-instantiation-per-object, -U, 5-208
5-196 -V, 5-209
--no-tasking-sfr, 5-197 -v, 5-210
--no-warnings, 5-212 -W, 5-211
--option-file, 5-169 -w, 5-212
--output, 5-198 -Wa, 5-211
--pass, 5-211 -Wc, 5-211
--pass-assembler, 5-211 -Wcp, 5-211
--pass-c, 5-211 -Wl, 5-211
--pass-linker, 5-211 -Wpl, 5-211
--pass-c++, 5-211 controls
--pass-prelinker, 5-211 See also assembler directives
--prelink-copy-if-non-local, 5-199 detailed description, 3-65
--prelink-local-only, 5-200 copy table, 5-137, 8-25, 8-48
--prelink-remove-instantiation-flags copysign functions, 2-17
, 5-201 core type, 5-69
--preprocess, 5-165 cos, 3-9
--show-c++-warnings, 5-202 cos functions, 2-13
--silicon-bug, 5-203 cosh functions, 2-13
--space, 5-205 cpow, 2-5
--static, 5-206 cproj, 2-6
--undefine, 5-208 cpu, 3-9
--verbose, 5-210 CPU type, 5-8, 5-69, 5-157
--version, 5-209 creal, 2-6
--warnings-as-errors, 5-213 CSE, 5-12
-A, 5-154 csin, 2-5
-C, 5-157 csinh, 2-5
-cc, 5-159 csqrt, 2-5
-cl, 5-159 cstart.asm, 4-3
-co, 5-159 ctan, 2-5
INDEX

-cs, 5-159 ctanh, 2-5

-D, 5-161 ctime, 2-42
-E, 5-165 cvf, 3-9
-F, 5-168 cvi, 3-9
-f, 5-169 cycle count, 5-100
 Index Index-9

D EXIT_SUCCES, 2-34
exitm, 3-35
data types, 1-4 exp, 3-10
debug, 3-67 exp functions, 2-14
debug information, 5-24, 5-82, 5-146 exp2 functions, 2-14
def, 3-10 expm1 functions, 2-14
default_a0_size, 1-27 extension isuffix, 1-27
default_a1_size, 1-27 extern, 1-27, 3-36
default_near_size, 1-27
define, 3-28
derivative definition, 8-4, 8-29
difftime, 2-42
F
directives fabs functions, 2-17
See also assembler directives fail, 3-37
detailed description, 3-21 fclose, 2-24
div, 2-37 fdim functions, 2-18
double, 3-38 FE_ALL_EXCEPT, 2-10
dup, 3-29 FE_DIVBYZERO, 2-10
dupa, 3-30 FE_INEXACT, 2-10
dupc, 3-31 FE_INVALID, 2-10
dupf, 3-32 FE_OVERFLOW, 2-10
FE_UNDERFLOW, 2-10
feclearexcept, 2-9

E fegetenv, 2-9
fegetexceptflag, 2-9
ELF/DWARF object format, 7-3 feholdexept, 2-9
elif, 3-41 feof, 2-33
else, 3-41 feraiseexcept, 2-9
end, 3-33 ferror, 2-33
endif, 3-41 fesetenv, 2-9
enum, 5-33 fesetexceptflag, 2-9
EOF, 2-23 fetestexcept, 2-9, 2-10
equ, 3-34 feupdateenv, 2-9
erf functions, 2-18 fflush, 2-24
erfc functions, 2-18 fgetc, 2-29
errno, 2-7 fgetpos, 2-32
errno declaration, 2-59 fgets, 2-29
errno.h, 2-59 fgetwc, 2-29
exceptions, floating-point, 4-13 fgetws, 2-29
exit, 2-36 File system simulation, 2-4
exit macro, 3-35 FILENAME_MAX, 2-23
EXIT_FAILURE, 2-34 fld, 3-10

• • • • • • • •
Index-10 TriCore Reference Manual

float, 3-38
floating-point, 4-10 G
libraries, 4-13 getc, 2-29
single precision, 5-23, 5-81, 5-177 getchar, 2-29
special values, 4-13 getcwd, 2-44
trap handler, 4-14 getenv, 2-36
trap handling api, 4-15 gets, 2-29
trapping, 4-13 getwc, 2-29
floor functions, 2-15 getwchar, 2-29
flr, 3-11 global, 3-40
fma functions, 2-17 gmtime, 2-42
fmax functions, 2-18
fmin functions, 2-18
fmod functions, 2-16
fopen, 2-24
FOPEN_MAX, 2-23
H
for_constant_data_use_memory, 1-28 half, 3-62
for_extern_data_use_memory, 1-28 Header files, 2-4
for_initialized_data_use_memory, 1-28 alert.h, 2-4
for_uninitialized_data_use_memory, complex.h, 2-4
1-28 ctype.h, 2-6
fpclassify, 2-19 errno.h, 2-7
fprintf, 2-31 fcntl.h, 2-9
fputc, 2-30 fenv.h, 2-9
fputs, 2-30 float.h, 2-10
fputwc, 2-30 fss.h, 2-10
fputws, 2-30 inttypes.h, 2-11
fract, 3-11, 3-39 iso646.h, 2-12
fractional arithmetic support, 1-14 limits.h, 2-12
fread, 2-32 locale.h, 2-12
free, 2-35 math.h, 2-13
freopen, 2-25 setjmp.h, 2-20
frexp functions, 2-16 signal.h, 2-20
fscanf, 2-29 stdarg.h, 2-21
fseek, 2-32 stdbool.h, 2-21
fsetpos, 2-32 stddef.h, 2-22
FSS, 2-4 stdint.h, 2-11
ftell, 2-32 stdio.h, 2-22
INDEX

functional problems, 9-3 stdlib.h, 2-33

functions, assembly, 3-3 string.h, 2-37
fwprintf, 2-31 tgmath.h, 2-13
fwrite, 2-32 time.h, 2-41
fwscanf, 2-29 unistd.h, 2-44
 Index Index-11

wchar.h, 2-22, 2-37, 2-41, 2-45 isdigit, 2-6

wctype.h, 2-6, 2-46 isfinite, 2-19
heap, 4-10, 8-24 isgraph, 2-6
begin of, 4-10 isgreater, 2-19
end of, 4-10 isgreaterequal, 2-19
hi, 3-11 isinf, 2-19
his, 3-11 isless, 2-19
hw_only, 3-69 islessequal, 2-19
hypot functions, 2-17 islessgreater, 2-19
islower, 2-6
isnan, 2-19

I isnormal, 2-19
ISO C standard, 5-10
ident, 3-70 isprint, 2-6
if, 3-41 ispunct, 2-6
ilogb functions, 2-14 isspace, 2-6
imaginary, 2-4 isunordered, 2-19
imaxabs, 2-11 isupper, 2-6
imaxdiv, 2-11 iswalnum, 2-6, 2-46
include, 3-43 iswalpha, 2-6, 2-46
indirect, 1-28 iswblank, 2-6
indirect function calling, 5-28, 5-29 iswcntrl, 2-6, 2-46
indirect_runtime, 1-28 iswctype, 2-46
inline functions, 5-31 iswdigit, 2-6, 2-46
inline/noinline, 1-28 iswgraph, 2-6, 2-46
insert assembly instruction, 1-21 iswlower, 2-6, 2-47
int, 3-11 iswprint, 2-6, 2-47
Intel hex, record type, 7-8 iswpunct, 2-6, 2-47
interrupt handling, 1-19 iswspace, 2-6, 2-47
intrinsic functions, 1-12 iswupper, 2-6, 2-47
bit handling, 1-23 iswxdigit, 2-6
fractional data type, 1-14 iswxditig, 2-47
insert assembly instruction, 1-21 isxdigit, 2-6
interrupt handling, 1-19
min/max of integers, 1-13
miscellaneous, 1-25
packed data type, 1-15
L
register handling, 1-22 L_tmpnam, 2-23
iob structures, 2-59 l10, 3-12
isalnum, 2-6 labs, 2-37
isalpha, 2-6 language extensions, intrinsic
isblank, 2-6 functions, 1-12
iscntrl, 2-6 ldexp functions, 2-16

• • • • • • • •
Index-12 TriCore Reference Manual

ldiv, 2-37 -d, 5-113

len, 3-12 -e, 5-117
lgamma functions, 2-18 -f, 5-120
linker map file, 5-132 -I, 5-123
linker options -i, 5-124
-?, 5-108 -k, 5-125
--case-insensitive, 5-111 -L, 5-126
--chip-output, 5-109 -l, 5-128
--define, 5-112 -M, 5-132
--diag, 5-115 -m, 5-133
--error-file, 5-119 -N, 5-137
--extern, 5-117 -O, 5-141
--first-library-first, 5-122 -o, 5-143
--help, 5-108 -r, 5-145
--ignore-default-library-path, -S, 5-146
5-126 -t, 5-148
--include-directory, 5-123 -V, 5-147
--incremental, 5-145 -v, 5-148
--keep-output-files, 5-125 -w, 5-149
--library, 5-128 linker script file
--library-directory, 5-126 architecture definition, 8-3
--link-only, 5-129 boad specification, 8-5
--lsl-check, 5-130 bus definition, 8-4
--lsl-dump, 5-131 derivative definition, 8-4
--map-file, 5-132 memory definition, 8-4
--map-file-format, 5-133 preprocessing, 8-6
--misra-c-report, 5-135 processor definition, 8-4
--munch, 5-136 section layout definition, 8-5
--no-rescan, 5-138 structure, 8-3
--no-rom-copy, 5-137 list, 3-73
--no-warnings, 5-149 list file, 5-92
--non-romable, 5-140 assembler, 5-90
--optimize, 5-141 linker, 5-132
--option-file, 5-120 list on/off, 3-71
--output-file, 5-143 llabs, 2-37
--strip-debug, 5-146 lldiv, 2-37
--user-provided-initialization-code, llrint functions, 2-15
5-124 llround functions, 2-15
INDEX

--verbose, 5-148 lng, 3-12

--version, 5-147 lo, 3-12
--warnings-as-errors, 5-151 local, 3-44
-c, 5-109 localeconv, 2-13
-D, 5-112 localtime, 2-42
 Index Index-13

log, 3-12 heap, 8-24, 8-46

log functions, 2-14 high_to_low, 8-24, 8-38
log10 functions, 2-14 id, 8-23
log1p functions, 2-14 if, 8-49
log2 functions, 2-14 load_addr, 8-44
logb functions, 2-14 low_to_high, 8-24, 8-38
longjmp, 2-20 map, 8-23, 8-24, 8-26, 8-31
los, 3-13 mau, 8-23, 8-31, 8-35
lrint functions, 2-15 mem, 8-43
lround functions, 2-15 memory, 8-31, 8-35
lsb, 3-13 min_size, 8-24, 8-45, 8-46
lseek, 2-44 nvram, 8-31
LSL expression evaluation, 8-20 ordered, 8-41
LSL functions overlay, 8-42
absolute(), 8-9 page, 8-44
addressof(), 8-9 page_size, 8-24
exists(), 8-10 processor, 8-33
max(), 8-10 ram, 8-31
min(), 8-10 reserved, 8-31, 8-46
sizeof(), 8-10 rom, 8-31
LSL keywords run_addr, 8-25, 8-43
align, 8-23, 8-24, 8-25, 8-41 section, 8-47
alloc_allowed, 8-46 section_layout, 8-38
allow_cross_references, 8-42 select, 8-39
architecture, 8-22, 8-30 size, 8-26, 8-31, 8-35, 8-45, 8-46,
attributes, 8-40, 8-41 8-47
bus, 8-23, 8-26, 8-35 space, 8-23, 8-26
clustered, 8-42 speed, 8-31, 8-35
contiguous, 8-41 src_dbits, 8-27
copy_unit, 8-25 src_offset, 8-26
copytable, 8-25, 8-48 stack, 8-24, 8-45
core, 8-30 start_address, 8-25
derivative, 8-29, 8-34 symbol, 8-25
dest, 8-25, 8-26 type, 8-31, 8-35
dest_dbits, 8-27 width, 8-23
dest_offset, 8-26 LSL syntax, 8-6
direction, 8-38, 8-41 lst, 3-13
else, 8-49 lun, 3-13
extends, 8-22, 8-29
fill, 8-42, 8-46, 8-48
fixed, 8-24, 8-45, 8-46
group, 8-39, 8-40
grows, 8-24

• • • • • • • •
Index-14 TriCore Reference Manual

M -V, 5-239
-W, 5-240
mac, 3-14 -w, 5-241
macro, 3-45 -x, 5-242
define, 5-161 defining a macro, 5-215
definition, 3-45 malloc, 2-35
undefine, 3-50, 5-208 map file
macro/nomacro, 1-28 control program option, 5-195
macros, 1-31 format, 5-133
make utility, 5-215 linker, 5-132
macros, predefined mappings, 8-26
__DATE__, 5-56 max, 3-14
__FILE__, 5-56 MB_CUR_MAX, 2-34, 2-45
__LINE__, 5-56 MB_LEN_MAX, 2-45
__STDC__, 5-56 mblen, 2-37
__TIME__, 5-56 mbrlen, 2-46
Magnitude, 2-5 mbrtowc, 2-45
make utility options mbsinit, 2-45
-?, 5-217 mbsrtowcs, 2-45
-a, 5-218 mbstate_t, 2-45
-c, 5-219 mbstowcs, 2-37
-D, 5-220 mbtowc, 2-37
-d, 5-221 memchr, 2-40
-DD, 5-220 memcmp, 2-39
-dd, 5-221 memcpy, 2-38
-e, 5-222 memmove, 2-38
-err, 5-223 memory definition, 8-4
-f, 5-224 memory management instructions,
-G, 5-225 5-94, 5-191
-i, 5-226 memset, 2-41
-K, 5-227 message, 1-28, 3-47
-k, 5-228 min, 3-14
-m, 5-229, 5-235 min/max of integers, 1-13
-n, 5-231 MISRA C, 5-36
-p, 5-232 supported rules, 10-3
-q, 5-233 mktime, 2-42
-r, 5-234 fpu, 3-68
mmu, 3-75
INDEX

-s, 5-236
-t, 5-237 modf functions, 2-16
-time, 5-238 Modulus, 2-5
 Index Index-15

msb, 3-14 Pragma

mxp, 3-14 extern, 1-27
indirect, 1-28
indirect_runtime, 1-28

N macro, 1-28
message, 1-28
nan functions, 2-17 object_comment, 1-29
nearbyint functions, 2-15 tradeoff, 1-30
nextafter functions, 2-17 warning, 1-30
nexttoward functions, 2-17 weak, 1-30
Norm, 2-5 Pragmas
NULL, 2-22 alias, 1-26, 1-30
align, 1-26
clear/noclear, 1-26

O
default_a0_size, 1-27
default_a1_size, 1-27
default_near_size, 1-27
object, 3-76 extension isuffix, 1-27
object_comment, 1-29 for_constant_data_use_memory,
offsetof, 2-22 1-28
open, 2-9 for_extern_data_use_memory, 1-28
optimization, 5-41, 5-96, 5-141 for_initialized_data_use_memory,
optimize/endoptimize, 1-29 1-28
option file, 5-21, 5-79, 5-120, 5-169, for_uninitialized_data_use_memory,
5-229 1-28
org, 3-48 inline/noinline, 1-28
output file, 5-44, 5-97, 5-143, 5-198 optimize/endoptimize, 1-29
output format, 5-109, 5-175 pack, 1-29
section, 1-29
section all, 1-29
P section code_init, 1-29
section const_init, 1-29
pack, 1-29 section data_overlay, 1-29
packed data type support, 1-15 section vector_init, 1-29
page, 3-77 smartinline, 1-28
pass option to tool, 5-211 source/nosource, 1-29
perror, 2-33 pragmas, 1-26
Phase angle, 2-5 prctl, 3-79
pmacro, 3-50 predefined macros, 1-31
pos, 3-15 predefined macros in C
pow, 3-15 __CTC__, 1-31
pow functions, 2-17 __DOUBLE_FP__, 1-31
power-on vector, 4-3 __DSPC__, 1-31

• • • • • • • •
Index-16 TriCore Reference Manual

__DSPC_VERSION__, 1-31
__FPU__, 1-31 S
__SINGLE_FP__, 1-31 scalbln functions, 2-16
__TASKING__, 1-31 scalbn functions, 2-16
preprocessing, 8-6 scanf, 2-27, 2-30
preprocessor, 5-93 conversion characters, 2-28
printf, 2-25, 2-31 scp, 3-16
conversion characters, 2-27 sdecl, 3-51
processor definition, 8-4, 8-33 sect, 3-54
ptrdiff_t, 2-22 section, 1-29
putc, 2-30 summary, 5-100
putchar, 2-30 section activation, 3-54
puts, 2-31 section all, 1-29
putwc, 2-30 section attributes, 3-51
putwchar, 2-30 section code_init, 1-29
section data_overlay, 1-29
section declaration, 3-51
Q section layout definition, 8-5, 8-37
section names, 3-52
qsort, 2-36 sections
grouping, 8-39
rename, 5-46
R SEEK_CUR, 2-32
SEEK_END, 2-32
raise, 2-20 SEEK_SET, 2-32
rand, 2-35 set, 3-55
RAND_MAX, 2-34 setbuf, 2-25
read, 2-44 setjmp, 2-20
realloc, 2-35 setlocale, 2-12
reentrancy, 2-48 setvbuf, 2-25
register handling, 1-22 sfract, 3-16, 3-39
remainder functions, 2-16 sgn, 3-16
remove, 2-33 SIGABRT, 2-20
remquo functions, 2-16 SIGFPE, 2-20
rename, 2-33 SIGFPE signal handler, 4-14
rename sections, 5-46 SIGILL, 2-20
reset vector, 8-25 SIGINT, 2-20
INDEX

rewind, 2-32 signal, 2-20

Riemann sphere, 2-6 signbit, 2-19
rint functions, 2-15 SIGSEGV, 2-20
rnd, 3-15 SIGTERM, 2-20
round functions, 2-15 silicon bug workaround, 5-50, 5-98,
rvb, 3-15 5-203
 Index Index-17

sin, 3-16 strtol, 2-35

sin functions, 2-13 strtold, 2-34
sinh functions, 2-13 strtoll, 2-35
size, 3-56 strtoul, 2-35
size_t, 2-22 strtoull, 2-35
smartinline, 1-28 strtoumax, 2-11
snh, 3-16 strxfrm, 2-39
snprintf, 2-31 sub, 3-17
source/nosource, 1-29 switch auto, 1-30
space, 3-57 switch jumptab, 1-30
sprintf, 2-31 switch linear, 1-30
sqrt functions, 2-17 switch lookup, 1-30
sqt, 3-17 switch restore, 1-30
srand, 2-35 switch statement, 5-53
sscanf, 2-30 swprintf, 2-31
stack, 4-9, 8-24 swscanf, 2-30
begin of, 4-9 syntax error checking, 5-11, 5-72,
start address, 8-25 5-160
startup code, 4-3 system, 2-36
stat, 2-44 system libraries, 5-126, 5-128
stderr, 2-23
stdin, 2-23
stdout, 2-23
stitle, 3-80 T
strcat, 2-38 tan, 3-17
strchr, 2-40 tan functions, 2-13
strcmp, 2-39 tanh functions, 2-13
strcoll, 2-39 tc, 3-81
strcpy, 2-38 tc2, 3-82
strcspn, 2-40 temporary files, 5-207
strerror, 2-41 tgamma functions, 2-18
strftime, 2-43 time, 2-42
strncat, 2-38 time_t, 2-41
strncmp, 2-39 tm (struct), 2-41
strncpy, 2-38 TMP_MAX, 2-23
strpbrk, 2-40 tmpfile, 2-33
strrchr, 2-40 tmpnam, 2-33
strspn, 2-40 tnh, 3-17
strstr, 2-40 tolower, 2-7
strtod, 2-34 toupper, 2-7
strtof, 2-34 towctrans, 2-47
strtoimax, 2-11 towlower, 2-7, 2-47
strtok, 2-40

• • • • • • • •
Index-18 TriCore Reference Manual

towupper, 2-7, 2-47

tradeoff, 1-30 W
trap, 4-18 warning, 1-30, 3-60
trap handler, 4-14 title, 3-83, 3-84
trap handling, 5-176 warnings, 5-213
trap handling api, 4-15 suppress, 5-103
TriCore 2 instructions, 5-34, 5-88, warnings as errors, 5-62, 5-105, 5-151
5-184 warnings, suppress, 5-60, 5-149
trunc functions, 2-15 wchar_t, 2-22
type, 3-58 wcrtomb, 2-46
wcscat, 2-38
wcschr, 2-40
U wcscmp, 2-39
wcscoll, 2-39
undef, 3-59 wcscpy, 2-38
unf, 3-17 wcscspn, 2-40
ungetc, 2-29 wcsncat, 2-38
ungetwc, 2-29 wcsncmp, 2-39
unlink, 2-44 wcsncpy, 2-38
wcspbrk, 2-40
wcsrchr, 2-40
V wcsrtombs, 2-45
wcsspn, 2-40
va_arg, 2-21 wcsstr, 2-40
va_end, 2-21 wcstod, 2-34
va_start, 2-21 wcstof, 2-34
verbose, 5-148, 5-210 wcstoimax, 2-11
version information, 5-59, 5-102, wcstok, 2-40
5-147, 5-209, 5-239, 5-240, 5-251 wcstol, 2-35
vfprintf, 2-31 wcstold, 2-34
vfscanf, 2-30 wcstoll, 2-35
vfwprintf, 2-31 wcstombs, 2-37
vfwscanf, 2-30 wcstoul, 2-35
vprintf, 2-31 wcstoull, 2-35
vscanf, 2-30 wcstoumax, 2-11
vsprintf, 2-31 wcsxfrm, 2-39
vsscanf, 2-30 wctob, 2-46
INDEX

vswprintf, 2-31 wctomb, 2-37

vswscanf, 2-30 wctrans, 2-47
vwprintf, 2-31 wctype, 2-46
vwscanf, 2-30 weak, 1-30, 3-61
 Index Index-19

WEOF, 2-23 write, 2-44

wmemchr, 2-40 wscanf, 2-30
wmemcmp, 2-39 wstrftime, 2-43
wmemcpy, 2-38
wmemmove, 2-38
wmemset, 2-41
word, 3-62 X
wprintf, 2-31 xpn, 3-18

• • • • • • • •
Index-20 TriCore Reference Manual
INDEX