iar assemblernetstorage.iar.com/.../007248/ew/doc/ewrx_assemblerguide.enu.pdf · assembler...

ARX-2

IAR Assembler™

Reference Guide

for the RenesasRX Microprocessor Family

ARX-2

ARX-2

COPYRIGHT NOTICECopyright © 2009–2010 IAR Systems AB.

No part of this document may be reproduced without the prior written consent of IAR Systems AB. The software described in this document is furnished under a license and may only be used or copied in accordance with the terms of such a license.

DISCLAIMERThe information in this document is subject to change without notice and does not represent a commitment on any part of IAR Systems. While the information contained herein is assumed to be accurate, IAR Systems assumes no responsibility for any errors or omissions.

In no event shall IAR Systems, its employees, its contractors, or the authors of this document be liable for special, direct, indirect, or consequential damage, losses, costs, charges, claims, demands, claim for lost profits, fees, or expenses of any nature or kind.

TRADEMARKSIAR Systems, IAR Embedded Workbench, C-SPY, visualSTATE, From Idea To Target, IAR KickStart Kit, IAR PowerPac, IAR YellowSuite, IAR Advanced Development Kit, IAR, and the IAR Systems logotype are trademarks or registered trademarks owned by IAR Systems AB. J-Link is a trademark licensed to IAR Systems AB.

Microsoft and Windows are registered trademarks of Microsoft Corporation.

Renesas Electronics is a registered trademark of Renesas Electronics Corporation. RX is a trademark of Renesas Electronics Corporation.

Adobe and Acrobat Reader are registered trademarks of Adobe Systems Incorporated.

All other product names are trademarks or registered trademarks of their respective owners.

EDITION NOTICE

Second edition: June 2010

Part number: ARX-2

This guide applies to version 2.x of IAR Embedded Workbench® for the Renesas RX microcontroller family.

Internal reference: M3, asrct2010.2, IJOA.

ContentsTables ....................................................................................................................... ix

Preface ..................................................................................................................... xi

Who should read this guide ................................................................xi

How to use this guide ............................................................................xi

What this guide contains .....................................................................xii

Other documentation ...........................................................................xii

Document conventions ........................................................................xii

Typographic conventions ..................................................................xiii

Naming conventions .........................................................................xiii

Introduction to the IAR Assembler™ for RX .................................... 1

Introduction to assembler programming ...................................... 1

Getting started ...................................................................................... 1

Modular programming ........................................................................... 2

External interface details ...................................................................... 3

Assembler invocation syntax ............................................................... 3

Passing options ..................................................................................... 3

Environment variables ......................................................................... 4

Error return codes ................................................................................. 4

Source format ............................................................................................ 5

RX architecture considerations ......................................................... 5

Assembler instructions ......................................................................... 5

Code and data in big-endian applications ............................................ 6

Expressions, operands, and operators ............................................. 6

Integer constants .................................................................................. 6

ASCII character constants .................................................................... 7

Floating-point constants ....................................................................... 7

TRUE and FALSE ............................................................................... 8

Symbols ................................................................................................ 8

Labels ................................................................................................... 9

Register symbols .................................................................................. 9

ARX-2

iii

iv

Predefined symbols .............................................................................. 9

Absolute and relocatable expressions ................................................ 12

Expression restrictions ....................................................................... 12

List file format .......................................................................................... 13

Header ................................................................................................ 13

Body ................................................................................................... 13

Summary ............................................................................................ 13

Symbol and cross-reference table ...................................................... 13

Programming hints ................................................................................ 14

Using C-style preprocessor directives ................................................ 14

Assembler options ........................................................................................... 15

Setting command line assembler options ................................... 15

Specifying parameters ........................................................................ 16

Summary of assembler options ........................................................ 16

Description of assembler options .................................................... 18

Assembler operators ...................................................................................... 35

Precedence of operators ..................................................................... 35

Summary of assembler operators ................................................... 35

Parenthesis operator – 1 ..................................................................... 35

Function operators – 2 ........................................................................ 36

Unary operators – 3 ............................................................................ 36

Multiplicative arithmetic operators – 4 .............................................. 36

Additive arithmetic operators – 5 ....................................................... 36

Shift operators – 6 .............................................................................. 37

Comparison operators – 7 .................................................................. 37

Equivalence operators – 8 .................................................................. 37

Logical operators – 9-14 .................................................................... 37

Conditional operator – 15 .................................................................. 37

Description of assembler operators ............................................... 38

Assembler directives ....................................................................................... 51

Summary of assembler directives ................................................... 51

ARX-2

IAR AssemblerReference Guide for RX

Contents

Module control directives ................................................................... 55

Syntax ................................................................................................. 55

Parameters .......................................................................................... 55

Descriptions ....................................................................................... 55

Symbol control directives ................................................................... 57

Syntax ................................................................................................. 57

Parameters .......................................................................................... 57

Descriptions ....................................................................................... 58

Examples ............................................................................................ 58

Mode control directives ....................................................................... 59

Syntax ................................................................................................. 59

Description ......................................................................................... 59

Examples ............................................................................................ 60

Section control directives ................................................................... 61

Syntax ................................................................................................. 61

Parameters .......................................................................................... 61

Descriptions ....................................................................................... 62

Examples ............................................................................................ 63

Value assignment directives .............................................................. 64

Syntax ................................................................................................. 64

Parameters .......................................................................................... 64

Descriptions ....................................................................................... 65

Examples ............................................................................................ 65

Conditional assembly directives ....................................................... 66

Syntax ................................................................................................. 67

Parameters ......................................................................................... 67

Descriptions ....................................................................................... 67

Examples ............................................................................................ 68

Macro processing directives ............................................................... 69

Syntax ................................................................................................. 69

Parameters .......................................................................................... 69

Descriptions ....................................................................................... 70

Examples ............................................................................................ 73

ARX-2

v

vi

Listing control directives ..................................................................... 76

Syntax ................................................................................................. 77

Descriptions ....................................................................................... 77

Examples ............................................................................................ 78

C-style preprocessor directives ........................................................ 81

Syntax ................................................................................................. 81

Parameters .......................................................................................... 82

Descriptions ....................................................................................... 82

Examples ............................................................................................ 85

Data definition or allocation directives ......................................... 86

Syntax ................................................................................................. 87

Parameters .......................................................................................... 87

Descriptions ....................................................................................... 87

Examples ............................................................................................ 88

Assembler control directives ............................................................ 89

Syntax ................................................................................................. 89

Parameters .......................................................................................... 89

Descriptions ....................................................................................... 89

Examples ............................................................................................ 90

Call frame information directives ................................................... 91

Syntax ................................................................................................. 92

Parameters .......................................................................................... 93

Descriptions ....................................................................................... 94

Simple rules ........................................................................................ 98

CFI expressions ................................................................................ 100

Example ........................................................................................... 102

Pragma directives ............................................................................................ 105

Summary of pragma directives ...................................................... 105

Descriptions of pragma directives ................................................ 105

Diagnostics ......................................................................................................... 107

Message format ..................................................................................... 107

Severity levels ........................................................................................ 107

Setting the severity level .................................................................. 108

ARX-2


Contents

Internal error .................................................................................... 108

Index ..................................................................................................................... 109

ARX-2

vii

viii

ARX-2


Tables1: Typographic conventions used in this guide ........................................................ xiii

2: Naming conventions used in this guide ............................................................... xiii

3: Assembler environment variables ........................................................................... 4

4: Assembler error return codes .................................................................................. 4

5: Integer constant formats .......................................................................................... 7

6: ASCII character constant formats ........................................................................... 7

7: Floating-point constants .......................................................................................... 8

8: Predefined register symbols .................................................................................... 9

9: Predefined symbols ............................................................................................... 10

10: Symbol and cross-reference table ....................................................................... 14

11: Assembler options summary ............................................................................... 16

12: Assembler directives summary ........................................................................... 51

13: Module control directives ................................................................................... 55

14: Symbol control directives ................................................................................... 57

15: Mode control directives ....................................................................................... 59

16: Section control directives .................................................................................... 61

17: Value assignment directives ................................................................................ 64

18: Conditional assembly directives ......................................................................... 66

19: Macro processing directives ................................................................................ 69

20: Listing control directives ..................................................................................... 76

21: C-style preprocessor directives ........................................................................... 81

22: Data definition or allocation directives ............................................................... 86

23: Assembler control directives ............................................................................... 89

24: Call frame information directives ....................................................................... 91

25: Unary operators in CFI expressions .................................................................. 101

26: Binary operators in CFI expressions ................................................................. 101

27: Ternary operators in CFI expressions ............................................................... 102

28: Code sample with backtrace rows and columns ............................................... 103

29: Pragma directives summary .............................................................................. 105

ARX-2

ix

x

ARX-2


PrefaceWelcome to the IAR Assembler™ Reference Guide for RX. The purpose of this guide is to provide you with detailed reference information that can help you to use the IAR Assembler for RX to develop your application according to your requirements.

Who should read this guideYou should read this guide if you plan to develop an application, or part of an application, using assembler language for the RX microcontroller and need to get detailed reference information on how to use the IAR Assembler. In addition, you should have working knowledge of the following:

● The architecture and instruction set of the RX microcontroller. Refer to the documentation from Renesas for information about the RX microcontroller

● General assembler language programming

● Application development for embedded systems

● The operating system of your host computer.

How to use this guideWhen you first begin using the IAR Assembler, you should read the chapter Introduction to the IAR Assembler™ for RX in this reference guide.

If you are an intermediate or advanced user, you can focus more on the reference chapters that follow the introduction.

If you are new to using the IAR Systems toolkit, we recommend that you first read the initial chapters of the IAR Embedded Workbench® IDE User Guide. They give product overviews, and tutorials that can help you get started.

ARX-2

xi

xii

What this guide contains

What this guide containsBelow is a brief outline and summary of the chapters in this guide.

● Introduction to the IAR Assembler™ for RX provides programming information. It also describes the source code format, and the format of assembler listings.

● Assembler options first explains how to set the assembler options from the command line and how to use environment variables. It then gives an alphabetical summary of the assembler options, and contains detailed reference information about each option.

● Assembler operators gives a summary of the assembler operators, arranged in order of precedence, and provides detailed reference information about each operator.

● Assembler directives gives an alphabetical summary of the assembler directives, and provides detailed reference information about each of the directives, classified into groups according to their function.

● Pragma directives describes the pragma directives available in the assembler.

● Diagnostics contains information about the formats and severity levels of diagnostic messages.

Other documentationThe complete set of IAR Systems development tools for the RX microcontroller is described in a series of guides and online help files. For information about:

● Using the IAR Embedded Workbench® IDE with the IAR C-SPY® Debugger, refer to the IAR Embedded Workbench® IDE User Guide

● Programming for the IAR C/C++ Compiler and using the IAR ILINK Linker, refer to the IAR C/C++ Development Guide for RX

● Using the IAR DLIB Library, refer to the online help system

All of these guides are delivered in hypertext PDF or HTML format on the installation media.

Document conventions When, in this text, we refer to the programming language C, the text also applies to C++, unless otherwise stated.

When referring to a directory in your product installation, for example rx\doc, the full path to the location is assumed, for example c:\Program Files\IAR Systems\Embedded Workbench 6.n\rx\doc.

ARX-2


Preface

TYPOGRAPHIC CONVENTIONS

This guide uses the following typographic conventions:

NAMING CONVENTIONS

The following naming conventions are used for the products and tools from IAR Systems® referred to in this guide:

Style Used for

computer • Source code examples and file paths.• Text on the command line.• Binary, hexadecimal, and octal numbers.

parameter A placeholder for an actual value used as a parameter, for example filename.h where filename represents the name of the file.

[option] An optional part of a command.

[a|b|c] An optional part of a command with alternatives.

{a|b|c} A mandatory part of a command with alternatives.

bold Names of menus, menu commands, buttons, and dialog boxes that appear on the screen.

italic • A cross-reference within this guide or to another guide.• Emphasis.

… An ellipsis indicates that the previous item can be repeated an arbitrary number of times.

Identifies instructions specific to the IAR Embedded Workbench® IDE interface.

Identifies instructions specific to the command line interface.

Identifies helpful tips and programming hints.

Identifies warnings.

Table 1: Typographic conventions used in this guide

Brand name Generic term

IAR Embedded Workbench® for RX IAR Embedded Workbench®

IAR Embedded Workbench® IDE for RX the IDE

IAR C-SPY® Debugger for RX C-SPY, the debugger

IAR C-SPY® Simulator the simulator

IAR C/C++ Compiler™ for RX the compiler

Table 2: Naming conventions used in this guide

ARX-2

xiii

xiv

Document conventions

IAR Assembler™ for RX the assembler

IAR ILINK Linker™ ILINK, the linker

IAR DLIB Library™ the DLIB library

Brand name Generic term

Table 2: Naming conventions used in this guide (Continued)

ARX-2


Introduction to the IAR Assembler™ for RXThis chapter contains these sections:

● Introduction to assembler programming

● Modular programming

● External interface details

● Source format

● Assembler instructions

● Expressions, operands, and operators

● List file format

● Programming hints.

Introduction to assembler programmingEven if you do not intend to write a complete application in assembler language, there might be situations where you find it necessary to write parts of the code in assembler, for example, when using mechanisms in the RX microcontroller that require precise timing and special instruction sequences.

To write efficient assembler applications, you should be familiar with the architecture and instruction set of the RX microcontroller. Refer to Renesas’s hardware documentation for syntax descriptions of the instruction mnemonics.

GETTING STARTED

To ease the start of the development of your assembler application, you can:

● Work through the tutorials—especially the one about mixing C and assembler modules—that you find in the IAR Embedded Workbench® IDE User Guide

● Read about the assembler language interface—also useful when mixing C and assembler modules—in the IAR C/C++ Development Guide for RX

ARX-2

1

2

Modular programming

● In the IAR Embedded Workbench IDE, you can base a new project on a template for an assembler project.

Modular programmingIt is widely accepted that modular programming is a prominent feature of good software design. If you structure your code in small modules—in contrast to one single monolith—you can organize your application code in a logical structure, which makes the code easier to understand, and which aids:

● efficient program development

● reuse of modules

● maintenance.

The IAR development tools provide different facilities for achieving a modular structure in your software.

Typically, you write your assembler code in assembler source files; each file becomes a named module. If you divide your source code into many small source files, you will get many small modules. You can divide each module further into different subroutines.

A section is a logical entity containing a piece of data or code that should be mapped to a physical location in memory. Use the section control directives to place your code and data in sections. A section is relocatable. An address for a relocatable section is resolved at link time. Sections let you control how your code and data is placed in memory. A section is the smallest linkable unit, which allows the linker to include only those units that are referred to.

If you are working on a large project you will soon accumulate a collection of useful routines that are used by several of your applications. To avoid ending up with a huge amount of small object files, collect modules that contain such routines in a library object file. Note that a module in a library is always conditionally linked. In the IAR Embedded Workbench IDE, you can set up a library project, to collect many object files in one library. For an example, see the tutorials in the IAR Embedded Workbench® IDE User Guide.

To summarize, your software design benefits from modular programming, and to achieve a modular structure you can:

● Create many small modules, one per source file

● In each module, divide your assembler source code into small subroutines (corresponding to functions on the C level)

● Divide your assembler source code into sections, to gain more precise control of how your code and data finally is placed in memory

ARX-2


Introduction to the IAR Assembler™ for RX

● Collect your routines in libraries, which means that you can reduce the number of object files and make the modules conditionally linked.

External interface detailsThis section provides information about how the assembler interacts with its environment.

You can use the assembler either from the IAR Embedded Workbench IDE or from the command line. Refer to the IAR Embedded Workbench® IDE User Guide for information about using the assembler from the IAR Embedded Workbench IDE.

ASSEMBLER INVOCATION SYNTAX

The invocation syntax for the assembler is:

iasmrx [options][sourcefile][options]

For example, when assembling the source file prog.s, use this command to generate an object file with debug information:

iasmrx prog --debug

By default, the IAR Assembler for RX recognizes the filename extensions s, asm, and msa for source files. The default filename extension for assembler output is o.

Generally, the order of options on the command line, both relative to each other and to the source filename, is not significant. However, there is one exception: when you use the -I option, the directories are searched in the same order that they are specified on the command line.

If you run the assembler from the command line without any arguments, the assembler version number and all available options including brief descriptions are directed to stdout and displayed on the screen.

PASSING OPTIONS

You can pass options to the assembler in three different ways:

● Directly from the command line

Specify the options on the command line after the iasmrx command; see Assembler invocation syntax, page 3.

● Via environment variables

The assembler automatically appends the value of the environment variables to every command line; see Environment variables, page 4.

● Via a text file by using the -f option; see -f, page 25.

ARX-2

3

4

External interface details

For general guidelines for the option syntax, an options summary, and a detailed description of each option, see the Assembler options chapter.

ENVIRONMENT VARIABLES

Assembler options can also be specified in the ASMRX environment variable. The assembler automatically appends the value of this variable to every command line, so it provides a convenient method of specifying options that are required for every assembly.

You can use these environment variables with the IAR Assembler:

For example, setting this environment variable always generates a list file with the name temp.lst:

set IASMRX=-l temp.lst

For information about the environment variables used by the compiler and linker, see the IAR C/C++ Development Guide for RX.

ERROR RETURN CODES

When using the IAR Assembler from within a batch file, you might have to determine whether the assembly was successful to decide what step to take next. For this reason, the assembler returns these error return codes:

Environment variable Description

IASMRX Specifies command line options; for example:set IASMRX=-la . --warnings_are_errors

IASMRX_INC Specifies directories to search for include files; for example:set IASMRX_INC=c:\myinc\

Table 3: Assembler environment variables

Return code Description

0 Assembly successful, warnings might appear.

1 Warnings occurred, provided that the option --warnings_affect_exit_code was used.

2 Non-fatal errors or fatal assembly errors occurred (making the assembler abort).

3 Crashing errors occurred.

Table 4: Assembler error return codes

ARX-2



Source formatThe format of an assembler source line is as follows:

[label [:]] [operation] [operands] [; comment]

where the components are as follows:

The components are separated by spaces or tabs.

A source line cannot exceed 2047 characters.

Tab characters, ASCII 09H, are expanded according to the most common practice; i.e. to columns 8, 16, 24 etc. This affects the source code output in list files and debug information. Because tabs might be set up differently in different editors, do not use tabs in your source files.

RX architecture considerationsASSEMBLER INSTRUCTIONS

The IAR Assembler for RX supports the syntax for assembler instructions as described in the Renesas hardware documentation. It complies with the requirement of the RX architecture on word alignment.

label A definition of a label, which is a symbol that represents an address. If the label starts in the first column—that is, at the far left on the line—the :(colon) is optional.

operation An assembler instruction or directive. This must not start in the first column—there must be some whitespace to the left of it.

operands An assembler instruction or directive can have zero, one, or more operands. The operands are separated by commas. An operand can be:• a constant representing a numeric value or an address• a symbolic name representing a numeric value or an address (where the latter also is referred to as a label)• a floating-point constant• a register• a predefined symbol• the program location counter (PLC)• an expression.

comment Comment, preceded by a ; (semicolon)C or C++ comments are also allowed.

ARX-2

5

6

Expressions, operands, and operators

CODE AND DATA IN BIG-ENDIAN APPLICATIONS

When you assemble big-endian applications, the linker must be able to distinguish code from data. This is done using the assembly directives CODE and DATA. Any object read as data must be preceded by a DATA directive, and any lines that are to be executed must be preceded by a CODE directive.

There is no default mode for the assembler, and there will be no assembly error messages if these directives are omitted—but you will not be able to link successfully.

For more information, see Mode control directives, page 59.

Expressions, operands, and operatorsExpressions consist of expression operands and operators.

The assembler accepts a wide range of expressions, including both arithmetic and logical operations. All operators use 64-bit two’s complement integers. Range checking is performed if a value is used for generating code.

Expressions are evaluated from left to right, unless this order is overridden by the priority of operators; see also Assembler operators, page 35.

These operands are valid in an expression:

● Constants for data or addresses, excluding floating-point constants.

● Symbols—symbolic names—which can represent either data or addresses, where the latter also is referred to as labels.

● The program location counter (PLC), $ (dollar).

The operands are described in greater detail on the following pages.

