Skip to main content

IAR Embedded Workbench for RISC-V 3.40

Module control directives

In this section:
Syntax

END

RTMODEL key , value

Parameters

key

A text string specifying the key.

value

A text string specifying the value.

Description

Module control directives are used for marking the end of source program modules, and for enforcing consistency between them. For information about the restrictions that apply when using a directive in an expression, see Expression restrictions.

Directive

Description

Expression restrictions

END

Ends the assembly of the module in a file.

Only locally defined labels or integer constants

RTMODEL

Declares runtime model attributes.

Not applicable

Table 123. Module control directives  


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 Runtime model attributes.

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

Assembler source file f2.s:

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

Assembler source file f3.s:

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