Note: You cannot have two symbols in one expression, or any other complex expression, unless the expression can be resolved at assembly time. If they are not resolved, the assembler generates an error.

INTEGER CONSTANTS

Because all IAR Systems assemblers use 64-bit two’s complement internal arithmetic, integers have a (signed) range from -263 to 263-1.

Constants are written as a sequence of digits with an optional - (minus) sign in front to indicate a negative number.

Commas and decimal points are not permitted.

ARX-2



The following types of number representation are supported:

Note: Both the prefix and the suffix can be written with either uppercase or lowercase letters.

ASCII CHARACTER CONSTANTS

ASCII constants can consist of any number of characters enclosed in single or double quotes. Only printable characters and spaces can be used in ASCII strings. If the quote character itself will be accessed, two consecutive quotes must be used:

FLOATING-POINT CONSTANTS

The IAR Assembler accepts floating-point values as constants and converts them into IEEE single-precision (signed 32-bit) floating-point format and double-precision (signed 64-bit), or fractional format.

Floating-point numbers can be written in the format:

[+|-][digits].[digits][{E|e}[+|-]digits]

Integer type Example

Binary 1010b

Octal 1234q

Decimal 1234, -1

Hexadecimal 0FFFFh, 0xFFFF

Table 5: Integer constant formats

Format Value

'ABCD' ABCD (four characters).

"ABCD" ABCD'\0' (five characters the last ASCII null).

'A''B' A'B

'A''' A'

'''' (4 quotes) '

'' (2 quotes) Empty string (no value).

"" (2 double quotes) Empty string (an ASCII null character).

\' ', for quote within a string, as in 'I\'d love to'

\\ \, for \ within a string

\" ", for double quote within a string

Table 6: ASCII character constant formats

ARX-2

7

8


This table shows some valid examples:

Spaces and tabs are not allowed in floating-point constants.

Note: Floating-point constants do not give meaningful results when used in expressions.

When a fractional format is used—for example, DQ15—the range that can be represented is -1.0 <= x < 1.0. Any value outside that range is silently saturated into the maximum or minimum value that can be represented.

If the word length of the fractional data is n, the fractional number will be represented as the 2-complement number: x * 2^(n-1).

TRUE AND FALSE

In expressions a zero value is considered FALSE, and a non-zero value is considered TRUE.

Conditional expressions return the value 0 for FALSE and 1 for TRUE.

SYMBOLS

User-defined symbols can be up to 255 characters long, and all characters are significant. Depending on what kind of operation a symbol is followed by, the symbol is either a data symbol or an address symbol where the latter is referred to as a label. A symbol before an instruction is a label and a symbol before, for example the EQU directive, is a data symbol. A symbol can be:

● absolute—its value is known by the assembler

● relocatable—its value is resolved at link time.

Symbols must begin with a letter, a–z or A–Z, ? (question mark), or _ (underscore). Symbols can include the digits 0–9 and $ (dollar).

Case is insignificant for built-in symbols like instructions, registers, operators, and directives. For user-defined symbols, case is by default significant but can be turned on and off using the Case sensitive user symbols (--case_insensitive) assembler option. See --case_insensitive, page 18 for additional information.

Use the symbol control directives to control how symbols are shared between modules. For example, use the PUBLIC directive to make one or more symbols available to other modules. The EXTERN directive is used for importing an untyped external symbol.

Format Value

10.23 1.023 x 101

1.23456E-24 1.23456 x 10-24

1.0E3 1.0 x 103

Table 7: Floating-point constants

ARX-2



Note that symbols and labels are byte addresses. For additional information, see Generating a lookup table, page 88.

LABELS

Symbols used for memory locations are referred to as labels.

Program location counter (PLC)

The assembler keeps track of the start address of the current instruction. This is called the program location counter.

If you must refer to the program location counter in your assembler source code, use the $ (dollar) sign. For example:

bra $ ; Loop forever

REGISTER SYMBOLS

This table shows the existing predefined register symbols:

PREDEFINED SYMBOLS

The IAR Assembler defines a set of symbols for use in assembler source files. The symbols provide information about the current assembly, allowing you to test them in preprocessor directives or include them in the assembled code. The strings returned by the assembler are enclosed in double quotes.

Name Size Description

R1–R15 32 bits General purpose registers

SP/R0 32 bits Register R0, the currently active SP

PSW 32 bits Status register

PC 32 bits Program counter

USP 32 bits User mode stack pointer

ISP 32 bits Supervisor mode stack pointer

FPSW 32 bits Floating-point status register

BPSW 32 bits Backup status register (fast interrupt)

BPC 32 bits Backup program counter (fast interrupt)

FINTV 32 bits The fast interrupt vector register

INTB 32 bits The INTVEC maskable interrupt vector base register

Table 8: Predefined register symbols

ARX-2

9

10


These predefined symbols are available:

Symbol Value

__BIG_ENDIAN__ An integer that identifies the setting of the option --endian. If --endian=b has been specified, the value of this symbol is defined to 1 (TRUE). If --endian=l has been specified, the value of this symbol is defined to 0 (FALSE).

__BUILD_NUMBER__ A unique integer that identifies the build number of the assembler currently in use. The build number does not necessarily increase with an assembler that is released later.

__CORE__ An integer that identifies the chip core in use. It is defined to either __RX600__ or __RX610__.

__DATA_MODEL__ An integer that identifies the data model in use. The symbol reflects the --data_model option and can be defined to __NEAR__, __FAR__, or __HUGE__.

__DATE__ The current date in dd/Mmm/yyyy format (string).

__DOUBLE__ Either 32 or 64, depending on the setting of the option --double.

__FILE__ The name of the current source file (string).

__IAR_SYSTEMS_ASM__ IAR assembler identifier (number). The current value is 8. Note that the number could be higher in a future version of the product. This symbol can be tested with #ifdef to detect whether the code was assembled by an assembler from IAR Systems.

__IASMRX__ An integer that is set to 1 when the code is assembled with the IAR Assembler for RX.

__INTSIZE__ Either 16 or 32, depending on the setting of the option --int.

__LINE__ The current source line number (number).

__LITTLE_ENDIAN__ An integer that identifies the setting of the option --endian. If --endian=l has been specified, the value of this symbol is defined to 1 (TRUE). If --endian=b has been specified, the value of this symbol is defined to 0 (FALSE).

__SUBVERSION__ An integer that identifies the subversion number of the assembler version number, for example 3 in 1.2.3.4.

__TIME__ The current time in hh:mm:ss format (string).

Table 9: Predefined symbols

ARX-2



Including symbol values in code

Several data definition directives make it possible to include a symbol value in the code. These directives define values or reserve memory. To include a symbol value in the code, use the symbol in the appropriate data definition directive.

For example, to include the time of assembly as a string for the program to display:

name timeOfAssembly extern printStr public printTime section CODE:CODE data8 ; select data mode ; (required for big-endian)time: dc8 __TIME__ ; String representing the ; time of assembly. code ; select code mode ; (required for big-endian)printTime: mov.l #time,R1 ; Load address of time ; string in R1. bsr printStr ; Call string output routine. end

Testing symbols for conditional assembly

To test a symbol at assembly time, use one of the conditional assembly directives. These directives let you control the assembly process at assembly time.

For example, if you want to assemble separate code sections depending on whether you are using an old assembler version or a new assembler version, do as follows:

#if (__VER__ > 300) ; New assembler version;…;…#else ; Old assembler version;…;…#endif

For more information, see Conditional assembly directives, page 66.

__VER__ The version number in integer format; for example, version 4.17 is returned as 417 (number).

Symbol Value

Table 9: Predefined symbols (Continued)

ARX-2

11

12


ABSOLUTE AND RELOCATABLE EXPRESSIONS

Depending on what operands an expression consists of, the expression is either absolute or relocatable. Absolute expressions are those expressions that only contain absolute symbols or relocatable symbols that cancel each other out.

Expressions that include symbols in relocatable sections cannot be resolved at assembly time, because they depend on the location of sections. These are referred to as relocatable expressions.

Such expressions are evaluated and resolved at link time, by the IAR ILINK Linker. They can only be built up out of a maximum of one symbol reference and an offset after the assembler has reduced it.

For example, a program could define the sections DATA and CODE as follows:

name simpleExpressions section MYCONST:CONST(2)first dc8 5 ; A relocatable label.second equ 10 + 5 ; An absolute expression.

dc8 first ; Examples of some legal dc8 first + 1 ; relocatable expressions. dc8 first + second end

Note: At assembly time, there is no range check. The range check occurs at link time and, if the values are too large, there is a linker error.

EXPRESSION RESTRICTIONS

Expressions can be categorized according to restrictions that apply to some of the assembler directives. One such example is the expression used in conditional statements like IF, where the expression must be evaluated at assembly time and therefore cannot contain any external symbols.

The following expression restrictions are referred to in the description of each directive they apply to.

No forward

All symbols referred to in the expression must be known, no forward references are allowed.

No external

No external references in the expression are allowed.

ARX-2



Absolute

The expression must evaluate to an absolute value; a relocatable value (section offset) is not allowed.

Fixed

The expression must be fixed, which means that it must not depend on variable-sized instructions. A variable-sized instruction is an instruction that might vary in size depending on the numeric value of its operand.

List file formatThe format of an assembler list file is as follows:

HEADER

The header section contains product version information, the date and time when the file was created, and which options were used.

BODY

The body of the listing contains the following fields of information:

● The line number in the source file. Lines generated by macros, if listed, have a . (period) in the source line number field.

● The address field shows the location in memory, which can be absolute or relative depending on the type of section. The notation is hexadecimal.

● The data field shows the data generated by the source line. The notation is hexadecimal. Unresolved values are represented by ..... (periods), where two periods signify one byte. These unresolved values are resolved during the linking process.

● The assembler source line.

SUMMARY

The end of the file contains a summary of errors and warnings that were generated.

SYMBOL AND CROSS-REFERENCE TABLE

When you specify the Include cross-reference option, or if the LSTXRF+ directive was included in the source file, a symbol and cross-reference table is produced.

ARX-2

13

14

Programming hints

This information is provided for each symbol in the table:

Programming hintsThis section gives hints on how to write efficient code for the IAR Assembler. For information about projects including both assembler and C or C++ source files, see the IAR C/C++ Development Guide for RX.

USING C-STYLE PREPROCESSOR DIRECTIVES

The C-style preprocessor directives are processed before other assembler directives. Therefore, do not use preprocessor directives in macros and do not mix them with assembler-style comments. For more information about comments, see Assembler control directives, page 89.

Information Description

Symbol The symbol’s user-defined name.

Mode ABS (Absolute), or REL (Relocatable).

Sections The name of the section that this symbol is defined relative to.

Value/Offset The value (address) of the symbol within the current module, relative to the beginning of the current section.

Table 10: Symbol and cross-reference table

ARX-2


Assembler optionsThis chapter first explains how to set the options from the command line, and gives an alphabetical summary of the assembler options. It then provides detailed reference information for each assembler option.

The IAR Embedded Workbench® IDE User Guide describes how to set assembler options in the IAR Embedded Workbench® IDE, and gives reference information about the available options.

Setting command line assembler optionsTo set assembler options from the command line, include them on the command line after the iasmrx command, either before or after the source filename. For example, when assembling the source file prog.s, use this command to generate an object file with debug information:

iasmrx prog.s --debug

Some options accept a filename, included after the option letter with a separating space. For example, to generate a listing to the file prog.lst:

iasmrx prog.s -l prog.lst

Some other options accept a string that is not a filename. The string is included after the option letter, but without a space. For example, to define a symbol:

iasmrx prog.s -DDEBUG=1

Generally, the order of options on the command line, both relative to each other and to the source filename, is not significant. However, there is one exception: when you use the -I option, the directories are searched in the same order as they are specified on the command line.

Notice that a command line option has a short name and/or a long name:

● A short option name consists of one character, with or without parameters. You specify it with a single dash, for example -r.

● A long name consists of one or several words joined by underscores, with or without parameters. You specify it with double dashes, for example --debug.

ARX-2

15

16

Summary of assembler options

SPECIFYING PARAMETERS

When a parameter is needed for an option with a short name, you can specify it either immediately following the option or as the next command line argument.

For instance, you can specify an include file path of \usr\include either as:

-I\usr\include

or as

-I \usr\include

Note: You can use / instead of \ as directory delimiter. A trailing slash or backslash can be added to the last directory name, but is not required.

Additionally, some options can take a parameter that is a directory name. The output file then receives a default name and extension.

When a parameter is needed for an option with a long name, you can specify it either immediately after the equal sign (=) or as the next command line argument, for example:

--diag_suppress=Pe0001

or

--diag_suppress Pe0001

Options that accept multiple values can be repeated, and can also have comma-separated values (without space), for example:

--diag_warning=Be0001,Be0002

The current directory is specified with a period (.), for example:

iasmrx prog -l .

A file specified by - (a single dash) is standard input or output, whichever is appropriate.

Note: When an option takes a parameter, the parameter cannot start with a dash (-) followed by another character. Instead you can prefix the parameter with two dashes (--). This example generates a list on standard output:

iasmrx prog -l ---

Summary of assembler optionsThis table summarizes the assembler options available from the command line:

Command line option Description

--case_insensitive Case-insensitive user symbols

Table 11: Assembler options summary

ARX-2


Assembler options

--core Defines the symbol __CORE__

-D Defines preprocessor symbols

--data_model Defines the symbol __DATA_MODEL__

--debug Generates debug information

--dependencies Lists file dependencies

--diag_error Treats these diagnostics as errors

--diag_remark Treats these diagnostics as remarks

--diag_suppress Suppresses these diagnostics

--diag_warning Treats these diagnostics as warnings

--diagnostics_tables Lists all diagnostic messages

--dir_first Allows directives in the first column

--double Defines the symbol __DOUBLE__

--enable_multibytes Enables support for multibyte characters

--endian Defines the symbols __BIG_ENDIAN__ and __LITTLE_ENDIAN__

--error_limit Specifies the allowed number of errors before the assembler stops

-f Extends the command line

--header_context Lists all referred source files

-I Adds a search path for a header file

-l Generates a list file

-M Macro quote characters

--mnem_first Allows mnemonics in the first column

--no_fragments Disables section fragment handling

--no_path_in_file_macros Removes the path from the return value of the symbols __FILE__ and __BASE_FILE__

--no_system_include Disables the automatic search for system include files

--no_warnings Disables all warnings

--no_wrap_diagnostics Disables wrapping of diagnostic messages

-o Sets the object filename. Alias for --output.

--only_stdout Uses standard output only

--output Sets the object filename


Table 11: Assembler options summary (Continued)

ARX-2

17

18

Description of assembler options

Description of assembler optionsThe following sections give detailed reference information about each assembler option.

Note that if you use the page Extra Options to specify specific command line options, there is no check for consistency problems like conflicting options, duplication of options, or use of irrelevant options.

--case_insensitive

Syntax --case_insensitive

Description Use this option to make user symbols case-insensitive. By default, case sensitivity is on.

You can also use the assembler directives CASEON and CASEOFF to control case sensitivity for user-defined symbols.

Note: The --case_insensitive option does not affect preprocessor symbols. Preprocessor symbols are always case-sensitive, regardless of whether they are defined in the IDE or on the command line.

Example By default, for example, LABEL and label refer to different symbols. When --case_insensitive is used, LABEL and label instead refer to the same symbol.

See also Assembler control directives, page 89 and Defining and undefining preprocessor symbols, page 82.

Project>Options>Assembler >Language>User symbols are case sensitive

--predef_macros Lists the predefined symbols

--preinclude Includes an include file before reading the source file

--preprocess Preprocessor output to file

-r Generates debug information. Alias for --debug.

--remarks Enables remarks

--silent Sets silent operation

--system_include_dir Specifies the path for system include files

--warnings_affect_exit_code Warnings affect exit code

--warnings_are_errors Treats all warnings as errors


Table 11: Assembler options summary (Continued)

ARX-2


Assembler options

--core

Syntax --core={RX600|RX610}

Parameters

Description Use this option to define the symbol __CORE__. See Predefined symbols, page 9.

To set related options, choose:

Project>Options>General Options>Device

-D

Syntax -Dsymbol[=value]

Parameters

Description Use this option to define a symbol to be used by the preprocessor.

Example You might want to arrange your source code to produce either the test version or the production version of your application, depending on whether the symbol TESTVER was defined. To do this, use include sections such as:

#ifdef TESTVER... ; additional code lines for test version only#endif

Then select the version required on the command line as follows:

Production version: iasmrx prog

Test version: iasmrx prog -DTESTVER

Alternatively, your source might use a variable that you must change often. You can then leave the variable undefined in the source, and use -D to specify the value on the command line; for example:

iasmrx prog -DFRAMERATE=3

Project>Options>Assembler>Preprocessor>Defined symbols

RX600 (default) Sets the predefined symbol __CORE__ to RX600.

RX610 Sets the predefined symbol __CORE__ to RX610.

symbol The name of the symbol you want to define.

value The value of the symbol. If no value is specified, 1 is used.

ARX-2

19

20


--data_model

Syntax --data_model={near|n|far|f|huge|h}

Parameters

Description Use this option to define the symbol __DATA_MODEL__.

See also Predefined symbols, page 9.

Project>Options>General Options>Target>Data model

--debug, -r

Syntax --debug-r

Description Use this option to make the assembler generate debug information, which means the generated output can be used in a symbolic debugger such as IAR C-SPY® Debugger.

To reduce the size and link time of the object file, the assembler does not generate debug information by default.

Project>Options>Assembler >Output>Generate debug information

--dependencies

Syntax --dependencies=[i][m] {filename|directory}

Parameters

near|n Sets the predefined symbol __DATA_MODEL__ to __NEAR__

far|f (default) Sets the predefined symbol __DATA_MODEL__ to __FAR__

huge|h Sets the predefined symbol __DATA_MODEL__ to __HUGE__

No parameter The same affect as for the parameter i.

i (default) The names of the dependent files, including the full path if available, is output. For example:c:\iar\product\include\stdio.hd:\myproject\include\foo.h

ARX-2


Assembler options

For information about specifying a filename or directory, see Specifying parameters, page 16.

Description Use this option to list each source file opened by the assembler in a file.

Example 1 To generate a listing of file dependencies to the file listing.i, use:

iasmrx prog --dependencies=i listing

Example 2 An example of using --dependencies with gmake:

1 Set up the rule for assembling files to be something like:

%.o : %.c$(ASM) $(ASMFLAGS) $< --dependencies=m $*.d

That is, in addition to producing an object file, the command also produces a dependent file in makefile style (in this example using the extension .d).

2 Include all the dependent files in the makefile, using for example:

-include $(sources:.c=.d)

Because of the -, it works the first time, when the .d files do not yet exist.

This option is not available in the IDE.

--diag_error

Syntax --diag_error=tag,tag,...

Parameters

m The output uses makefile style. For each source file, one line containing a makefile dependency rule is output. Each line consists of the name of the object file, a colon, a space, and the name of a source file. For example:foo.o: c:\iar\product\include\stdio.hfoo.o: d:\myproject\include\foo.h

filename The output is stored in the specified file.

directory The output is stored in a file (filename extension i) which is stored in the specified directory.

tag The number of a diagnostic message, for example the message number As001.

ARX-2

21

22


Description Use this option to classify diagnostic messages as errors.

An error indicates a violation of the assembler language rules, of such severity that object code is not generated, and the exit code will not be 0. The option can be used more than once on the command line.

Example This example classifies warning As001 as an error:

--diag_error=As001

Project>Options>Assembler >Diagnostics>Treat these as errors

--diag_remark

Syntax --diag_remark=tag,tag,...

Parameters

Description Use this option to classify diagnostic messages as remarks.

A remark is the least severe type of diagnostic message and indicates a source code construct that might cause strange behavior in the generated code.

Example This example classifies the warning As001 as a remark:

--diag_remark=As001

Project>Options>Assembler >Diagnostics>Treat these as remarks

--diag_suppress

Syntax --diag_suppress=tag,tag,...

Parameters

Description Use this option to suppress diagnostic messages.



ARX-2


Assembler options

Example This example suppresses the warnings As001 and As002:

--diag_suppress=As001,As002

Project>Options>Assembler >Diagnostics>Suppress these diagnostics

--diag_warning

Syntax --diag_warning=tag,tag,...

Parameters

Description Use this option to classify diagnostic messages as warnings.

A warning indicates an error or omission that is of concern, but which does not cause the assembler to stop before the assembly is completed.

Example This example classifies the remark As028 as a warning:

--diag_warning=As028

Project>Options>Assembler >Diagnostics>Treat these as warnings

--diagnostics_tables

Syntax --diagnostics_tables {filename|directory}

Parameters


Description Use this option to list all possible diagnostic messages in a named file. This can be very convenient, for example, if you used a #pragma directive to suppress or change the severity level of any diagnostic messages, but forgot to document why.

This option cannot be given together with other options.


filename The diagnostic messages are stored in the specified file.

directory The diagnostic messages are stored in a file (filename extension i) which is stored in the specified directory.

ARX-2

23

24


Example To output a list of all possible diagnostic messages to the file diag.txt, use:

--diagnostics_tables diag


--dir_first

Syntax --dir_first

Description Use this option to make directive names (without a trailing colon) that start in the first column to be recognized as directives.

The default behavior of the assembler is to treat all identifiers starting in the first column as labels.

Project>Options>Assembler >Language>Allow directives in first column

--double

Syntax --double={32|64}

Parameters

Description Use this option to define the symbol __DOUBLE__.


Project>Options>General Options>Target>Size of type 'double'

--enable_multibytes

Syntax --enable_multibytes

Description By default, multibyte characters cannot be used in assembler source code. Use this option to interpret multibyte characters in the source code according to the host computer’s default setting for multibyte support.

Multibyte characters are allowed in comments, in string literals, and in character constants. They are transferred untouched to the generated code.

Project>Options>Assembler>Language>Enable multibyte support

32 (default) Sets the predefined symbol __DOUBLE__ to 32

64 Sets the predefined symbol __DOUBLE__ to 64

ARX-2


Assembler options

--endian

Syntax --endian={b|big|l|little}

Parameters

Description Use this option to define the symbols __BIG_ENDIAN__ and __LITTLE_ENDIAN__.


Project>Options>General Options>Target>Byte order

--error_limit

Syntax --error_limit=n

Parameters

Description Use this option to specify the number of errors allowed before the assembler stops. By default, 100 errors are allowed.


-f

Syntax -f filename

Parameters

For information about specifying a filename, see Specifying parameters, page 16.

Description Use this option to extend the command line with text read from the specified file.

b|big Sets the predefined symbol __BIG_ENDIAN__ to 1 and

__LITTLE_ENDIAN__ to 0

l|little (default)

Sets the predefined symbol __BIG_ENDIAN__ to 0 and

__LITTLE_ENDIAN__ to 1

n The number of errors before the assembler stops the assembly. n must be a positive integer; 0 indicates no limit.

filename The commands that you want to extend the command line with are read from the specified file. Notice that there must be a space between the option itself and the filename.

ARX-2

25

26


The -f option is particularly useful if there are many options which are more conveniently placed in a file than on the command line itself.

Example To run the assembler with further options taken from the file extend.xcl, use:

iasmrx prog -f extend.xcl

To set this option, use:

Project>Options>Assembler>Extra Options

--header_context

Syntax --header_context

Description Occasionally, you must know which header file that was included from what source line, to find the cause of a problem. Use this option to list, for each diagnostic message, not only the source position of the problem, but also the entire include stack at that point.


-I

Syntax -Ipath

Parameters

Description Use this option to specify paths to be used by the preprocessor. This option can be used more than once on the command line.

By default, the assembler searches for #include files in the current working directory, in the system header directories, and in the paths specified in the IASMRX_INC environment variable. The -I option allows you to give the assembler the names of directories which it will also search if it fails to find the file in the current working directory.

Example For example, using the options:

-Ic:\global\ -Ic:\thisproj\headers\

and then writing:

#include "asmlib.hdr"

path The search path for #include files.

ARX-2


Assembler options

in the source code, make the assembler search first in the current directory, then in the directory c:\global\, and then in the directory C:\thisproj\headers\. Finally, the assembler searches the directories specified in the IASMRX_INC environment variable, provided that this variable is set, and in the system header directories.

Project>Options>Assembler >Preprocessor>Additional include directories

--int

Syntax --int={16|32}

Parameters

Description Use this option to define the symbol __INTSIZE__.


Project>Options>General Options>Target>Size of type 'int'

-l

Syntax -l[a][d][e][m][o][x][N][H] {filename|directory}

Parameters

16 Sets the predefined symbol __INTSIZE__ to 16

32 (default) Sets the predefined symbol __INTSIZE__ to 32

a Assembled lines only.

d The LSTOUT directive controls if lines are written to the list file or not. Using -ld turns the start value for this to off.

e No macro expansions.

m Macro definitions.

o Multiline code.

x Includes cross-references.

N Do not include diagnostics.

H Includes header file source lines.


directory The output is stored in a file (filename extension i) which is stored in the specified directory.

ARX-2

27

28



Description By default, the assembler does not generate a listing. Use this option to generate a listing to a file.

Example To generate a listing to the file list.lst, use:

iasmrx sourcefile -l list

To set related options, select:

Project>Options>Assembler >List

-M

Syntax -Mab

Parameters

Description Use this option to sets the characters to be used as left and right quotes of each macro argument to a and b respectively.

By default, the characters are < and >. The -M option allows you to change the quote characters to suit an alternative convention or simply to allow a macro argument to contain < or > themselves.

Example For example, using the option:

-M[]

in the source you would write, for example:

print [>]

to call a macro print with > as the argument.

Note: Depending on your host environment, it might be necessary to use quote marks with the macro quote characters, for example:

iasmrx filename -M’<>’

Project>Options>Assembler >Language>Macro quote characters

ab The characters to be used as left and right quotes of each macro argument, respectively.

ARX-2


Assembler options

--mnem_first

Syntax --mnem_first

Description Use this option to make mnemonics names (without a trailing colon) starting in the first column be recognized as mnemonics.

The default behavior of the assembler is to treat all identifiers starting in the first column as labels.

Project>Options>Assembler >Language>Allow mnemonics in first column

--no_fragments

Syntax --no_fragments

Description Use this option to disable section fragment handling. Normally, the toolset uses IAR proprietary information for transferring section fragment information to the linker. The linker uses this information to remove unused code and data, and thus further minimize the size of the executable image.

To set this option, use Project>Options>Assembler >Extra Options.

--no_path_in_file_macros

Syntax --no_path_in_file_macros

Description Use this option to exclude the path from the return value of the predefined preprocessor symbols __FILE__ and __BASE_FILE__.


--no_system_include

Syntax --no_system_include

Description By default, the assembler automatically locates the system include files. Use this option to disable the automatic search for system include files. In this case, you might need to set up the search path by using the -I assembler option.

Project>Options>Assembler>Preprocessor>Ignore standard include directories

ARX-2

29

30


--no_warnings

Syntax --no_warnings

Description By default, the assembler issues standard warning messages. Use this option to disable all warning messages.


--no_wrap_diagnostics

Syntax --no_wrap_diagnostics

Description By default, long lines in assembler diagnostic messages are broken into several lines to make the message easier to read. Use this option to disable line wrapping of diagnostic messages.


--only_stdout

Syntax --only_stdout

Description Use this option to make the assembler direct messages to stdout instead of to stderr.


--output, -o

Syntax --output {filename|directory} -o {filename|directory}

arameters


filename The object code is stored in the specified file.

directory The object code is stored in a file (filename extension o) which is stored in the specified directory.

ARX-2


Assembler options

Description By default, the object code produced by the assembler is located in a file with the same name as the source file, but with the extension o. Use this option to specify a different output filename for the object code output.

Project>Options>General Options>Output>Output directories>Object files

--predef_macros

Syntax --predef_macros {filename|directory}

Description


Description Use this option to list the predefined symbols. When using this option, make sure to also use the same options as for the rest of your project.

Note that this option requires that you specify a source file on the command line.


--preinclude

Syntax --preinclude includefile

Parameters

Description Use this option to make the assembler include the specified include file before it starts to read the source file. This is useful if you want to change something in the source code for the entire application, for instance if you want to define a new symbol.

To set this option, use:

Project>Options>Assembler>Extra Options

filename The list of predefined macros is stored in the specified file.

directory The list of predefined macros is stored in a file (filename extension predef) which is stored in the specified directory.

includefile The header file to be included.

ARX-2

31

32


--preprocess

Syntax --preprocess=[c][n][l] {filename|directory}

Parameters


Description Use this option to direct preprocessor output to a named file.

Example To store the assembler output with preserved comments to the file output.i, use:

iasmrx sourcefile --preprocess=c output

Project>Options>Assembler >Preprocessor>Preprocessor output to file

--remarks

Syntax --remarks

Description Use this option to make the assembler generate remarks, which is the least severe type of diagnostic message and which indicates a source code construct that might cause strange behavior in the generated code. By default, remarks are not generated.

See also Severity levels, page 107.

Project>Options>Assembler >Diagnostics>Enable remarks

No parameter A preprocessed file.

c Preserves C and C++ style comments that otherwise are removed by the preprocessor. Assembler style comments are always preserved.

n Preprocess only.

l Generate #line directives.


directory The output is stored in a file (filename extension i) which is stored in the specified directory. The filename is the same as the name of the assembled source file.

ARX-2


Assembler options

--silent

Syntax --silent

Description By default, the assembler sends various minor messages via the standard output stream. Use this option to make the assembler operate without sending any messages to the standard output stream.

The assembler sends error and warning messages to the error output stream, so they are displayed regardless of this setting.


--system_include_dir

Syntax --system_include_dir path

Parameters

Description By default, the assembler automatically locates the system include files. Use this option to explicitly specify a different path to the system include files. This might be useful if you have not installed IAR Embedded Workbench in the default location.


--warnings_affect_exit_code

Syntax --warnings_affect_exit_code

Description By default, the exit code is not affected by warnings, only errors produce a non-zero exit code. Use this option to make warnings generate a non-zero exit code.


--warnings_are_errors

Syntax --warnings_are_errors

Description Use this option to make the assembler treat all warnings as errors. If the assembler encounters an error, no object code is generated.

path The path to the system include files.

ARX-2

33

34


If you want to keep some warnings, use this option in combination with the option --diag_warning. First make all warnings become treated as errors and then reset the ones that should still be treated as warnings, for example:

--diag_warning=As001

See also --diag_warning, page 23.

Project>Options>Assembler >Diagnostics>Treat all warnings as errors

ARX-2


Assembler operatorsThis chapter first describes the precedence of the assembler operators, and then summarizes the operators, classified according to their precedence. Finally, this chapter provides reference information about each operator, presented in alphabetical order.

Precedence of operatorsEach operator has a precedence number assigned to it that determines the order in which the operator and its operands are evaluated. The precedence numbers range from 1 (the highest precedence, that is, first evaluated) to 15 (the lowest precedence, that is, last evaluated).

These rules determine how expressions are evaluated:

● The highest precedence operators are evaluated first, then the second highest precedence operators, and so on until the lowest precedence operators are evaluated

● Operators of equal precedence are evaluated from left to right in the expression

● Parentheses ( and ) can be used for grouping operators and operands and for controlling the order in which the expressions are evaluated. For example, this expression evaluates to 1:

7/(1+(2*3))

Note: The precedence order in the IAR Assembler for RX closely follows the precedence order of the ANSI C++ standard for operators, where applicable.

Summary of assembler operatorsThe following tables give a summary of the operators, in order of precedence. Synonyms, where available, are shown in brackets after the operator name.

Note: An assembler operator can only operate on expressions that can be translated into one ELF relocation or that can be resolved absolutely.

PARENTHESIS OPERATOR – 1

() Parenthesis.

ARX-2

35

36

Summary of assembler operators

FUNCTION OPERATORS – 2

UNARY OPERATORS – 3

MULTIPLICATIVE ARITHMETIC OPERATORS – 4

ADDITIVE ARITHMETIC OPERATORS – 5

BYTE1 First byte.

BYTE2 Second byte.

BYTE3 Third byte.

BYTE4 Fourth byte.

DATE Current date/time.

HIGH High byte.

HWRD High word.

LOW Low byte.

LWRD Low word.

SFB Section begin.

SFE Section end.

SIZEOF Section size.

UPPER Third byte.

+ Unary plus.

BINNOT [~] Bitwise NOT.

NOT [!] Logical NOT.

- Unary minus.

* Multiplication.

/ Division.

MOD [%] Modulo.

+ Addition.

– Subtraction.

ARX-2


Assembler operators

SHIFT OPERATORS – 6

COMPARISON OPERATORS – 7

EQUIVALENCE OPERATORS – 8

LOGICAL OPERATORS – 9-14

CONDITIONAL OPERATOR – 15

SHL [<<] Logical shift left.

SHR [>>] Logical shift right.

GE [>=] Greater than or equal.

GT [>] Greater than.

LE [<=] Less than or equal.

LT [<] Less than.

UGT Unsigned greater than.

ULT Unsigned less than.

EQ [=] [==] Equal.

NE [<>] [!=] Not equal.

BINAND [&] Bitwise AND (9).

BINXOR [^] Bitwise exclusive OR (10).

BINOR [|] Bitwise OR (11).

AND [&&] Logical AND (12).

XOR Logical exclusive OR (13).

OR [||] Logical OR (14).

?: Conditional operator.

ARX-2

37

38

Description of assembler operators

Description of assembler operatorsThe following sections give full descriptions of each assembler operator. The number within parentheses specifies the priority of the operator.

() Parenthesis (1).

( and ) group expressions to be evaluated separately, overriding the default precedence order.

Example

1+2*3 → 7(1+2)*3 → 9

* Multiplication (4).

* produces the product of its two operands. The operands are taken as signed 32-bit integers and the result is also a signed 32-bit integer.

Example

2*2 → 4-2*2 → -4

+ Unary plus (3).

Unary plus operator.

Example

+3 → 33*+2 → 6

+ Addition (5).

The + addition operator produces the sum of the two operands which surround it. The operands are taken as signed 32-bit integers and the result is also a signed 32-bit integer.

Example

92+19 → 111-2+2 → 0-2+-2 → -4

ARX-2


Assembler operators

- Unary minus (3).

The unary minus operator performs arithmetic negation on its operand.

The operand is interpreted as a 32-bit signed integer and the result of the operator is the two’s complement negation of that integer.

Example

-3 → -33*-2 → -64--5 → 9

- Subtraction (5).

The subtraction operator produces the difference when the right operand is taken away from the left operand. The operands are taken as signed 32-bit integers and the result is also signed 32-bit integer.

Example

92-19 → 73-2-2 → -4-2--2 → 0

/ Division (4).

/ produces the integer quotient of the left operand divided by the right operand. The operands are taken as signed 32-bit integers and the result is also a signed 32-bit integer.

Example

9/2 → 4-12/3 → -49/2*6 → 24

?: Conditional operator (15).

The result of this operator is the first expr if condition evaluates to true and the second expr if condition evaluates to false.

Note: The question mark and a following label must be separated by space or a tab, otherwise the ? is considered the first character of the label.

ARX-2

39

40


Syntax

condition ? expr : expr

Example

5 ? 6 : 7 →60 ? 6 : 7 →7

AND [&&] Logical AND (12).

Use AND to perform logical AND between its two integer operands. If both operands are non-zero the result is 1 (true), otherwise it is 0 (false).

Example

1010B AND 0011B → 11010B AND 0101B → 11010B AND 0000B → 0

BINAND [&] Bitwise AND (9).

Use BINAND to perform bitwise AND between the integer operands. Each bit in the 32-bit result is the logical AND of the corresponding bits in the operands.

Example

1010B BINAND 0011B → 0010B1010B BINAND 0101B → 0000B1010B BINAND 0000B → 0000B

BINNOT [~] Bitwise NOT (3).

Use BINNOT to perform bitwise NOT on its operand. Each bit in the 32-bit result is the complement of the corresponding bit in the operand.

Example

BINNOT 1010B → 11111111111111111111111111110101B

BINOR [|] Bitwise OR (11).

Use BINOR to perform bitwise OR on its operands. Each bit in the 32-bit result is the inclusive OR of the corresponding bits in the operands.

ARX-2


Assembler operators

Example

1010B BINOR 0101B → 1111B1010B BINOR 0000B → 1010B

BINXOR [^] Bitwise exclusive OR (10).

Use BINXOR to perform bitwise XOR on its operands. Each bit in the 32-bit result is the exclusive OR of the corresponding bits in the operands.

Example

1010B BINXOR 0101B → 1111B1010B BINXOR 0011B → 1001B

BYTE1 First byte (2).

BYTE1 takes a single operand, which is interpreted as an unsigned 32-bit integer value. The result is the low byte (bits 7 to 0) of the operand.

Example

BYTE1 0x12345678 → 0x78

BYTE2 Second byte (2).

BYTE2 takes a single operand, which is interpreted as an unsigned 32-bit integer value. The result is the middle-low byte (bits 15 to 8) of the operand.

Example

BYTE2 0x12345678 → 0x56

BYTE3 Third byte (2).

BYTE3 takes a single operand, which is interpreted as an unsigned 32-bit integer value. The result is the middle-high byte (bits 23 to 16) of the operand.

Example

BYTE3 0x12345678 → 0x34

ARX-2

41

42


BYTE4 Fourth byte (2).

BYTE4 takes a single operand, which is interpreted as an unsigned 32-bit integer value. The result is the high byte (bits 31 to 24) of the operand.

Example

BYTE4 0x12345678 → 0x12

DATE Current date/time (2).

Use the DATE operator to specify when the current assembly began.

The DATE operator takes an absolute argument (expression) and returns:

Example

To assemble the date of assembly:

today: DC8 DATE 5, DATE 4, DATE 3

EQ [=] [==] Equal (8).

= evaluates to 1 (true) if its two operands are identical in value, or to 0 (false) if its two operands are not identical in value.

Example

1 = 2 → 02 == 2 → 1'ABC' = 'ABCD' → 0

DATE 1 Current second (0–59)

DATE 2 Current minute (0–59)

DATE 3 Current hour (0–23)

DATE 4 Current day (1–31)

DATE 5 Current month (1–12)

DATE 6 Current year MOD 100 (1998 →98, 2000 →00, 2002 →02)

ARX-2


Assembler operators

GE [>=] Greater than or equal (7).

>= evaluates to 1 (true) if the left operand is equal to or has a higher numeric value than the right operand, otherwise it is 0 (false).

Example

1 >= 2 → 02 >= 1 → 11 >= 1 → 1

GT [>] Greater than (7).

> evaluates to 1 (true) if the left operand has a higher numeric value than the right operand, otherwise it is 0 (false).

Example

-1 > 1 → 02 > 1 → 11 > 1 → 0

HIGH High byte (2).

HIGH takes a single operand to its right which is interpreted as an unsigned, 16-bit integer value. The result is the unsigned 8-bit integer value of the higher order byte of the operand.

Example

HIGH 0xABCD → 0xAB

HWRD High word (2).

HWRD takes a single operand, which is interpreted as an unsigned, 32-bit integer value. The result is the high word (bits 31 to 16) of the operand.

Example

HWRD 0x12345678 → 0x1234

LE [<=] Less than or equal (7).

<= evaluates to 1 (true) if the left operand has a lower or equal numeric value to the right operand, otherwise it is 0 (false).

ARX-2

43

44


Example

1 <= 2 → 12 <= 1 → 01 <= 1 → 1

LOW Low byte (2).

LOW takes a single operand, which is interpreted as an unsigned, 32-bit integer value. The result is the unsigned, 8-bit integer value of the lower order byte of the operand.

Example

LOW 0xABCD → 0xCD

LT [<] Less than (7).

< evaluates to 1 (true) if the left operand has a lower numeric value than the right operand, otherwise it is 0 (false).

Example

-1 < 2 → 12 < 1 → 02 < 2 → 0

LWRD Low word (2).

LWRD takes a single operand, which is interpreted as an unsigned, 32-bit integer value. The result is the low word (bits 15 to 0) of the operand.

Example

LWRD 0x12345678 → 0x5678

MOD [%] Modulo (4).

MOD produces the remainder from the integer division of the left operand by the right operand. The operands are taken as signed 32-bit integers and the result is also a signed 32-bit integer.

X MOD Y is equivalent to X-Y*(X/Y) using integer division.

ARX-2


Assembler operators

Example

2 MOD 2 → 012 MOD 7 → 53 MOD 2 → 1

NE [<>] [!=] Not equal (8).

<> evaluates to 0 (false) if its two operands are identical in value or to 1 (true) if its two operands are not identical in value.

Example

1 <> 2 → 12 <> 2 → 0'A' <> 'B' → 1

NOT [!] Logical NOT (3).

Use NOT to negate a logical argument.

Example

NOT 0101B → 0NOT 0000B → 1

OR [||] Logical OR (14).

Use OR to perform a logical OR between two integer operands.

Example

1010B OR 0000B → 10000B OR 0000B → 0

SFB Section begin (2).

SFB accepts a single operand to its right. The operand must be the name of a relocatable section. The operator evaluates to the absolute address of the first byte of that section. This evaluation occurs at link time.

Syntax

SFB(section [{+|-}offset])

ARX-2

45

46


Parameters

Example

name sectionBegin section MYCODE:CODE ; Forward declaration of MYCODE section SEGTAB:CONST(2) data32 ; Disassembled as 32-bit datastart dc32 sfb(MYCODE) end

Even if this code is linked with many other modules, start is still set to the address of the first byte of the section.

SFE Section end (2).

SFE accepts a single operand to its right. The operand must be the name of a relocatable section. The operator evaluates to the section start address plus the section size. This evaluation occurs at link time.

Syntax

SFE (section [{+ | -} offset])

Parameters

Example

name sectionEnd section MYCODE:CODE ; Forward declaration of MYCODE section SEGTAB:CONST data32 ; Disassembled as 32-bit dataendmycode dc32 sfe(MYCODE) end

section The name of a relocatable section, which must be defined before SFB is used.

offset An optional offset from the start address. The parentheses are optional if offset is omitted.

section The name of a relocatable section, which must be defined before SFE is used.

offset An optional offset from the start address. The parentheses are optional if offset is omitted.

ARX-2


Assembler operators

Even if this code is linked with many other modules, end is still set to the first byte after that section (mycode).

The size of the section MY_SECTION can be calculated as:

SFE(MY_SECTION)-SFB(MY_SECTION)

SHL [<<] Logical shift left (6).

Use SHL to shift the left operand, which is always treated as unsigned, to the left. The number of bits to shift is specified by the right operand, interpreted as an integer value between 0 and 32.

Example

00011100B SHL 3 → 11100000B00000111111111111B SHL 5 → 11111111111100000B14 SHL 1 → 28

SHR [>>] Logical shift right (6).

Use SHR to shift the left operand, which is always treated as unsigned, to the right. The number of bits to shift is specified by the right operand, interpreted as an integer value between 0 and 32.

Example

01110000B SHR 3 → 00001110B1111111111111111B SHR 20 → 014 SHR 1 → 7

SIZEOF Section size (2).

SIZEOF generates SFE-SFB for its argument, which should be the name of a relocatable section; that is, it calculates the size in bytes of a section. This is done when modules are linked together.

Syntax

SIZEOF (section)

Parameters

section The name of a relocatable section, which must be defined before SIZEOF is used.

ARX-2

47

48


Example

These two files set size to the size of the section MYCODE.

Table.s:

name table section MYCODE:CODE ; Forward declaration of MYCODE section SEGTAB:CONST data32 ; Disassembled as 32-bit datasize dc32 sizeof(MYCODE) end

Application.s:

name application section MYCODE:CODE code ; Disassembled as code nop ; Placeholder for application end

UGT Unsigned greater than (7).

UGT evaluates to 1 (true) if the left operand has a larger value than the right operand, otherwise it is 0 (false). The operation treats its operands as unsigned values.

Example

2 UGT 1 → 1-1 UGT 1 → 1

ULT Unsigned less than (7).

ULT evaluates to 1 (true) if the left operand has a smaller value than the right operand, otherwise it is 0 (false). The operation treats the operands as unsigned values.

Example

1 ULT 2 → 1-1 ULT 2 → 0

UPPER Third byte (2).

UPPER takes a single operand, which is interpreted as an unsigned 32-bit integer value. The result is the middle-high byte (bits 23 to 16) of the operand.

ARX-2


Assembler operators

Example

UPPER 0x12345678 → 0x34

XOR Logical exclusive OR (13).

XOR evaluates to 1 (true) if either the left operand or the right operand is non-zero, but to 0 (false) if both operands are zero or both are non-zero. Use XOR to perform logical XOR on its two operands.

Example

0101B XOR 1010B → 00101B XOR 0000B → 1

ARX-2

49

50


ARX-2


Assembler directivesThis chapter gives an alphabetical summary of the assembler directives and provides detailed reference information for each category of directives.

Summary of assembler directivesThe assembler directives are classified into these groups according to their function:

● Module control directives, page 55

● Symbol control directives, page 57

● Mode control directives, page 59

● Section control directives, page 61

● Value assignment directives, page 64

● Conditional assembly directives, page 66

● Macro processing directives, page 69

● Listing control directives, page 76

● C-style preprocessor directives, page 81

● Data definition or allocation directives, page 86

● Assembler control directives, page 89

● Call frame information directives, page 91.

This table gives a summary of all the assembler directives:

Directive Description Section

_args Is set to number of arguments passed to macro. Macro processing

#define Assigns a value to a label. C-style preprocessor

#elif Introduces a new condition in a #if…#endif block.

C-style preprocessor

#else Assembles instructions if a condition is false. C-style preprocessor

#endif Ends a #if, #ifdef, or #ifndef block. C-style preprocessor

#error Generates an error. C-style preprocessor

#if Assembles instructions if a condition is true. C-style preprocessor

#ifdef Assembles instructions if a symbol is defined. C-style preprocessor

#ifndef Assembles instructions if a symbol is undefined. C-style preprocessor

Table 12: Assembler directives summary

ARX-2

51

52

Summary of assembler directives

#include Includes a file. C-style preprocessor

#line Changes the line numbers. C-style preprocessor

#pragma Controls extension features. C-style preprocessor

#undef Undefines a label. C-style preprocessor

/*comment*/ C-style comment delimiter. Assembler control

// C++ style comment delimiter. Assembler control

= Assigns a permanent value local to a module. Value assignment

ALIGN Aligns the program location counter by inserting zero-filled bytes.

Section control

ALIGNRAM Aligns the program location counter. Section control

ASSIGN Assigns a temporary value. Value assignment

CASEOFF Disables case sensitivity. Assembler control

CASEON Enables case sensitivity. Assembler control

CFI Specifies call frame information. Call frame information

CODE Subsequent instructions are assembled, linked, and disassembled as code.

Mode control

DATA Subsequent instructions are assembled, linked, and disassembled as 8-bit data.

Mode control

DATA8 Subsequent instructions are assembled, linked, and disassembled as 8-bit data.

Mode control


Mode control


Mode control


Mode control

DC8 Generates 8-bit constants, including strings. Data definition or allocation

DC16 Generates 16-bit constants. Data definition or allocation



Table 12: Assembler directives summary (Continued)

ARX-2


Assembler directives



DEFINE Defines a file-wide value. Value assignment

DF32 Generates 32-bit floating-point constants. Data definition or allocation

DF64 Generates 64-bit floating-point constants. Data definition or allocation

DQ15 Generates 16-bit fractional constants. Data definition or allocation

DQ31 Generates 32-bit fractional constants. Data definition or allocation

DS8 Allocates space for 8-bit integers. Data definition or allocation





ELSE Assembles instructions if a condition is false. Conditional assembly

ELSEIF Specifies a new condition in an IF…ENDIF block. Conditional assembly

END Ends the assembly of the last module in a file. Module control

ENDIF Ends an IF block. Conditional assembly

ENDM Ends a macro definition. Macro processing

ENDR Ends a repeat structure. Macro processing

EQU Assigns a permanent value local to a module. Value assignment

EVEN Aligns the program counter to an even address. Section control

EXITM Exits prematurely from a macro. Macro processing

EXTERN Imports an external symbol. Symbol control

IF Assembles instructions if a condition is true. Conditional assembly



ARX-2

53

54

Summary of assembler directives

IMPORT Imports an external symbol. Symbol control

LIBRARY Begins a module; an alias for PROGRAM and NAME. Module control

LOCAL Creates symbols local to a macro. Macro processing

LSTCND Controls conditional assembler listing. Listing control

LSTCOD Controls multi-line code listing. Listing control

LSTEXP Controls the listing of macro generated lines. Listing control

LSTMAC Controls the listing of macro definitions. Listing control

LSTOUT Controls assembler-listing output. Listing control

LSTPAG Retained for backward compatibility reasons; recognized but ignored.

Listing control

LSTREP Controls the listing of lines generated by repeat directives.

Listing control

LSTXRF Generates a cross-reference table. Listing control

MACRO Defines a macro. Macro processing

MODULE Begins a module; an alias for PROGRAM and NAME. Module control

NAME Begins a program module. Module control

ODD Aligns the program location counter to an odd address.

Section control

OVERLAY Recognized but ignored. Symbol control

PROGRAM Begins a module. Module control

PUBLIC Exports symbols to other modules. Symbol control

PUBWEAK Exports symbols to other modules, multiple definitions allowed.

Symbol control

RADIX Sets the default base. Assembler control

REPT Assembles instructions a specified number of times. Macro processing

REPTC Repeats and substitutes characters. Macro processing

REPTI Repeats and substitutes strings. Macro processing

REQUIRE Forces a symbol to be referenced. Symbol control

RSEG Begins a section. Alias for SECTION. Section control

RTMODEL Declares runtime model attributes. Module control

SECTION Begins a section. Section control

SECTION_TYPE Sets ELF type and flags for a section. Section control

SET Assigns a temporary value. Value assignment



ARX-2



Module control directivesModule control directives are used for marking the beginning and end of source program modules, and for assigning names to them. See Expression restrictions, page 12, for a description of the restrictions that apply when using a directive in an expression.

SYNTAX

END

NAME symbol

PROGRAM symbol

RTMODEL key, value

PARAMETERS

DESCRIPTIONS

Beginning a module

Use any of the directives NAME or PROGRAM to begin an ELF module, and to assign a name.

VAR Assigns a temporary value. Value assignment



Directive Description Expression restrictions

END Ends the assembly of the last module in a file. Only locally defined labels or integer constants

NAME Begins amodule; alias to PROGRAM. No external referencesAbsolute

PROGRAM Begins amodule. No external referencesAbsolute

RTMODEL Declares runtime model attributes. Not applicable

Table 13: Module control directives

key A text string specifying the key.

symbol Name assigned to module.

value A text string specifying the value.

ARX-2

55

56

Module control directives

A module is included in the linked application, even if other modules do not reference them. For more information about how modules are included in the linked application, read about the linking process in the IAR C/C++ Development Guide for RX.

Note: There can be only one module in a file.

Terminating the source file

Use END to indicate the end of the source file. Any lines after the END directive are ignored. The END directive also ends the module in the file.

Declaring runtime model attributes

Use RTMODEL to enforce consistency between modules. All modules that are linked together and define the same runtime attribute key must have the same value for the corresponding key value, or the special value *. Using the special value * is equivalent to not defining the attribute at all. It can however be useful to explicitly state that the module can handle any runtime model.

A module can have several runtime model definitions.

Note: The compiler runtime model attributes start with double underscores. In order to avoid confusion, this style must not be used in the user-defined assembler attributes.

If you are writing assembler routines for use with C or C++ code, and you want to control the module consistency, refer to the IAR C/C++ Development Guide for RX.

Examples

The following examples define three modules in one source file each, where:

● MOD_1 and MOD_2 cannot be linked together since they have different values for runtime model CAN.

● MOD_1 and MOD_3 can be linked together since they have the same definition of runtime model RTOS and no conflict in the definition of CAN.

● MOD_2 and MOD_3 can be linked together since they have no runtime model conflicts. The value * matches any runtime model value.

Assembler source file f1.s:

module mod_1 rtmodel "CAN", "ISO11519" rtmodel "Platform", "M7" ; ... end

ARX-2




module mod_2 rtmodel "CAN", "ISO11898" rtmodel "Platform", "*" ; ... end


module mod_3 rtmodel "Platform", "M7" ; ... end

Symbol control directivesThese directives control how symbols are shared between modules:

SYNTAX

EXTERN symbol [,symbol] …

IMPORT symbol [,symbol] …

PUBLIC symbol [,symbol] …

PUBWEAK symbol [,symbol] …

REQUIRE symbol

PARAMETERS

Directive Description

EXTERN, IMPORT Imports an external symbol.

OVERLAY Recognized but ignored.

PUBLIC Exports symbols to other modules.

PUBWEAK Exports symbols to other modules, multiple definitions allowed.

REQUIRE Forces a symbol to be referenced.

Table 14: Symbol control directives

label Label to be used as an alias for a C/C++ symbol.

symbol Symbol to be imported or exported.

ARX-2

57

58

Symbol control directives

DESCRIPTIONS

Exporting symbols to other modules

Use PUBLIC to make one or more symbols available to other modules. Symbols defined PUBLIC can be relocatable or absolute, and can also be used in expressions (with the same rules as for other symbols).

The PUBLIC directive always exports full 32-bit values, which makes it feasible to use global 32-bit constants also in assemblers for 8-bit and 16-bit processors. With the LOW, HIGH, >>, and << operators, any part of such a constant can be loaded in an 8-bit or 16-bit register or word.

There can be any number of PUBLIC-defined symbols in a module.

Exporting symbols with multiple definitions to other modules

PUBWEAK is similar to PUBLIC except that it allows the same symbol to be defined in more than one module. Only one of those definitions is used by ILINK. If a module containing a PUBLIC definition of a symbol is linked with one or more modules containing PUBWEAK definitions of the same symbol, ILINK uses the PUBLIC definition.

Note: Library modules are only linked if a reference to a symbol in that module is made, and that symbol was not already linked. During the module selection phase, no distinction is made between PUBLIC and PUBWEAK definitions. This means that to ensure that the module containing the PUBLIC definition is selected, you should link it before the other modules, or make sure that a reference is made to some other PUBLIC symbol in that module.

Importing symbols

Use EXTERN or IMPORT to import an untyped external symbol.

The REQUIRE directive marks a symbol as referenced. This is useful if the section containing the symbol must be loaded for the code containing the reference to work, but the dependence is not otherwise evident.

EXAMPLES

The following example defines a subroutine to print an error message, and exports the entry address err so that it can be called from other modules.

Because the message is enclosed in double quotes, the string will be followed by a zero byte.

ARX-2



It defines print as an external routine; the address is resolved at link time.

name errorMessage extern print public err section CODE:CODE codeerr bra print data8 dc8 "** Error **" code rts end

Note: This example only works in little-endian mode.

Mode control directivesThese directives provide control over the assembly mode:

SYNTAX

CODEDATADATA8DATA16DATA32DATA64

DESCRIPTION

The CODE and DATA directives set the assembly mode for code and data sections. This information is used by C-SPY and IAR ELF Dumper.


CODE Subsequent instructions are assembled, linked, and disassembled as code.

DATA, DATA8 Subsequent instructions are assembled, linked, and disassembled as 8-bit data.




Table 15: Mode control directives

ARX-2

59

60

Mode control directives

Note: The CODE or DATA directives are required for big-endian applications, but they improve the disassembly for all applications.

The CODE or DATA directives can be used for:

● Starting a code/data producing a section fragment (SECTION) that actually generates bytes that end up in the image, either code or data

● Changing the assembly mode in the middle of a section fragment.

The directive should come after the section fragment start (for example after the SECTION directive) and immediately precede any code-generating part (instructions or DC declarations).

You do not need the CODE or DATA directives for declaring sections, extern labels etc, and not when you declare RAM space.

In big-endian mode, the two least significant address bits are inverted on the RX microcontroller. This means that the chip operates on four-byte chunks. If you change the byte order, as you do when you switch between the code and data assembly modes, you must make sure that each segment part begins on a 4-byte aligned address when you toggle the assembly mode between code and data, or linking will fail with an alignment error.

EXAMPLES

In this example, the disassembly mode changes several times to accommodate different types of data:

name codedata extern printStr public printDate section __DEFAULT_CODE_SECTION__:CODE

code ; Disassembled as codeprintDate: mov.l #a_date,R1 ; Load address of date ; string in R0. bsr printStr ; Call string output routine. rts data8 ; Disassembled as 8-bit data.a_date: dc8 __DATE__ ; String representing the ; date of assembly. end

ARX-2



Section control directivesThe section directives control how code and data are located. See Expression restrictions, page 12, for a description of the restrictions that apply when using a directive in an expression.

SYNTAX

ALIGN align [,value]

ALIGNRAM align

EVEN [value]

ODD [value]

RSEG section :type [flag] [(align)]

SECTION segment :type [flag] [(align)]

SECTION_TYPE type-expr {,flags-expr}

PARAMETERS


ALIGN Aligns the program location counter by inserting zero-filled bytes.

No external referencesAbsolute

ALIGNRAM Aligns the program location counter. No external referencesAbsolute

EVEN Aligns the program counter to an even address. No external referencesAbsolute

ODD Aligns the program counter to an odd address. No external referencesAbsolute

RSEG Begins a an ELF section; alias to SECTION. No external referencesAbsolute

SECTION Begins an ELF section. No external referencesAbsolute

SECTION_TYPE Sets ELF type and flags for a section.

Table 16: Section control directives

align The power of two to which the address should be aligned, in most cases in the range 0 to 30. The default align value is 0.

ARX-2

61

62

Section control directives

DESCRIPTIONS

Beginning a relocatable section

Use SECTION (or RSEG) to start a new section. The assembler maintains separate location counters (initially set to zero) for all sections, which makes it possible to switch sections and mode anytime without having to save the current program location counter.

Note: The first instance of a SECTION or RSEG directive must not be preceded by any code generating directives, such as DC8 or DS8, or by any assembler instructions.

To set the ELF type, and possibly the ELF flags for the newly created section, use SECTION_TYPE. By default, the values of the flags are zero. For information about valid values, refer to the ELF documentation.

Aligning a section

Use ALIGN to align the program location counter to a specified address boundary. The expression gives the power of two to which the program counter should be aligned and the permitted range is 0 to 8.

The alignment is made relative to the section start; normally this means that the section alignment must be at least as large as that of the alignment directive to give the desired result.

flag NOROOT, ROOTNOROOT means that the section fragment is discarded by the linker if no symbols in this section fragment are referred to. Normally, all section fragments except startup code and interrupt vectors should set this flag. The default mode is ROOT which indicates that the section fragment must not be discarded.

REORDER, NOREORDERREORDER starts a new section with the given name. The default mode is NOREORDER which starts a new fragment in the section with the given name, or a new section if no such section exists.

section The name of the section.

type The memory type, which can be either CODE, CONST, or DATA.

value Byte value used for padding, default is zero.

type-expr A constant expression identifying the ELF type of the section.

flags-expr A constant expression identifying the ELF flags of the section.

ARX-2



ALIGN aligns by inserting zero/filled bytes, up to a maximum of 255. The EVEN directive aligns the program counter to an even address (which is equivalent to ALIGN 1) and the ODD directive aligns the program location counter to an odd address. The byte value for padding must be within the range 0 to 255.

Use ALIGNRAM to align the program location counter by incrementing it; no data is generated. The expression can be within the range 0 to 30.

EXAMPLES

Beginning a relocatable section

In the following example, the data following the first SECTION directive is placed in a section called TABLE.

The code following the second SECTION directive is placed in a relocatable section called CODE:

name calculate extern operator extern addOperator, subOperator

section TABLE:CONST(8) data8operatorTable: dc8 addOperator, subOperator

section CODE:CODE codecalculate mov.l #operator,r1 mov.l [R1],R1 mov.l #operatorTable,R2 cmp [R2].ub,R1 beq add add #1,R2 cmp [R2].ub,R1 beq sub ;... rts

add ;... rts nopsub ;... rts nop

end

ARX-2

63

64

Value assignment directives

Aligning a section

This example starts a section, moves to an even address, and adds some data. It then aligns to a 64-byte boundary before creating a 64-byte table.

name alignment section DATA:DATA ; Start a relocatable data section. data16 ; Disassembled as 16-bit data even ; Ensure it is on an even boundary.target dc16 1 ; target and best will be on anbest dc16 1 ; even boundary. data8 ; Disassembled as 8-bit data align 6 ; Now, align to a 64-byte boundary,results ds8 64 ; and create a 64-byte table. end

Value assignment directivesThese directives are used for assigning values to symbols:

SYNTAX

label = expr

label ASSIGN expr

label DEFINE const_expr

label EQU expr

label SET expr

label VAR expr

PARAMETERS


=, EQU Assigns a permanent value local to a module.

ASSIGN, SET, VAR Assigns a temporary value.

DEFINE Defines a file-wide value.

Table 17: Value assignment directives

const_expr Constant value assigned to symbol.

expr Value assigned to symbol or value to be tested.

label Symbol to be defined.

ARX-2



DESCRIPTIONS

Defining a temporary value

Use ASSIGN, SET, or VAR to define a symbol that might be redefined, such as for use with macro variables. Symbols defined with ASSIGN, SET, or VAR cannot be declared PUBLIC.

Defining a permanent local value

Use EQU or = to create a local symbol that denotes a number or offset. The symbol is only valid in the module in which it was defined, but can be made available to other modules with a PUBLIC directive (but not with a PUBWEAK directive).

Use EXTERN to import symbols from other modules.

Defining a permanent global value

Use DEFINE to define symbols that should be known to the module containing the directive. After the DEFINE directive, the symbol is known.

A symbol which was given a value with DEFINE can be made available to modules in other files with the PUBLIC directive.

Symbols defined with DEFINE cannot be redefined within the same file. Also, the expression assigned to the defined symbol must be constant.

EXAMPLES

Redefining a symbol

This example uses SET to redefine the symbol cons in a loop to generate a table of the first 8 powers of 3:

name tablecons set 1

; Generate table of powers of 3.cr_tabl macro times dc32 conscons set cons * 3 if times > 1 cr_tabl times - 1 endif endm

ARX-2

65

66

Conditional assembly directives

section .text:CODE(2) datatable cr_tabl 4 end

It generates this code:

9 name table

10 000001 cons set 1

11

12 ; Generate table of powers of 3.

20

21 000000 section `.text`:CODE(2)

22 000000 data

23 000000 table cr_tabl 4

23.1 000000 01000000 dc32 cons

23.2 000003 cons set cons * 3

23.3 000004 if 4 > 1

23.4 000004 cr_tabl 4 - 1

23.5 000004 03000000 dc32 cons

23.6 000009 cons set cons * 3

23.7 000008 if 4 - 1 > 1

23.8 000008 cr_tabl 4 - 1 - 1

23.9 000008 09000000 dc32 cons

23.10 00001B cons set cons * 3

23.11 00000C if 4 - 1 - 1 > 1

23.12 00000C cr_tabl 4 - 1 - 1 - 1

23.13 00000C 1B000000 dc32 cons

23.14 000051 cons set cons * 3

23.15 000010 if 4 - 1 - 1 - 1 > 1

23.16 000010 endif

23.17 000010 endif

23.18 000010 endif

23.19 000010 endif

24 000010 end

Conditional assembly directivesThese directives provide logical control over the selective assembly of source code. See Expression restrictions, page 12, for a description of the restrictions that apply when using a directive in an expression.


ELSE Assembles instructions if a condition is false.

Table 18: Conditional assembly directives

ARX-2



SYNTAX

ELSE

ELSEIF condition

ENDIF

IF condition

PARAMETERS

DESCRIPTIONS

Use the IF, ELSE, and ENDIF directives to control the assembly process at assembly time. If the condition following the IF directive is not true, the subsequent instructions do not generate any code (that is, it is not assembled or syntax checked) until an ELSE or ENDIF directive is found.

ELSEIF Specifies a new condition in an IF…ENDIF block. No forward referencesNo external referencesAbsoluteFixed

ENDIF Ends an IF block.

IF Assembles instructions if a condition is true. No forward referencesNo external referencesAbsoluteFixed

condition One of these:

An absolute expression The expression must not contain forward or external references, and any non-zero value is considered as true.

string1==string2 The condition is true if string1 and string2 have the same length and contents.

string1!=string2 The condition is true if string1 and string2 have different lengths or contents.


Table 18: Conditional assembly directives (Continued)

ARX-2

67

68

Conditional assembly directives

Use ELSEIF to introduce a new condition after an IF directive. Conditional assembly directives can be used anywhere in an assembly, but have their greatest use in conjunction with macro processing.

All assembler directives (except for END) as well as the inclusion of files can be disabled by the conditional directives. Each IF directive must be terminated by an ENDIF directive. The ELSE directive is optional, and if used, it must be inside an IF...ENDIF block. IF...ENDIF and IF...ELSE...ENDIF blocks can be nested to any level.

EXAMPLES

This example uses a macro to add a constant to a direct page memory location:

addMem macro loc,val ; loc is a direct page memory ; location, and val is an ; 32-bit value to add to that ; location. if val = 0 ; Do nothing. elseif val < 16 mov.l #loc,R1 mov.l [R1],R2 add #val,R2 mov.l R2,[R1] else mov.l #loc,R1 mov.l [R1],R2 add #val,R2,R2 mov.l R2,[R1] endif endm module addWithMacro section CODE:CODE codeaddSome addMem 0xa0,0 ; Add 0 to memory location ; 0xa0. addMem 0xa0,1 ; Add 1 to the same address. addMem 0xa0,2 ; Add 2 to the same address. addMem 0xa0,3 ; Add 3 to the same address. addMem 0xa0,47 ; Add 47 to the same address. rts end

ARX-2



Macro processing directivesThese directives allow user macros to be defined. See Expression restrictions, page 12, for a description of the restrictions that apply when using a directive in an expression.

SYNTAX

_args

ENDM

ENDR

EXITM

LOCAL symbol [,symbol] …

name MACRO [argument] [,argument] …

REPT expr

REPTC formal,actual

REPTI formal,actual [,actual] …

PARAMETERS


_args Is set to number of arguments passed to macro.

ENDM Ends a macro definition.

ENDR Ends a repeat structure.

EXITM Exits prematurely from a macro.

LOCAL Creates symbols local to a macro.

MACRO Defines a macro.

REPT Assembles instructions a specified number of times. No forward referencesNo external referencesAbsoluteFixed

REPTC Repeats and substitutes characters.

REPTI Repeats and substitutes text.

Table 19: Macro processing directives

actual A string to be substituted.

argument A symbolic argument name.

expr An expression.

ARX-2

69

70

Macro processing directives

DESCRIPTIONS

A macro is a user-defined symbol that represents a block of one or more assembler source lines. Once you have defined a macro, you can use it in your program like an assembler directive or assembler mnemonic.

When the assembler encounters a macro, it looks up the macro’s definition, and inserts the lines that the macro represents as if they were included in the source file at that position.

Macros perform simple text substitution effectively, and you can control what they substitute by supplying parameters to them.

Defining a macro

You define a macro with the statement:

name MACRO [argument] [,argument] …

Here name is the name you are going to use for the macro, and argument is an argument for values that you want to pass to the macro when it is expanded.

For example, you could define a macro errMac as follows:

name errMacroerrMac macro text extern abort bsr abort data8 dc8 text,0 endm

Note: This example only works in little-endian mode.

This macro uses a parameter text to set up an error message for a routine abort. You would call the macro with a statement such as:

errMac 'Disk not ready'

The assembler expands this to:

bsr abort data8 dc8 'Disk not ready',0

formal An argument into which each character of actual (REPTC) or each actual (REPTI) is substituted.

name The name of the macro.

symbol A symbol to be local to the macro.

ARX-2



If you omit a list of one or more arguments, the arguments you supply when calling the macro are called \1 to \9 and \A to \Z.

The previous example could therefore be written as follows:

name errMacroerrMac macro text extern abort bsr abort data8 dc8 \1,0 endm

Use the EXITM directive to generate a premature exit from a macro.

EXITM is not allowed inside REPT...ENDR, REPTC...ENDR, or REPTI...ENDR blocks.

Use LOCAL to create symbols local to a macro. The LOCAL directive must be used before the symbol is used.

Each time that a macro is expanded, new instances of local symbols are created by the LOCAL directive. Therefore, it is legal to use local symbols in recursive macros.

Note: It is illegal to redefine a macro.

Passing special characters

Macro arguments that include commas or white space can be forced to be interpreted as one argument by using the matching quote characters < and > in the macro call.

For example:

name macroUsermovMac macro op mov.l op endm

The macro can be called using the macro quote characters:

movMac <0x19a0,R1>

You can redefine the macro quote characters with the -M command line option; see -M, page 28.

ARX-2

71

72


Predefined macro symbols

The symbol _args is set to the number of arguments passed to the macro. This example shows how _args can be used:

fill macro if _args == 2 rept \2 dc8 \1 endr else dc8 \1 endif endm

module fill section CODE:CODE data fill 3 fill 4, 3 end

It generates this code:

19 module fill

20 000000 section CODE:CODE

21 000000 data

22 000000 fill 3

22.1 000000 if _args == 2

22.2 000000 else

22.3 000000 03 dc8 3

22.4 000001 endif

23 000001 fill 4, 3

23.1 000001 if _args == 2

23.2 000001 rept 3

23.3 000001 04 dc8 4

23.4 000002 04 dc8 4

23.5 000003 04 dc8 4

23.6 000004 endr

23.7 000004 else

23.8 000004 endif

24 000004 end

ARX-2



How macros are processed

The macro process consists of three distinct phases:

1 The assembler scans and saves macro definitions. The text between MACRO and ENDM is saved but not syntax checked.

2 A macro call forces the assembler to invoke the macro processor (expander). The macro expander switches (if not already in a macro) the assembler input stream from a source file to the output from the macro expander. The macro expander takes its input from the requested macro definition.

The macro expander has no knowledge of assembler symbols since it only deals with text substitutions at source level. Before a line from the called macro definition is handed over to the assembler, the expander scans the line for all occurrences of symbolic macro arguments, and replaces them with their expansion arguments.

3 The expanded line is then processed as any other assembler source line. The input stream to the assembler continues to be the output from the macro processor, until all lines of the current macro definition have been read.

Repeating statements

Use the REPT...ENDR structure to assemble the same block of instructions several times. If expr evaluates to 0 nothing is generated.

Use REPTC to assemble a block of instructions once for each character in a string. If the string contains a comma it should be enclosed in quotation marks.

Only double quotes have a special meaning and their only use is to enclose the characters to iterate over. Single quotes have no special meaning and are treated as any ordinary character.

Use REPTI to assemble a block of instructions once for each string in a series of strings. Strings containing commas should be enclosed in quotation marks.

EXAMPLES

This section gives examples of the different ways in which macros can make assembler programming easier.

Coding inline for efficiency

In time-critical code it is often desirable to code routines inline to avoid the overhead of a subroutine call and return. Macros provide a convenient way of doing this.

ARX-2

73

74


This example outputs bytes from a buffer to a port:

name ioBufferSubroutine public copyBufferptbd equ 0x0002 ; Definition of the port B ; data register. section DATA16:DATA databuffer ds8 256

section CODE:CODE codecopyBuffer mov.l #buffer,R1 ; Initialize the loop counter. mov.l #ptbd,R3 mov.l #256,R4loop mov.b [R1+],R2 mov.b R2,[R3] sub #1,R4 bne loop ; Have we copied 256 bytes? rts end

The main program calls this routine as follows:

doCopy bsr copyBuffer

For efficiency we can recode this using a macro:

name ioBufferInlineptbd equ 0x0002 ; Definition of the port B ; data register. section DATA16:DATA databuffer ds8 256

section CODE:CODE codecopyBuffer macro mov.l #buffer,R1 ; Initialize the loop counter. mov.l #ptbd,R3 mov.l #256,R4loop mov.b [R1+],R2 mov.b R2,[R3] sub #1,R4 bne loop ; Have we copied 256 bytes? endm end

ARX-2



Notice the use of the LOCAL directive to make the label loop local to the macro; otherwise an error is generated if the macro is used twice, as the loop label already exists.

Using REPTC and REPTI

This example assembles a series of calls to a subroutine plot to plot each character in a string:

name reptc extern plotc section CODE:CODE codebanner reptc chr, "Welcome" mov.l #'chr',r1 bsr plotc endr rts end

This produces this code:

9 name reptc

10 000000 extern plotc


12 000000 CODE

13 000000 banner reptc chr, "Welcome"

13.1 000000 FB1657 mov.l #'W',r1

13.2 000003 05000000 bsr plotc

13.3 000007 FB1665 mov.l #'e',r1

13.4 00000A 05000000 bsr plotc

13.5 00000E FB166C mov.l #'l',r1

13.6 000011 05000000 bsr plotc

13.7 000015 FB1663 mov.l #'c',r1

13.8 000018 05000000 bsr plotc

13.9 00001C FB166F mov.l #'o',r1

13.10 00001F 05000000 bsr plotc

13.11 000023 FB166D mov.l #'m',r1

13.12 000026 05000000 bsr plotc

13.13 00002A FB1665 mov.l #'e',r1

13.14 00002D 05000000 bsr plotc

13.15 000031 endr

17 000031 02 rts

18 000032 end

ARX-2

75

76

Listing control directives

This example uses repti to clear several memory locations:

name repti extern base, count, init section CODE:CODE codebanner repti adds, base, count, init mov.l #adds,R1 mov.l #0,[R1] endr rts end

This produces this code:

9 name repti

10 000000 extern base, count, init


12 000000 code

13 000000 banner repti adds, base, count, init

13.1 000000 FB1200000000 mov.l #base,R1

13.2 000006 F81600 mov.l #0,[R1]

13.3 000009 FB1200000000 mov.l #count,R1

13.4 00000F F81600 mov.l #0,[R1]

13.5 000012 FB1200000000 mov.l #init,R1

13.6 000018 F81600 mov.l #0,[R1]

13.7 00001B endr

17 00001B 02 rts

18 00001C end

Listing control directivesThese directives provide control over the assembler list file:


LSTCND Controls conditional assembly listing.

LSTCOD Controls multi-line code listing.

LSTEXP Controls the listing of macro-generated lines.

LSTMAC Controls the listing of macro definitions.

LSTOUT Controls assembly-listing output.

LSTREP Controls the listing of lines generated by repeat directives.

LSTXRF Generates a cross-reference table.

Table 20: Listing control directives

ARX-2



Note: The directives COL, LSTPAGE, PAGE, and PAGSIZ are included for backward compatibility reasons; they are recognized but no action is taken.

SYNTAX

LSTCND{+|-}

LSTCOD{+|-}

LSTEXP{+|-}

LSTMAC{+|-}

LSTOUT{+|-}

LSTREP{+|-}

LSTXRF{+|-}

DESCRIPTIONS

Turning the listing on or off

Use LSTOUT- to disable all list output except error messages. This directive overrides all other listing control directives.

The default is LSTOUT+, which lists the output (if a list file was specified).

Listing conditional code and strings

Use LSTCND+ to force the assembler to list source code only for the parts of the assembly that are not disabled by previous conditional IF statements.

The default setting is LSTCND-, which lists all source lines.

Use LSTCOD+ to list more than one line of code for a source line, if needed; that is, long ASCII strings produce several lines of output.

The default setting is LSTCOD-, which restricts the listing of output code to just the first line of code for a source line.

Using the LSTCND and LSTCOD directives does not affect code generation.

Controlling the listing of macros

Use LSTEXP- to disable the listing of macro-generated lines. The default is LSTEXP+, which lists all macro-generated lines.

Use LSTMAC+ to list macro definitions. The default is LSTMAC-, which disables the listing of macro definitions.

ARX-2

77

78


Controlling the listing of generated lines

Use LSTREP- to turn off the listing of lines generated by the directives REPT, REPTC, and REPTI.

The default is LSTREP+, which lists the generated lines.

Generating a cross-reference table

Use LSTXRF+ to generate a cross-reference table at the end of the assembler list for the current module. The table shows values and line numbers, and the type of the symbol.

The default is LSTXRF-, which does not give a cross-reference table.

EXAMPLES

Turning the listing on or off

To disable the listing of a debugged section of program:

lstout- ; This section has already been debugged. lstout+ ; This section is currently being debugged. end

Listing conditional code and strings

This example shows how LSTCND+ hides a call to a subroutine that is disabled by an IF directive:

name lstcndTest extern print section FLASH:CODE codedebug set 0begin if debug bsr print endif

lstcnd+begin2 if debug bsr print endif

end

ARX-2



This generates the following listing:

9 name lstcndTest

10 000000 extern print

11 000000 section FLASH:CODE

12 000000 code

13 000000 debug set 0

14 000000 begin if debug

15 bsr print

16 000000 endif

17

18 lstcnd+

19 000000 begin2 if debug

21 000000 endif

22

23 000000 end

Controlling the listing of macros

This example shows the effect of LSTMAC and LSTEXP:

name lstmacTest extern memLoc section FLASH:CODE(2) code

dec2 macro arg mov.l #arg,R1 mov.l [R1],R2 sub #2,R1 mov.l R2,[R1] endm

lstmac+inc2 macro arg mov.l #arg,R1 mov.l [R1],R2 add #2,R2 mov.l R2,[R1] endm

begin dec2 memLoc lstexp- inc2 memLoc rts

ARX-2

79

80


; Restore default values for; listing control directives.

lstmac- lstexp+

end

This produces the following output:

9 name lstmacTest

10 000000 extern memLoc

11 000000 section FLASH:CODE(2)

12 000000 code

13

20

21 lstmac+

22 inc2 macro arg

23 mov.l #arg,R1

24 mov.l [R1],R2

25 add #2,R2

26 mov.l R2,[R1]

27 endm

28

29 000000 begin dec2 memLoc

29.1 000000 FB1200000000 mov.l #memLoc,R1

29.2 000006 EC12 mov.l [R1],R2

29.3 000008 6021 sub #2,R1

29.4 00000A E312 mov.l R2,[R1]

30 lstexp-

31 00000C inc2 memLoc

32 000018 02 rts

33 ; Restore default values for

34 ; listing control directives.

35

36 lstmac-

37 lstexp+

38

39 000019 end

ARX-2



C-style preprocessor directivesThe assembler has a C-style preprocessor that follows the C99 standard.

These C-language preprocessor directives are available:

SYNTAX

#define symbol text

#elif condition

#else

#endif

#error "message"

#if condition

#ifdef symbol

#ifndef symbol

#include {"filename" | <filename>}

#line line-no {"filename"}

#undef symbol


#define Assigns a value to a preprocessor symbol.

#elif Introduces a new condition in an #if...#endif block.

#else Assembles instructions if a condition is false.

#endif Ends an #if, #ifdef, or #ifndef block.

#error Generates an error.

#if Assembles instructions if a condition is true.

#ifdef Assembles instructions if a preprocessor symbol is defined.

#ifndef Assembles instructions if a preprocessor symbol is undefined.

#include Includes a file.

#line Changes the source references in the debug information.

#pragma Controls extension features. The supported #pragma directives are described in the chapter Pragma directives.

#undef Undefines a preprocessor symbol.

Table 21: C-style preprocessor directives

ARX-2

81

82

C-style preprocessor directives

PARAMETERS

DESCRIPTIONS

You must not mix assembler language and C-style preprocessor directives. Conceptually, they are different languages and mixing them might lead to unexpected behavior because an assembler directive is not necessarily accepted as a part of the C preprocessor language.

Note that the preprocessor directives are processed before other directives. As an example avoid constructs like:

redef macro ; Avoid the following!#define \1 \2 endm

because the \1 and \2 macro arguments are not available during the preprocessing phase.

Defining and undefining preprocessor symbols

Use #define to define a value of a preprocessor symbol.

#define symbol value

Use #undef to undefine a symbol; the effect is as if it had not been defined.

Conditional preprocessor directives

Use the #if...#else...#endif directives to control the assembly process at assembly time. If the condition following the #if directive is not true, the subsequent instructions

condition An absolute expression The expression must not contain any assembler labels or symbols, and any non-zero value is considered as true.

filename Name of file to be included or referred.

line-no Source line number.

message Text to be displayed.

symbol Preprocessor symbol to be defined, undefined, or tested.

text Value to be assigned.

ARX-2



will not generate any code (that is, it will not be assembled or syntax checked) until an #endif or #else directive is found.

All assembler directives (except for END) and file inclusion can be disabled by the conditional directives. Each #if directive must be terminated by an #endif directive. The #else directive is optional and, if used, it must be inside an #if...#endif block.

#if...#endif and #if...#else...#endif blocks can be nested to any level.

Use #ifdef to assemble instructions up to the next #else or #endif directive only if a symbol is defined.

Use #ifndef to assemble instructions up to the next #else or #endif directive only if a symbol is undefined.

Including source files

Use #include to insert the contents of a file into the source file at a specified point. The filename can be specified within double quotes or within angle brackets.

Following is the full description of the assembler’s #include file search procedure:

● If the name of the #include file is an absolute path, that file is opened.

● When the assembler encounters the name of an #include file in angle brackets such as:

#include <iorx62n.h>

it searches the following directories for the file to include:

1 The directories specified with the -I option, in the order that they were specified.

2 The directories specified using the ARX_INC environment variable, if any.

● When the assembler encounters the name of an #include file in double quotes such as:

#include "vars.h"

it searches the directory of the source file in which the #include statement occurs, and then performs the same sequence as for angle-bracketed filenames.

If there are nested #include files, the assembler starts searching the directory of the file that was last included, iterating upwards for each included file, searching the source file directory last.

Use angle brackets for header files provided with the IAR Assembler for RX, and double quotes for header files that are part of your application.

ARX-2

83

84

C-style preprocessor directives

Displaying errors

Use #error to force the assembler to generate an error, such as in a user-defined test.

Comments in C-style preprocessor directives

If you make a comment within a define statement, use:

● the C comment delimiters /* ... */ to comment sections

● the C++ comment delimiter // to mark the rest of the line as comment.

Do not use assembler comments within a define statement as it leads to unexpected behavior.

This expression evaluates to 3 because the comment character is preserved by #define:

#define x 3 ; This is a misplaced comment.

module misplacedComment1expression equ x * 8 + 5 ;... end

This example illustrates some problems that might occur when assembler comments are used in the C-style preprocessor:

#define five 5 ; This comment is not OK.#define six 6 // This comment is OK.#define seven 7 /* This comment is OK. */

module misplacedComment2 section MYCONST:CONST(2)

DC32 five, 11, 12; The previous line expands to:; "DC32 5 ; This comment is not OK., 11, 12"

DC32 six + seven, 11, 12; The previous line expands to:; "DC32 6 + 7, 11, 12"

end

Changing the source line numbers

Use the #line directive to change the source line numbers and the source filename used in the debug information. #line operates on the lines following the #line directive.

ARX-2



EXAMPLES

Using conditional preprocessor directives

This example defines the labels tweak and adjust. If adjust is defined, then register 16 is decremented by an amount that depends on adjust, in this case 30.

name calibrate extern calibrationConstant section CODE:CODE code#define tweak 1#define adjust 3

calibrate mov.l #calibrationConstant,R1 mov.l [R1],R2#ifdef tweak#if adjust==1 sub #4,R2#elif adjust==2 add #-20,R2#elif adjust==3 add #-30,R2,R2#endif#endif /* ifdef tweak */ mov.b R2,[R1] rts end

Including a source file

This example uses #include to include a file defining macros into the source file. For example, these macros could be defined in Macros.inc:

; Exchange registers a and b.; Use the stack for temporary storage.

xch macro a,b push.l \1 push.l \2 pop \2 pop \1 endm

ARX-2

85

86

Data definition or allocation directives

The macro definitions can then be included, using #include, as in this example:

program includeFile public xchRegs section CODE:CODE code; Standard macro definitions#include "Macros.inc"

xchRegs xch r1,r3 xch r2,r4 rts

end

Data definition or allocation directivesThese directives define values or reserve memory. The column Alias in the following table shows the Renesas directive that corresponds to the IAR Systems directive. See Expression restrictions, page 12, for a description of the restrictions that apply when using a directive in an expression.


DC8 Generates 8-bit constants, including strings.

DC16 Generates 16-bit constants.




DF32 Generates 32-bit floating-point constants.

DF64 Generates 64-bit floating-point constants.

DQ15 Generates 16-bit fractional constants.

DQ31 Generates 32-bit fractional constants.

DS8 Allocates space for 8-bit integers.





Table 22: Data definition or allocation directives

ARX-2



SYNTAX

DC8 expr [,expr] ...





DF32 value [,value] ...

DF64 value [,value] ...

DQ15 value [,value] ...

DQ31 value [,value] ...

DS8 count

DS16 count

DS24 count

DS32 count

DS64 count

PARAMETERS

DESCRIPTIONS

Use DC8, DC16, DC24, DC32, DC64, DF32, or DF64 to create a constant, which means an area of bytes is reserved big enough for the constant.

Use DS8, DS16, DS24, DS32, or DS64 to reserve a number of uninitialized bytes.

count A valid absolute expression specifying the number of elements to be reserved.

expr A valid absolute, relocatable, or external expression, or an ASCII string. ASCII strings are zero filled to a multiple of the data size implied by the directive. Double-quoted strings are zero-terminated. For DC64, expr cannot be relocatable or external.

value A valid absolute expression or floating-point constant.

ARX-2

87

88

Data definition or allocation directives

EXAMPLES

Generating a lookup table

This example generates a constant table of 8-bit data that is accessed via the call instruction and added up to a sum.

module sumTableAndIndex section DATA16:CONST DATAtable dc8 12 dc8 15 dc8 17 dc8 16 dc8 14 dc8 11 dc8 9

section CODE:CODE codecount set 0

addTable mov #0,R1 mov.l #table,R2

rept 7 if count == 7 exitm endif mov.b [R2+],R4 add R4,R1count set count + 1 endr

rts end

Defining strings

To define a string:

myMsg DC8 'Please enter your name'

To define a string which includes a trailing zero:

myCstr DC8 "This is a string."

To include a single quote in a string, enter it twice; for example:

errMsg DC8 'Don''t understand!'

ARX-2



Reserving space

To reserve space for 10 bytes:

table DS8 10

Assembler control directivesThese directives provide control over the operation of the assembler. See Expression restrictions, page 12, for a description of the restrictions that apply when using a directive in an expression.

SYNTAX

/*comment*/

//comment

CASEOFF

CASEON

RADIX expr

PARAMETERS

DESCRIPTIONS

Use /*...*/ to comment sections of the assembler listing.

Use // to mark the rest of the line as comment.

Use RADIX to set the default base for constants. The default base is 10.


/*comment*/ C-style comment delimiter.

// C++ style comment delimiter.

CASEOFF Disables case sensitivity.

CASEON Enables case sensitivity.

RADIX Sets the default base on all numeric values.

No forward referencesNo external referencesAbsoluteFixed

Table 23: Assembler control directives

comment Comment ignored by the assembler.

expr Default base; default 10 (decimal).

ARX-2

89

90

Assembler control directives

Controlling case sensitivity

Use CASEON or CASEOFF to turn on or off case sensitivity for user-defined symbols. By default, case sensitivity is on.

When CASEOFF is active all symbols are stored in upper case, and all symbols used by ILINK should be written in upper case in the ILINK definition file.

EXAMPLES

Defining comments

This example shows how /*...*/ can be used for a multi-line comment:

/*Program to read serial input.Version 1: 19.2.10Author: mjp*/

See also Comments in C-style preprocessor directives, page 84.

Changing the base

To set the default base to 16:

radix 16 ; With the default base set mov.l #12,R1 ; to 16, the immediate value ;... ; of the load instruction is ; interpreted as 0x12.

; To reset the base from 16 to 10 again, the argument must be; written in hexadecimal format.

radix 0x0a ; Reset the default base to 10 mov.l #12,R2 ; Now, the immediate value of ;... ; the load instruction is ; interpreted as 0x0c.

ARX-2



Controlling case sensitivity

When CASEOFF is set, label and LABEL are identical in this example:

module caseSensitivity1 section CODE:CODE

caseoff CODElabel nop ; Stored as "LABEL". bra LABEL nop end

The following will generate a duplicate label error:

module caseSensitivity2 section CODE:CODE CODE caseofflabel nop ; Stored as "LABEL".LABEL nop ; Error, "LABEL" already defined. end

Call frame information directivesThese directives allow backtrace information to be defined in the assembler source code. The benefit is that you can view the call frame stack when you debug your assembler code.


CFI BASEADDRESS Declares a base address CFA (Canonical Frame Address).

CFI BLOCK Starts a data block.

CFI CODEALIGN Declares code alignment.

CFI COMMON Starts or extends a common block.

CFI CONDITIONAL Declares a data block to be a conditional thread.

CFI DATAALIGN Declares data alignment.

CFI ENDBLOCK Ends a data block.

CFI ENDCOMMON Ends a common block.

CFI ENDNAMES Ends a names block.

CFI FRAMECELL Creates a reference into the caller’s frame.

CFI FUNCTION Declares a function associated with data block.

Table 24: Call frame information directives

ARX-2

91

92

Call frame information directives

SYNTAX

The syntax definitions below show the syntax of each directive. The directives are grouped according to usage.

Names block directives

CFI NAMES name

CFI ENDNAMES name

CFI RESOURCE resource : bits [, resource : bits] …

CFI VIRTUALRESOURCE resource : bits [, resource : bits] …

CFI RESOURCEPARTS resource part, part [, part] …

CFI STACKFRAME cfa resource type [, cfa resource type] …

CFI STATICOVERLAYFRAME cfa section [, cfa section] …

CFI BASEADDRESS cfa type [, cfa type] …

Extended names block directives

CFI NAMES name EXTENDS namesblock

CFI ENDNAMES name

CFI FRAMECELL cell cfa (offset): size [, cell cfa (offset): size] …

CFI INVALID Starts a range of invalid backtrace information.

CFI NAMES Starts a names block.

CFI NOFUNCTION Declares a data block to not be associated with a function.

CFI PICKER Declares a data block to be a picker thread.

CFI REMEMBERSTATE Remembers the backtrace information state.

CFI RESOURCE Declares a resource.

CFI RESOURCEPARTS Declares a composite resource.

CFI RESTORESTATE Restores the saved backtrace information state.

CFI RETURNADDRESS Declares a return address column.

CFI STACKFRAME Declares a stack frame CFA.

CFI STATICOVERLAYFRAME Declares a static overlay frame CFA.

CFI VALID Ends a range of invalid backtrace information.

CFI VIRTUALRESOURCE Declares a virtual resource.

CFI cfa Declares the value of a CFA.

CFI resource Declares the value of a resource.


Table 24: Call frame information directives (Continued)

ARX-2



Common block directives

CFI COMMON name USING namesblock

CFI ENDCOMMON name

CFI CODEALIGN codealignfactor

CFI DATAALIGN dataalignfactor

CFI RETURNADDRESS resource type

CFI cfa { NOTUSED | USED }

CFI cfa { resource | resource + constant | resource - constant }

CFI cfa cfiexpr

CFI resource { UNDEFINED | SAMEVALUE | CONCAT }

CFI resource { resource | FRAME(cfa, offset) }

CFI resource cfiexpr

Extended common block directives

CFI COMMON name EXTENDS commonblock USING namesblock

CFI ENDCOMMON name

Data block directives

CFI BLOCK name USING commonblock

CFI ENDBLOCK name

CFI { NOFUNCTION | FUNCTION label }

CFI { INVALID | VALID }

CFI { REMEMBERSTATE | RESTORESTATE }

CFI PICKER

CFI CONDITIONAL label [, label] …


CFI cfa cfiexpr



CFI resource cfiexpr

PARAMETERS

bits The size of the resource in bits.

cell The name of a frame cell.

cfa The name of a CFA (canonical frame address).

ARX-2

93

94


DESCRIPTIONS

The call frame information directives (CFI directives) are an extension to the debugging format of the IAR C-SPY® Debugger. The CFI directives are used for defining the backtrace information for the instructions in a program. The compiler normally generates this information, but for library functions and other code written purely in assembler language, backtrace information must be added if you want to use the call frame stack in the debugger.

cfiexpr A CFI expression (see CFI expressions, page 100).

codealignfactor The smallest factor of all instruction sizes. Each CFI directive for a data block must be placed according to this alignment. 1 is the default and can always be used, but a larger value shrinks the produced backtrace information in size. The possible range is 1–256.

commonblock The name of a previously defined common block.

constant A constant value or an assembler expression that can be evaluated to a constant value.

dataalignfactor The smallest factor of all frame sizes. If the stack grows toward higher addresses, the factor is negative; if it grows toward lower addresses, the factor is positive. 1 is the default, but a larger value shrinks the produced backtrace information in size. The possible ranges are -256 to -1 and 1 to 256.

label A function label.

name The name of the block.

namesblock The name of a previously defined names block.

offset The offset relative the CFA. An integer with an optional sign.

part A part of a composite resource. The name of a previously declared resource.

resource The name of a resource.

section The name of a section.

size The size of the frame cell in bytes.

type The memory type, such as CODE, CONST or DATA. In addition, any of the memory types supported by the IAR ILINK Linker. It is used solely for the purpose of denoting an address space.

ARX-2



The backtrace information is used to keep track of the contents of resources, such as registers or memory cells, in the assembler code. This information is used by the IAR C-SPY Debugger to go “back” in the call stack and show the correct values of registers or other resources before entering the function. In contrast with traditional approaches, this permits the debugger to run at full speed until it reaches a breakpoint, stop at the breakpoint, and retrieve backtrace information at that point in the program. The information can then be used to compute the contents of the resources in any of the calling functions—assuming they have call frame information as well.

Backtrace rows and columns

At each location in the program where it is possible for the debugger to break execution, there is a backtrace row. Each backtrace row consists of a set of columns, where each column represents an item that should be tracked. There are three kinds of columns:

● The resource columns keep track of where the original value of a resource can be found.

● The canonical frame address columns (CFA columns) keep track of the top of the function frames.

● The return address column keeps track of the location of the return address.

There is always exactly one return address column and usually only one CFA column, although there might be more than one.

Defining a names block

A names block is used to declare the resources available for a processor. Inside the names block, all resources that can be tracked are defined.

Start and end a names block with the directives:

CFI NAMES nameCFI ENDNAMES name

where name is the name of the block.

Only one names block can be open at a time.

Inside a names block, four different kinds of declarations can appear: a resource declaration, a stack frame declaration, a static overlay frame declaration, or a base address declaration:

● To declare a resource, use one of the directives:

CFI RESOURCE resource : bitsCFI VIRTUALRESOURCE resource : bits

ARX-2

95

96


The parameters are the name of the resource and the size of the resource in bits. A virtual resource is a logical concept, in contrast to a “physical” resource such as a processor register. Virtual resources are usually used for the return address.

To declare more than one resource, separate them with commas.

A resource can also be a composite resource, made up of at least two parts. To declare the composition of a composite resource, use the directive:

CFI RESOURCEPARTS resource part, part, …

The parts are separated with commas. The resource and its parts must have been previously declared as resources, as described above.

● To declare a stack frame CFA, use the directive:

CFI STACKFRAME cfa resource type

The parameters are the name of the stack frame CFA, the name of the associated resource (the stack pointer), and the section type (to get the address space). To declare more than one stack frame CFA, separate them with commas.

When going “back” in the call stack, the value of the stack frame CFA is copied into the associated stack pointer resource to get a correct value for the previous function frame.

● To declare a static overlay frame CFA, use the directive:

CFI STATICOVERLAYFRAME cfa section

The parameters are the name of the CFA and the name of the section where the static overlay for the function is located. To declare more than one static overlay frame CFA, separate them with commas.

● To declare a base address CFA, use the directive:

CFI BASEADDRESS cfa type

The parameters are the name of the CFA and the section type. To declare more than one base address CFA, separate them with commas.

A base address CFA is used to conveniently handle a CFA. In contrast to the stack frame CFA, there is no associated stack pointer resource to restore.

Extending a names block

In some special cases you must extend an existing names block with new resources. This occurs whenever there are routines that manipulate call frames other than their own, such as routines for handling, entering, and leaving C or C++ functions; these routines manipulate the caller’s frame. Extended names blocks are normally used only by compiler developers.

Extend an existing names block with the directive:

CFI NAMES name EXTENDS namesblock

ARX-2



where namesblock is the name of the existing names block and name is the name of the new extended block. The extended block must end with the directive:

CFI ENDNAMES name

Defining a common block

The common block is used for declaring the initial contents of all tracked resources. Normally, there is one common block for each calling convention used.

Start a common block with the directive:

CFI COMMON name USING namesblock

where name is the name of the new block and namesblock is the name of a previously defined names block.

Declare the return address column with the directive:

CFI RETURNADDRESS resource type

where resource is a resource defined in namesblock and type is the section type. You must declare the return address column for the common block.

End a common block with the directive:

CFI ENDCOMMON name

where name is the name used to start the common block.

Inside a common block, you can declare the initial value of a CFA or a resource by using the directives listed last in Common block directives, page 93. For more information on these directives, see Simple rules, page 98, and CFI expressions, page 100.

Extending a common block

Since you can extend a names block with new resources, it is necessary to have a mechanism for describing the initial values of these new resources. For this reason, it is also possible to extend common blocks, effectively declaring the initial values of the extra resources while including the declarations of another common block. Just as in the case of extended names blocks, extended common blocks are normally only used by compiler developers.

Extend an existing common block with the directive:

CFI COMMON name EXTENDS commonblock USING namesblock

where name is the name of the new extended block, commonblock is the name of the existing common block, and namesblock is the name of a previously defined names block. The extended block must end with the directive:

CFI ENDCOMMON name

ARX-2

97

98


Defining a data block

The data block contains the actual tracking information for one continuous piece of code. No section control directive can appear inside a data block.

Start a data block with the directive:

CFI BLOCK name USING commonblock

where name is the name of the new block and commonblock is the name of a previously defined common block.

If the piece of code is part of a defined function, specify the name of the function with the directive:

CFI FUNCTION label

where label is the code label starting the function.

If the piece of code is not part of a function, specify this with the directive:

CFI NOFUNCTION

End a data block with the directive:

CFI ENDBLOCK name

where name is the name used to start the data block.

Inside a data block, you can manipulate the values of the columns by using the directives listed last in Data block directives, page 93. For more information on these directives, see Simple rules, page 98, and CFI expressions, page 100.

SIMPLE RULES

To describe the tracking information for individual columns, there is a set of simple rules with specialized syntax:

CFI cfa { NOTUSED | USED }




You can use these simple rules both in common blocks to describe the initial information for resources and CFAs, and inside data blocks to describe changes to the information for resources or CFAs.

In those rare cases where the descriptive power of the simple rules are not enough, you can use a full CFI expression to describe the information (see CFI expressions, page 100). However, whenever possible, you should always use a simple rule instead of a CFI expression.

ARX-2



There are two different sets of simple rules: one for resources and one for CFAs.

Simple rules for resources

The rules for resources conceptually describe where to find a resource when going back one call frame. For this reason, the item following the resource name in a CFI directive is referred to as the location of the resource.

To declare that a tracked resource is restored, that is, already correctly located, use SAMEVALUE as the location. Conceptually, this declares that the resource does not have to be restored since it already contains the correct value. For example, to declare that a register REG is restored to the same value, use the directive:

CFI REG SAMEVALUE

To declare that a resource is not tracked, use UNDEFINED as location. Conceptually, this declares that the resource does not have to be restored (when going back one call frame) since it is not tracked. Usually it is only meaningful to use it to declare the initial location of a resource. For example, to declare that REG is a scratch register and does not have to be restored, use the directive:

CFI REG UNDEFINED

To declare that a resource is temporarily stored in another resource, use the resource name as its location. For example, to declare that a register REG1 is temporarily located in a register REG2 (and should be restored from that register), use the directive:

CFI REG1 REG2

To declare that a resource is currently located somewhere on the stack, use FRAME(cfa, offset) as location for the resource, where cfa is the CFA identifier to use as “frame pointer” and offset is an offset relative the CFA. For example, to declare that a register REG is located at offset -4 counting from the frame pointer CFA_SP, use the directive:

CFI REG FRAME(CFA_SP,-4)

For a composite resource there is one additional location, CONCAT, which declares that the location of the resource can be found by concatenating the resource parts for the composite resource. For example, consider a composite resource RET with resource parts RETLO and RETHI. To declare that the value of RET can be found by investigating and concatenating the resource parts, use the directive:

CFI RET CONCAT

This requires that at least one of the resource parts has a definition, using the rules described above.

ARX-2

99

100


Simple rules for CFAs

In contrast with the rules for resources, the rules for CFAs describe the address of the beginning of the call frame. The call frame often includes the return address pushed by the subroutine calling instruction. The CFA rules describe how to compute the address to the beginning of the current call frame. There are two different forms of CFAs, stack frames and static overlay frames, each declared in the associated names block. See Names block directives, page 92.

Each stack frame CFA is associated with a resource, such as the stack pointer. When going back one call frame the associated resource is restored to the current CFA. For stack frame CFAs there are two possible simple rules: an offset from a resource (not necessarily the resource associated with the stack frame CFA) or NOTUSED.

To declare that a CFA is not used, and that the associated resource should be tracked as a normal resource, use NOTUSED as the address of the CFA. For example, to declare that the CFA with the name CFA_SP is not used in this code block, use the directive:

CFI CFA_SP NOTUSED

To declare that a CFA has an address that is offset relative the value of a resource, specify the resource and the offset. For example, to declare that the CFA with the name CFA_SP can be obtained by adding 4 to the value of the SP resource, use the directive:

CFI CFA_SP SP + 4

For static overlay frame CFAs, there are only two possible declarations inside common and data blocks: USED and NOTUSED.

CFI EXPRESSIONS

You can use call frame information expressions (CFI expressions) when the descriptive power of the simple rules for resources and CFAs is not enough. However, you should always use a simple rule when one is available.

CFI expressions consist of operands and operators. Only the operators described below are allowed in a CFI expression. In most cases, they have an equivalent operator in the regular assembler expressions.

In the operand descriptions, cfiexpr denotes one of these:

● A CFI operator with operands

● A numeric constant

● A CFA name

● A resource name.

ARX-2



Unary operators

Overall syntax: OPERATOR(operand)

Binary operators

Overall syntax: OPERATOR(operand1,operand2)

Operator Operand Description

COMPLEMENT cfiexpr Performs a bitwise NOT on a CFI expression.

LITERAL expr Get the value of the assembler expression. This can insert the value of a regular assembler expression into a CFI expression.

NOT cfiexpr Negates a logical CFI expression.

UMINUS cfiexpr Performs arithmetic negation on a CFI expression.

Table 25: Unary operators in CFI expressions

Operator Operands Description

ADD cfiexpr,cfiexpr Addition

AND cfiexpr,cfiexpr Bitwise AND

DIV cfiexpr,cfiexpr Division

EQ cfiexpr,cfiexpr Equal

GE cfiexpr,cfiexpr Greater than or equal

GT cfiexpr,cfiexpr Greater than

LE cfiexpr,cfiexpr Less than or equal

LSHIFT cfiexpr,cfiexpr Logical shift left of the left operand. The number of bits to shift is specified by the right operand. The sign bit will not be preserved when shifting.

LT cfiexpr,cfiexpr Less than

MOD cfiexpr,cfiexpr Modulo

MUL cfiexpr,cfiexpr Multiplication

NE cfiexpr,cfiexpr Not equal

OR cfiexpr,cfiexpr Bitwise OR

RSHIFTA cfiexpr,cfiexpr Arithmetic shift right of the left operand. The number of bits to shift is specified by the right operand. In contrast with RSHIFTL, the sign bit is preserved when shifting.

Table 26: Binary operators in CFI expressions

ARX-2

101

102


Ternary operators

Overall syntax: OPERATOR(operand1,operand2,operand3)

EXAMPLE

The following is a generic example and not an example specific to the RX microcontroller. This simplifies the example and clarifies the usage of the CFI directives. To obtain a target-specific example, generate assembler output when you compile a C source file.

Consider a generic processor with a stack pointer SP, and two registers R0 and R1. Register R0 is used as a scratch register (the register is destroyed by the function call),

RSHIFTL cfiexpr,cfiexpr Logical shift right of the left operand. The number of bits to shift is specified by the right operand. The sign bit will not be preserved when shifting.

SUB cfiexpr,cfiexpr Subtraction

XOR cfiexpr,cfiexpr Bitwise XOR


FRAME cfa,size,offset Gets the value from a stack frame. The operands are:cfa An identifier denoting a previously declared CFA.size A constant expression denoting a size in bytes.offset A constant expression denoting an offset in

bytes.Gets the value at address cfa+offset of size size.

IF cond,true,false Conditional operator. The operands are:cond A CFA expression denoting a condition.true Any CFA expression.false Any CFA expression.If the conditional expression is non-zero, the result is the value of the true expression; otherwise the result is the value of the false expression.

LOAD size,type,addr Gets the value from memory. The operands are:size A constant expression denoting a size in bytes.type A memory type.addr A CFA expression denoting a memory address.Gets the value at address addr in section type type of size size.

Table 27: Ternary operators in CFI expressions


Table 26: Binary operators in CFI expressions (Continued)

ARX-2



whereas register R1 must be restored after the function call. For reasons of simplicity, all instructions, registers, and addresses have a width of 16 bits.

Consider the following short code sample with the corresponding backtrace rows and columns. At entry, assume that the stack contains a 16-bit return address. The stack grows from high addresses toward zero. The CFA denotes the top of the call frame, that is, the value of the stack pointer after returning from the function.

Each backtrace row describes the state of the tracked resources before the execution of the instruction. As an example, for the MOV R1,R0 instruction the original value of the R1 register is located in the R0 register and the top of the function frame (the CFA column) is SP + 2. The backtrace row at address 0000 is the initial row and the result of the calling convention used for the function.

The SP column is empty since the CFA is defined in terms of the stack pointer. The RET column is the return address column—that is, the location of the return address. The R0 column has a ‘—’ in the first line to indicate that the value of R0 is undefined and does not need to be restored on exit from the function. The R1 column has SAME in the initial row to indicate that the value of the R1 register will be restored to the same value it already has.

Defining the names block

The names block for the small example above would be:

cfi names trivialNames cfi resource SP:16, R0:16, R1:16 cfi stackframe CFA SP DATA

; The virtual resource for the return address column. cfi virtualresource RET:16 cfi endnames trivialNames

Address CFA SP R0 R1 RET Assembler code

0000 SP + 2 — SAME CFA - 2 func1: PUSH R1

0002 SP + 4 CFA - 4 MOV R1,#4

0004 CALL func2

0006 POP R0

0008 SP + 2 R0 MOV R1,R0

000A SAME RET

Table 28: Code sample with backtrace rows and columns

ARX-2

103

104


Defining the common block

The common block for the simple example above would be:

cfi common trivialCommon using trivialNames cfi returnaddress RET DATA cfi CFA SP + 2 cfi R0 undefined cfi R1 samevalue cfi RET frame(CFA,-2) ; Offset -2 from top of frame. cfi endcommon trivialCommon

Note: SP cannot be changed using a CFI directive since it is the resource associated with CFA.

Defining the data block

Continuing the simple example, the data block would be:

rseg CODE:CODE cfi block func1block using trivialCommon cfi function func1

func1 push r1 cfi CFA SP + 4 cfi R1 frame(CFA,-4) mov r1,#4 call func2 pop r0 cfi R1 R0 cfi CFA SP + 2 mov r1,r0 cfi R1 samevalue ret cfi endblock func1block

Note that the CFI directives are placed after the instruction that affects the backtrace information.

ARX-2


Pragma directivesThis chapter describes the pragma directives of the IAR Assembler for RX.

The pragma directives control the behavior of the assembler, for example whether it outputs warning messages. The pragma directives are preprocessed, which means that macros are substituted in a pragma directive.

Summary of pragma directivesThis table shows the pragma directives of the assembler:

Descriptions of pragma directivesAll pragma directives using = for value assignment should be entered like:

#pragma pragmaname=pragmavalue

or

#pragma pragmaname = pragmavalue

#pragma diag_default #pragma diag_default=tag,tag,...

Changes the severity level back to default or as defined on the command line for the diagnostic messages with the specified tags. For example:

#pragma diag_default=Pe117

See the chapter Diagnostics for more information about diagnostic messages.

#pragma directive Description

#pragma diag_default Changes the severity level of diagnostic messages

#pragma diag_error Changes the severity level of diagnostic messages

#pragma diag_remark Changes the severity level of diagnostic messages

#pragma diag_suppress Suppresses diagnostic messages

#pragma diag_warning Changes the severity level of diagnostic messages

#pragma message Prints a message

Table 29: Pragma directives summary

ARX-2

105

106

Descriptions of pragma directives

#pragma diag_error #pragma diag_error=tag,tag,...

Changes the severity level to error for the specified diagnostics. For example:

#pragma diag_error=Pe117


#pragma diag_remark #pragma diag_remark=tag,tag,...

Changes the severity level to remark for the specified diagnostics. For example:

#pragma diag_remark=Pe177


#pragma diag_suppress #pragma diag_suppress=tag,tag,...

Suppresses the diagnostic messages with the specified tags. For example:

#pragma diag_suppress=Pe117,Pe177


#pragma diag_warning #pragma diag_warning=tag,tag,...

Changes the severity level to warning for the specified diagnostics. For example:

#pragma diag_warning=Pe826


#pragma message #pragma message(string)

Makes the assembler print a message on stdout when the file is assembled. For example:

#ifdef TESTING#pragma message("Testing")#endif

ARX-2


DiagnosticsThis chapter describes the format of the diagnostic messages and explains how diagnostic messages are divided into different levels of severity.

Message formatAll diagnostic messages are issued as complete, self-explanatory messages. A typical diagnostic message from the assembler is produced in the form:

filename,linenumber level[tag]: message

where filename is the name of the source file in which the error was encountered; linenumber is the line number at which the assembler detected the error; level is the level of seriousness of the diagnostic; tag is a unique tag that identifies the diagnostic message; message is a self-explanatory message, possibly several lines long.

Diagnostic messages are displayed on the screen, and printed in the optional list file. In the IAR Embedded Workbench IDE, diagnostic messages are displayed in the Build messages window.

Severity levelsThe diagnostics are divided into different levels of severity:

Remark

A diagnostic message that is produced when the assembler finds a source code construct that can possibly lead to erroneous behavior in the generated code. Remarks are, by default, not issued but can be enabled, see --remarks, page 32.

Warning

A diagnostic message that is produced when the assembler finds a programming error or omission which is of concern but not so severe as to prevent the completion of compilation. Warnings can be disabled with the command line option --no_warnings, see --no_warnings, page 30.

Error

A diagnostic message that is produced when the assembler finds a construct which clearly violates the language rules, such that code cannot be produced. An error produces a non-zero exit code.

ARX-2

107

108

Severity levels

Fatal error

A diagnostic message that is produced when the assembler finds a condition that not only prevents code generation, but which makes further processing of the source code pointless. After the diagnostic is issued, assembly ends. A fatal error produces a non-zero exit code.

SETTING THE SEVERITY LEVEL

The diagnostic messages can be suppressed or the severity level can be changed for all types of diagnostics except for fatal errors and some of the regular errors.

See Summary of assembler options, page 16, for a description of the assembler options that are available for setting severity levels.

See the chapter Pragma directives, for a description of the pragma directives that are available for setting severity levels.

INTERNAL ERROR

An internal error is a diagnostic message that signals that there was a serious and unexpected failure due to a fault in the assembler. It is produced using this form:

Internal error: message

where message is an explanatory message. If internal errors occur, they should be reported to your software distributor or IAR Systems Technical Support. Please include information enough to reproduce the problem. This would typically include:

● The product name

● The version number of the assembler, which can be seen in the header of the list files generated by the assembler

● Your license number

● The exact internal error message text

● The source file of the program that generated the internal error

● A list of the options that were used when the internal error occurred.

ARX-2


Index

Aabsolute expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12ADD (CFI operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101address field, in assembler list file . . . . . . . . . . . . . . . . . . . 13ALIGN (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . 61alignment error, possible reason for . . . . . . . . . . . . . . . . . . 60alignment, of sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62ALIGNRAM (assembler directive). . . . . . . . . . . . . . . . . . . 61AND (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . 40AND (CFI operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101architecture, RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi_args (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . 69_args (predefined macro symbol) . . . . . . . . . . . . . . . . . . . . 72ASCII character constants. . . . . . . . . . . . . . . . . . . . . . . . . . . 7asm (filename extension) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3ASMRX (environment variable) . . . . . . . . . . . . . . . . . . . . . . 4assembler control directives . . . . . . . . . . . . . . . . . . . . . . . . 89assembler diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107assembler directives

assembler control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89call frame information (CFI) . . . . . . . . . . . . . . . . . . . . . 91conditional assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

See also C-style preprocessor directivesC-style preprocessor . . . . . . . . . . . . . . . . . . . . . . . . . . . 81data definition or allocation . . . . . . . . . . . . . . . . . . . . . . 86list file control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76macro processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69module control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55section control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51symbol control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57value assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64#pragma . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

assembler environment variables . . . . . . . . . . . . . . . . . . . . . 4assembler expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6assembler instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5assembler invocation syntax . . . . . . . . . . . . . . . . . . . . . . . . . 3

assembler labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9format of . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

assembler list filesaddress field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13comments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89conditional code and strings. . . . . . . . . . . . . . . . . . . . . . 77cross-references

generating (LSTXRF) . . . . . . . . . . . . . . . . . . . . . . . . 78generating (-l) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

data field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13enabling and disabling (LSTOUT). . . . . . . . . . . . . . . . . 77filename, specifying (-l) . . . . . . . . . . . . . . . . . . . . . . . . . 27generated lines, controlling (LSTREP) . . . . . . . . . . . . . 78macro-generated lines, controlling . . . . . . . . . . . . . . . . . 77symbol and cross-reference table . . . . . . . . . . . . . . . . . . 13

assembler macrosarguments, passing to. . . . . . . . . . . . . . . . . . . . . . . . . . . 72defining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70generated lines, controlling in list file . . . . . . . . . . . . . . 77inline routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73predefined symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73quote characters, specifying . . . . . . . . . . . . . . . . . . . . . . 28special characters, using. . . . . . . . . . . . . . . . . . . . . . . . . 71

assembler operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35in expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

assembler optionspassing to assembler . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3specifying parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 16summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

assembler output, including debug information . . . . . . . . . 20assembler source files, including . . . . . . . . . . . . . . . . . . . . 83assembler source format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5assembler subversion number . . . . . . . . . . . . . . . . . . . . . . . 10assembler symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

exporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58importing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Index

ARX-2

109

110

in relocatable expressions . . . . . . . . . . . . . . . . . . . . . . . 12predefined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9redefining. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

assembling, invocation syntax. . . . . . . . . . . . . . . . . . . . . . . . 3assembly messages format . . . . . . . . . . . . . . . . . . . . . . . . 107ASSIGN (assembler directive) . . . . . . . . . . . . . . . . . . . . . . 64assumptions (programming experience) . . . . . . . . . . . . . . . xi

Bbacktrace information, defining . . . . . . . . . . . . . . . . . . . . . 91__BIG_ENDIAN__ (predefined symbol) . . . . . . . . . . . . . . 10BINAND (assembler operator) . . . . . . . . . . . . . . . . . . . . . . 40BINNOT (assembler operator) . . . . . . . . . . . . . . . . . . . . . . 40BINOR (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . 40BINXOR (assembler operator) . . . . . . . . . . . . . . . . . . . . . . 41bold style, in this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii__BUILD_NUMBER__ (predefined symbol) . . . . . . . . . . 10byte order

identifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10specifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

BYTE1 (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . 41BYTE2 (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . 41BYTE3 (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . 41BYTE4 (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . 42

Ccall frame information directives . . . . . . . . . . . . . . . . . . . . 91case sensitivity, controlling . . . . . . . . . . . . . . . . . . . . . . 18, 90CASEOFF (assembler directive). . . . . . . . . . . . . . . . . . . . . 89CASEON (assembler directive) . . . . . . . . . . . . . . . . . . . . . 89--case_insensitive (assembler option) . . . . . . . . . . . . . . . . . 18CFI directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91CFI expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100CFI operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101character constants, ASCII . . . . . . . . . . . . . . . . . . . . . . . . . . 7CODE (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . 59COL (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . 77

command line optionspart of invocation syntax . . . . . . . . . . . . . . . . . . . . . . . . . 3passing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3typographic convention . . . . . . . . . . . . . . . . . . . . . . . . xiii

command line, extending . . . . . . . . . . . . . . . . . . . . . . . . . . 25command prompt icon, in this guide . . . . . . . . . . . . . . . . . xiiicomments

in assembler list file . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89in assembler source code . . . . . . . . . . . . . . . . . . . . . . . . . 5multi-line, using with assembler directives . . . . . . . . . . 90

comments, in C-style preprocessor directives . . . . . . . . . . . 84COMPLEMENT (CFI operator) . . . . . . . . . . . . . . . . . . . . 101computer style, typographic convention . . . . . . . . . . . . . . xiiiconditional assembly directives . . . . . . . . . . . . . . . . . . . . . 66

See also C-style preprocessor directivesconditional code and strings, listing . . . . . . . . . . . . . . . . . . 77constants

default base of . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89integer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

conventions, used in this guide . . . . . . . . . . . . . . . . . . . . . . xiicopyright notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ii, ii__CORE__ (predefined symbol). . . . . . . . . . . . . . . . . . . . . 10--core (assembler option) . . . . . . . . . . . . . . . . . . . . . . . . . . 19core, identifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10CRC, in assembler list file . . . . . . . . . . . . . . . . . . . . . . . . . 13cross-references, in assembler list file

generating (LSTXRF) . . . . . . . . . . . . . . . . . . . . . . . . . . 78generating (-l) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

C-style preprocessor directives . . . . . . . . . . . . . . . . . . . . . . 81C++ terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

D-D (assembler option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19data allocation directives. . . . . . . . . . . . . . . . . . . . . . . . . . . 86data definition directives . . . . . . . . . . . . . . . . . . . . . . . . . . . 86data field, in assembler list file . . . . . . . . . . . . . . . . . . . . . . 13--data_model (assembler option). . . . . . . . . . . . . . . . . . . . . 20DATA (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . 59

ARX-2


Index

__DATA_MODEL__ (predefined symbol) . . . . . . . . . . . . . 10DATA8 (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . 59DATA16 (assembler directive) . . . . . . . . . . . . . . . . . . . . . . 59DATA32 (assembler directive) . . . . . . . . . . . . . . . . . . . . . . 59DATA64 (assembler directive) . . . . . . . . . . . . . . . . . . . . . . 59__DATE__ (predefined symbol) . . . . . . . . . . . . . . . . . . . . . 10DATE (assembler operator). . . . . . . . . . . . . . . . . . . . . . . . . 42DC8 (assembler directive). . . . . . . . . . . . . . . . . . . . . . . . . . 86DC16 (assembler directive). . . . . . . . . . . . . . . . . . . . . . . . . 86DC24 (assembler directive). . . . . . . . . . . . . . . . . . . . . . . . . 86DC32 (assembler directive). . . . . . . . . . . . . . . . . . . . . . . . . 86DC64 (assembler directive). . . . . . . . . . . . . . . . . . . . . . . . . 86--debug (assembler option) . . . . . . . . . . . . . . . . . . . . . . . . . 20--no_fragments (assembler option) . . . . . . . . . . . . . . . . . . . 29debug information, including in assembler output . . . . . . . 20default base, for constants . . . . . . . . . . . . . . . . . . . . . . . . . . 89#define (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . 81DEFINE (assembler directive) . . . . . . . . . . . . . . . . . . . . . . 64--dependencies (assembler option) . . . . . . . . . . . . . . . . . . . 20DF32 (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . 86DF64 (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . 86diagnostic messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

classifying as errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21classifying as remarks . . . . . . . . . . . . . . . . . . . . . . . . . . 22classifying as warnings . . . . . . . . . . . . . . . . . . . . . . . . . 23disabling warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30disabling wrapping of . . . . . . . . . . . . . . . . . . . . . . . . . . 30enabling remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32listing all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23suppressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

--diagnostics_tables (assembler option) . . . . . . . . . . . . . . . 23diag_default (#pragma directive) . . . . . . . . . . . . . . . . . . . 105--diag_error (assembler option). . . . . . . . . . . . . . . . . . . . . . 21diag_error (#pragma directive) . . . . . . . . . . . . . . . . . . . . . 106--diag_remark (assembler option) . . . . . . . . . . . . . . . . . . . . 22diag_remark (#pragma directive) . . . . . . . . . . . . . . . . . . . 106--diag_suppress (assembler option). . . . . . . . . . . . . . . . . . . 22diag_suppress (#pragma directive) . . . . . . . . . . . . . . . . . . 106--diag_warning (assembler option) . . . . . . . . . . . . . . . . . . . 23

diag_warning (#pragma directive) . . . . . . . . . . . . . . . . . . 106directives. See assembler directives--dir_first (assembler option) . . . . . . . . . . . . . . . . . . . . . . . 24disassembly mode, directives . . . . . . . . . . . . . . . . . . . . . . . 59disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ii, iiDIV (CFI operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101document conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii__DOUBLE__ (predefined symbol) . . . . . . . . . . . . . . . . . . 10--double (assembler option) . . . . . . . . . . . . . . . . . . . . . . . . 24DQ15 (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . 86DQ31 (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . 86DS8 (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . . 86DS16 (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . 86DS24 (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . 86DS32 (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . 86DS64 (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . 86

Eedition, of this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iiefficient coding techniques . . . . . . . . . . . . . . . . . . . . . . . . . 14#elif (assembler directive). . . . . . . . . . . . . . . . . . . . . . . . . . 81#else (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . 81ELSE (assembler directive). . . . . . . . . . . . . . . . . . . . . . . . . 66ELSEIF (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . 67--enable_multibytes (assembler option) . . . . . . . . . . . . . . . 24END (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . 55--endian (assembler option) . . . . . . . . . . . . . . . . . . . . . . . . 25#endif (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . 81ENDIF (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . 67ENDM (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . 69ENDR (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . 69environment variables

ASMRX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4assembler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4IASMRX_INC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

EQ (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . 42EQ (CFI operator). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101EQU (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . 64

ARX-2

111

112

#error (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . 81error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

classifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21#error, using to display. . . . . . . . . . . . . . . . . . . . . . . . . . 84

--error_limit (assembler option) . . . . . . . . . . . . . . . . . . . . . 25EVEN (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . 61EXITM (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . 69experience, programming . . . . . . . . . . . . . . . . . . . . . . . . . . xiexpressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6extended command line file (extend.xcl). . . . . . . . . . . . . . . 25EXTERN (assembler directive). . . . . . . . . . . . . . . . . . . . . . 57

F-f (assembler option). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25false value, in assembler expressions . . . . . . . . . . . . . . . . . . 8fatal error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108__FILE__ (predefined symbol). . . . . . . . . . . . . . . . . . . . . . 10file dependencies, tracking . . . . . . . . . . . . . . . . . . . . . . . . . 20file extensions. See filename extensionsfile types

assembler output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3assembler source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3extended command line . . . . . . . . . . . . . . . . . . . . . . . . . 25#include, specifying path . . . . . . . . . . . . . . . . . . . . . . . . 26

filename extensionsasm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3msa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3o. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3xcl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

filenames, specifying for assembler object file . . . . . . . . . . 31floating-point constants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7formats

assembler source code . . . . . . . . . . . . . . . . . . . . . . . . . . . 5diagnostic messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 107in list files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

fractions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8FRAME (CFI operator). . . . . . . . . . . . . . . . . . . . . . . . . . . 102

GGE (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . 43GE (CFI operator). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101global value, defining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65GT (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . 43GT (CFI operator). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

H--header_context (assembler option) . . . . . . . . . . . . . . . . . . 26HIGH (assembler operator). . . . . . . . . . . . . . . . . . . . . . . . . 43HWRD (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . 43

I-I (assembler option). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26IAR Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . 108__ IAR_SYSTEMS_ASM__ (predefined symbol) . . . . . . . 10__IASMRX__ (predefined symbol) . . . . . . . . . . . . . . . . . . 10IASMRX_INC (environment variable) . . . . . . . . . . . . . . . . . 4icons, in this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii#if (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . . . 81IF (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . . . 67IF (CFI operator). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102#ifdef (assembler directive). . . . . . . . . . . . . . . . . . . . . . . . . 81#ifndef (assembler directive). . . . . . . . . . . . . . . . . . . . . . . . 81IMPORT (assembler directive) . . . . . . . . . . . . . . . . . . . . . . 57#include files, specifying . . . . . . . . . . . . . . . . . . . . . . . . . . 26#include (assembler directive) . . . . . . . . . . . . . . . . . . . . . . 81include paths, specifying. . . . . . . . . . . . . . . . . . . . . . . . . . . 26inline coding, using macros . . . . . . . . . . . . . . . . . . . . . . . . 73installation directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiinstruction set, RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi--int (assembler option). . . . . . . . . . . . . . . . . . . . . . . . . . . . 27integer constants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6internal error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108__INTSIZE__ (predefined symbol) . . . . . . . . . . . . . . . . . . 10invocation syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

ARX-2


Index

italic style, in this guide . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

L-l (assembler option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27labels. See assembler labelsLE (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . 43LE (CFI operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101LIBRARY (assembler directive) . . . . . . . . . . . . . . . . . . . . . 54lightbulb icon, in this guide. . . . . . . . . . . . . . . . . . . . . . . . xiii__LINE__ (predefined symbol) . . . . . . . . . . . . . . . . . . . . . 10#line (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . 81list file format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

body. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13CRC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13symbol and cross reference

list filescontrol directives for . . . . . . . . . . . . . . . . . . . . . . . . . . . 76generating (-l) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

LITERAL (CFI operator) . . . . . . . . . . . . . . . . . . . . . . . . . 101__LITTLE_ENDIAN__ (predefined symbol) . . . . . . . . . . . 10LOAD (CFI operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102local value, defining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65LOCAL (assembler directive). . . . . . . . . . . . . . . . . . . . . . . 69LOW (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . 44LSHIFT (CFI operator). . . . . . . . . . . . . . . . . . . . . . . . . . . 101LSTCND (assembler directive). . . . . . . . . . . . . . . . . . . . . . 76LSTCOD (assembler directive). . . . . . . . . . . . . . . . . . . . . . 76LSTEXP (assembler directives) . . . . . . . . . . . . . . . . . . . . . 76LSTMAC (assembler directive) . . . . . . . . . . . . . . . . . . . . . 76LSTOUT (assembler directive) . . . . . . . . . . . . . . . . . . . . . . 76LSTPAGE (assembler directive) . . . . . . . . . . . . . . . . . . . . . 77LSTREP (assembler directive) . . . . . . . . . . . . . . . . . . . . . . 76LSTXRF (assembler directive) . . . . . . . . . . . . . . . . . . . . . . 76LT (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . 44LT (CFI operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101LWRD (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . 44

M-M (assembler option). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28macro processing directives . . . . . . . . . . . . . . . . . . . . . . . . 69macro quote characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

specifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28MACRO (assembler directive) . . . . . . . . . . . . . . . . . . . . . . 69macros. See assembler macrosmemory space, reserving and initializing . . . . . . . . . . . . . . 87memory, reserving space in. . . . . . . . . . . . . . . . . . . . . . . . . 86message (#pragma directive). . . . . . . . . . . . . . . . . . . . . . . 106messages, excluding from standard output stream . . . . . . . 33--mnem_first (assembler option) . . . . . . . . . . . . . . . . . . . . . 29MOD (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . 44MOD (CFI operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101mode control directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59module consistency. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56module control directives . . . . . . . . . . . . . . . . . . . . . . . . . . 55modules, beginning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55msa (filename extension) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3MUL (CFI operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101multibyte character support. . . . . . . . . . . . . . . . . . . . . . . . . 24

NNAME (assembler directive). . . . . . . . . . . . . . . . . . . . . . . . 55naming conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiNE (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . 45NE (CFI operator). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101NOT (assembler operator). . . . . . . . . . . . . . . . . . . . . . . . . . 45NOT (CFI operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101--no_path_in_file_macros (assembler option). . . . . . . . . . . 29--no_system_include (assembler option). . . . . . . . . . . . . . . 29--no_warnings (assembler option). . . . . . . . . . . . . . . . . . . . 30--no_wrap_diagnostics (assembler option) . . . . . . . . . . . . . 30

O-o (assembler option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

ARX-2

113

114

o (filename extension). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3ODD (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . 61--only_stdout (assembler option) . . . . . . . . . . . . . . . . . . . . 30operands

format of . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5in assembler expressions . . . . . . . . . . . . . . . . . . . . . . . . . 6

operations, format of. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5operation, silent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33operators. See assembler operatorsoption summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16OR (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . 45OR (CFI operator). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101--output (assembler option). . . . . . . . . . . . . . . . . . . . . . . . . 30OVERLAY (assembler directive) . . . . . . . . . . . . . . . . . . . . 57

PPAGE (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . 77PAGSIZ (assembler directive). . . . . . . . . . . . . . . . . . . . . . . 77parameters

specifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16typographic convention . . . . . . . . . . . . . . . . . . . . . . . . xiii

part number, of this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . ii#pragma (assembler directive) . . . . . . . . . . . . . . . . . . 81, 105precedence, of assembler operators. . . . . . . . . . . . . . . . . . . 35predefined register symbols . . . . . . . . . . . . . . . . . . . . . . . . . 9predefined symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

in assembler macros. . . . . . . . . . . . . . . . . . . . . . . . . . . . 72--predef_macros (assembler option) . . . . . . . . . . . . . . . . . . 31--preinclude (assembler option) . . . . . . . . . . . . . . . . . . . . . 31--preprocess (assembler option) . . . . . . . . . . . . . . . . . . . . . 32preprocessor symbols

defining and undefining . . . . . . . . . . . . . . . . . . . . . . . . . 82defining on command line . . . . . . . . . . . . . . . . . . . . . . . 19

prerequisites (programming experience) . . . . . . . . . . . . . . . xiprogram location counter (PLC) . . . . . . . . . . . . . . . . . . . . . . 9PROGRAM (assembler directive). . . . . . . . . . . . . . . . . . . . 55programming experience, required . . . . . . . . . . . . . . . . . . . xiprogramming hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

PUBLIC (assembler directive) . . . . . . . . . . . . . . . . . . . . . . 57publication date, of this guide . . . . . . . . . . . . . . . . . . . . . . . . iiPUBWEAK (assembler directive). . . . . . . . . . . . . . . . . . . . 57

R-r (assembler option). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18RADIX (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . 89reference information, typographic convention. . . . . . . . . xiiiregistered trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . .ii, iiregisters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9relocatable expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12remark (diagnostic message). . . . . . . . . . . . . . . . . . . . . . . 107

classifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22enabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

--remarks (assembler option) . . . . . . . . . . . . . . . . . . . . . . . 32repeating statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73REPT (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . 69REPTC (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . 69REPTI (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . 69REQUIRE (assembler directive) . . . . . . . . . . . . . . . . . . . . . 57RSEG (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . 61RSHIFTA (CFI operator) . . . . . . . . . . . . . . . . . . . . . . . . . 101RSHIFTL (CFI operator) . . . . . . . . . . . . . . . . . . . . . . . . . 102RTMODEL (assembler directive) . . . . . . . . . . . . . . . . . . . . 55rules, in CFI directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98runtime model attributes, declaring. . . . . . . . . . . . . . . . . . . 56RX architecture and instruction set . . . . . . . . . . . . . . . . . . . xi

Ss (filename extension) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3section control directives . . . . . . . . . . . . . . . . . . . . . . . . . . 61SECTION (assembler directive) . . . . . . . . . . . . . . . . . . . . . 61sections

aligning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62beginning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

SECTION_TYPE (assembler directive) . . . . . . . . . . . . . . . 61SET (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . . 64

ARX-2


Index

severity level, of diagnostic messages . . . . . . . . . . . . . . . . 107specifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

SFB (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . 45SFE (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . 46SHL (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . 47SHR (assembler operator). . . . . . . . . . . . . . . . . . . . . . . . . . 47--silent (assembler option) . . . . . . . . . . . . . . . . . . . . . . . . . 33silent operation, specifying . . . . . . . . . . . . . . . . . . . . . . . . . 33simple rules, in CFI directives. . . . . . . . . . . . . . . . . . . . . . . 98SIZEOF (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . 47source files

including . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83list all referred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

source format, assembler . . . . . . . . . . . . . . . . . . . . . . . . . . . 5source line numbers, changing . . . . . . . . . . . . . . . . . . . . . . 84standard error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30standard output stream, disabling messages to . . . . . . . . . . 33standard output, specifying . . . . . . . . . . . . . . . . . . . . . . . . . 30statements, repeating. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73stderr, messages to . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30stdout, direct messages to . . . . . . . . . . . . . . . . . . . . . . . . . . 30SUB (CFI operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102__SUBVERSION__ (predefined symbol). . . . . . . . . . . . . . 10Support, Technical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108symbol and cross-reference table, in assembler list file. . . . 13

See also Include cross-referencesymbol control directives . . . . . . . . . . . . . . . . . . . . . . . . . . 57symbols

See also assembler symbolsexporting to other modules. . . . . . . . . . . . . . . . . . . . . . . 58predefined, in assembler . . . . . . . . . . . . . . . . . . . . . . . . . 9predefined, in assembler macro . . . . . . . . . . . . . . . . . . . 72user-defined, case sensitive . . . . . . . . . . . . . . . . . . . . . . 18

--system_include_dir (assembler option) . . . . . . . . . . . . . . 33

TTechnical Support, IAR . . . . . . . . . . . . . . . . . . . . . . . . . . 108temporary values, defining . . . . . . . . . . . . . . . . . . . . . . . . . 65

terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii__TIME__ (predefined symbol) . . . . . . . . . . . . . . . . . . . . . 10time-critical code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73tools icon, in this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiitrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ii, iitrue value, in assembler expressions . . . . . . . . . . . . . . . . . . . 8typographic conventions . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

UUGT (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . 48ULT (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . 48UMINUS (CFI operator). . . . . . . . . . . . . . . . . . . . . . . . . . 101#undef (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . 81UPPER (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . 48user symbols, case sensitive . . . . . . . . . . . . . . . . . . . . . . . . 18

Vvalue assignment directives. . . . . . . . . . . . . . . . . . . . . . . . . 64values, defining. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86VAR (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . 64__VER__ (predefined symbol) . . . . . . . . . . . . . . . . . . . . . . 11version

assembler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10IAR Embedded Workbench . . . . . . . . . . . . . . . . . . . . . . . ii

Wwarnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

classifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23disabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30exit code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33treating as errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

warnings icon, in this guide . . . . . . . . . . . . . . . . . . . . . . . xiii--warnings_affect_exit_code (assembler option). . . . . . . 4, 33--warnings_are_errors (assembler option). . . . . . . . . . . . . . 33

ARX-2

115

116

Xxcl (filename extension) . . . . . . . . . . . . . . . . . . . . . . . . . . . 25XOR (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . 49XOR (CFI operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Symbols^ (assembler operator). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41_args (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . 69_args (predefined macro symbol) . . . . . . . . . . . . . . . . . . . . 72__BIG_ENDIAN__ (predefined symbol) . . . . . . . . . . . . . . 10__BUILD_NUMBER__ (predefined symbol) . . . . . . . . . . 10__CORE__ (predefined symbol). . . . . . . . . . . . . . . . . . . . . 10__DATA_MODEL__ (predefined symbol) . . . . . . . . . . . . . 10__DATE__ (predefined symbol) . . . . . . . . . . . . . . . . . . . . . 10__DOUBLE__ (predefined symbol) . . . . . . . . . . . . . . . . . . 10__FILE__ (predefined symbol). . . . . . . . . . . . . . . . . . . . . . 10__IAR_SYSTEMS_ASM__ (predefined symbol) . . . . . . . 10__IASMRX__ (predefined symbol) . . . . . . . . . . . . . . . . . . 10__INTSIZE__ (predefined symbol) . . . . . . . . . . . . . . . . . . 10__LINE__ (predefined symbol) . . . . . . . . . . . . . . . . . . . . . 10__LITTLE_ENDIAN__ (predefined symbol) . . . . . . . . . . . 10__SUBVERSION__ (predefined symbol). . . . . . . . . . . . . . 10__TIME__ (predefined symbol) . . . . . . . . . . . . . . . . . . . . . 10__VER__ (predefined symbol) . . . . . . . . . . . . . . . . . . . . . . 11- (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39-D (assembler option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-f (assembler option). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-I (assembler option). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-l (assembler option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-M (assembler option). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-o (assembler option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-r (assembler option). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18--case_insensitive (assembler option) . . . . . . . . . . . . . . . . . 18--core (assembler option) . . . . . . . . . . . . . . . . . . . . . . . . . . 19--data_model (assembler option). . . . . . . . . . . . . . . . . . . . . 20--debug (assembler option) . . . . . . . . . . . . . . . . . . . . . . . . . 20--dependencies (assembler option) . . . . . . . . . . . . . . . . . . . 20

--diagnostics_tables (assembler option) . . . . . . . . . . . . . . . 23--diag_error (assembler option). . . . . . . . . . . . . . . . . . . . . . 21--diag_remark (assembler option) . . . . . . . . . . . . . . . . . . . . 22--diag_suppress (assembler option). . . . . . . . . . . . . . . . . . . 22--diag_warning (assembler option) . . . . . . . . . . . . . . . . . . . 23--dir_first (assembler option) . . . . . . . . . . . . . . . . . . . . . . . 24--double (assembler option) . . . . . . . . . . . . . . . . . . . . . . . . 24--enable_multibytes (assembler option) . . . . . . . . . . . . . . . 24--endian (assembler option) . . . . . . . . . . . . . . . . . . . . . . . . 25--error_limit (assembler option) . . . . . . . . . . . . . . . . . . . . . 25--header_context (assembler option) . . . . . . . . . . . . . . . . . . 26--int (assembler option). . . . . . . . . . . . . . . . . . . . . . . . . . . . 27--mnem_first (assembler option) . . . . . . . . . . . . . . . . . . . . . 29--no_fragments (assembler option) . . . . . . . . . . . . . . . . . . . 29--no_path_in_file_macros (assembler option). . . . . . . . . . . 29--no_system_include (assembler option). . . . . . . . . . . . . . . 29--no_warnings (assembler option). . . . . . . . . . . . . . . . . . . . 30--no_wrap_diagnostics (assembler option) . . . . . . . . . . . . . 30--only_stdout (assembler option) . . . . . . . . . . . . . . . . . . . . 30--output (assembler option). . . . . . . . . . . . . . . . . . . . . . . . . 30--predef_macros (assembler option) . . . . . . . . . . . . . . . . . . 31--preinclude (assembler option) . . . . . . . . . . . . . . . . . . . . . 31--preprocess (assembler option) . . . . . . . . . . . . . . . . . . . . . 32--remarks (assembler option) . . . . . . . . . . . . . . . . . . . . . . . 32--silent (assembler option) . . . . . . . . . . . . . . . . . . . . . . . . . 33--system_include_dir (assembler option) . . . . . . . . . . . . . . 33--warnings_affect_exit_code (assembler option). . . . . . . 4, 33--warnings_are_errors (assembler option). . . . . . . . . . . . . . 33! (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45!= (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45?: (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39() (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38* (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38/ (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39/*...*/ (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . 89// (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89& (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40&& (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . 40#define (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . 81

ARX-2


Index

#elif (assembler directive). . . . . . . . . . . . . . . . . . . . . . . . . . 81#else (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . 81#endif (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . 81#error (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . 81#if (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . . . 81#ifdef (assembler directive). . . . . . . . . . . . . . . . . . . . . . . . . 81#ifndef (assembler directive). . . . . . . . . . . . . . . . . . . . . . . . 81#include files, specifying . . . . . . . . . . . . . . . . . . . . . . . . . . 26#include (assembler directive) . . . . . . . . . . . . . . . . . . . . . . 81#line (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . 81#pragma (assembler directive) . . . . . . . . . . . . . . . . . . 81, 105#undef (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . 81% (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44+ (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38< (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44<< (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . 47<= (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . 43<> (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . 45= (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64= (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42== (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . 42> (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43>= (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . 43>> (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . 47| (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40|| (assembler operator). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45~ (assembler operator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40$ (program location counter). . . . . . . . . . . . . . . . . . . . . . . . . 9

ARX-2

117

iar assemblernetstorage.iar.com/.../007248/ew/doc/ewrx_assemblerguide.enu.pdf · assembler...

Documents