IAR C/C++ Compiler

User Guide

for the Texas Instruments

MSP430 Microcontroller Family

C430-14
 COPYRIGHT NOTICE
© 1996–2021 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.

DISCLAIMER
The 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.

TRADEMARKS
IAR Systems, IAR Embedded Workbench, Embedded Trust, C-Trust, IAR Connect,
C-SPY, C-RUN, C-STAT, IAR Visual State, IAR KickStart Kit, I-jet, I-jet Trace,
I-scope, IAR Academy, IAR, and the logotype of IAR Systems are trademarks or
registered trademarks owned by IAR Systems AB.
Microsoft and Windows are registered trademarks of Microsoft Corporation.
Texas Instruments is a registered trademark of Texas Instruments Corporation. MSP430
is a trademark of Texas Instruments 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
Fourteenth edition: March 2021
Part number: C430-14
This guide applies to version 7.x of IAR Embedded Workbench® for the Texas
Instruments MSP430 microcontroller family.
Internal reference: M23, Mym8.5, docsrc-6.10, V_140324, INIT

IAR C/C++ Compiler User Guide

2 for MSP430

AFE1_AFE2-1:1
Brief contents
Tables ..................................................................................................................... 27

Preface .................................................................................................................... 29

Part 1. Using the compiler ....................................................... 37

Introduction to the IAR build tools ........................................................ 39

Developing embedded applications ........................................................ 45

Data storage ...................................................................................................... 59

Functions ............................................................................................................... 71

Linking overview ............................................................................................. 85

Linking your application .............................................................................. 101

The DLIB runtime environment ........................................................... 115

The CLIB runtime environment ............................................................ 161

Assembler language interface ................................................................. 169

Using C ................................................................................................................ 197

Using C++ .......................................................................................................... 205

Application-related considerations ....................................................... 221

Efficient coding for embedded applications ...................................... 233

Part 2. Reference information ........................................... 253

External interface details ............................................................................ 255

Compiler options ........................................................................................... 263

Data representation ...................................................................................... 303

Extended keywords ...................................................................................... 317

AFE1_AFE2-1:1
 Pragma directives ........................................................................................... 331

Intrinsic functions ........................................................................................... 355

The preprocessor .......................................................................................... 369

C/C++ standard library functions .......................................................... 377

Segment reference ......................................................................................... 387

The stack usage control file ...................................................................... 405

Implementation-defined behavior for Standard C ........................ 413

Implementation-defined behavior for C89 ....................................... 429

Index ..................................................................................................................... 443

IAR C/C++ Compiler User Guide

4 for MSP430

AFE1_AFE2-1:1
Contents
Tables ..................................................................................................................... 27

Preface .................................................................................................................... 29
Who should read this guide ............................................................... 29
Required knowledge .......................................................................... 29
How to use this guide .......................................................................... 29
What this guide contains ................................................................... 30
Part 1. Using the compiler .................................................................. 30
Part 2. Reference information ............................................................ 31
Other documentation ........................................................................... 31
User and reference guides .................................................................. 32
The online help system ...................................................................... 32
Further reading ................................................................................... 33
Web sites ............................................................................................ 33
Document conventions ........................................................................ 33
Typographic conventions ................................................................... 34
Naming conventions .......................................................................... 35

Part 1. Using the compiler ....................................................... 37

Introduction to the IAR build tools ........................................................ 39

The IAR build tools—an overview ................................................... 39

The IAR C/C++ Compiler .................................................................. 39
The IAR Assembler ........................................................................... 39
The IAR XLINK Linker .................................................................... 40
External tools ..................................................................................... 40
IAR language overview ......................................................................... 40
Device support ......................................................................................... 41
Supported MSP430 devices ............................................................... 41
Preconfigured support files ................................................................ 41
Examples for getting started .............................................................. 42

AFE1_AFE2-1:1
 Special support for embedded systems ........................................ 42
Extended keywords ............................................................................ 42
Pragma directives ............................................................................... 43
Predefined symbols ............................................................................ 43
Accessing low-level features ............................................................. 43

Developing embedded applications ........................................................ 45

Developing embedded software using IAR build tools .......... 45

CPU features and constraints ............................................................. 45
Mapping of memory ........................................................................... 45
Communication with peripheral units ................................................ 46
Event handling ................................................................................... 46
System startup .................................................................................... 46
Real-time operating systems .............................................................. 47
The build process—an overview ...................................................... 47
The translation process ....................................................................... 47
The linking process ............................................................................ 48
After linking ....................................................................................... 50
Application execution—an overview ............................................. 50
The initialization phase ...................................................................... 50
The execution phase ........................................................................... 53
The termination phase ........................................................................ 53
Building applications—an overview ................................................ 54
Basic project configuration ................................................................. 54
Processor configuration ...................................................................... 55
Data model (MSP430X only) ............................................................ 56
Code model (MSP430X only) ............................................................ 56
Size of double floating-point type ...................................................... 57
Optimization for speed and size ......................................................... 57
Normal or position-independent code ................................................ 57

Data storage ...................................................................................................... 59

Introduction ............................................................................................. 59
Different ways to store data ............................................................... 60

IAR C/C++ Compiler User Guide

6 for MSP430

AFE1_AFE2-1:1
 Contents

Memory types (MSP430X only) ...................................................... 60

Introduction to memory types ............................................................ 60
Using data memory attributes ............................................................ 61
Pointers and memory types ................................................................ 63
Structures and memory types ............................................................ 64
More examples ................................................................................... 64
C++ and memory types ..................................................................... 65
Data models .............................................................................................. 66
Specifying a data model ..................................................................... 66
Storage of auto variables and parameters .................................. 68
The stack ............................................................................................ 68
Dynamic memory on the heap ........................................................ 69
Potential problems .............................................................................. 70

Functions ............................................................................................................... 71

Function-related extensions .............................................................. 71

Code models (MSP430X only) ......................................................... 71
The Small code model ........................................................................ 72
The Large code model ........................................................................ 72
Comparing the code models ............................................................... 72
Primitives for interrupts, concurrency, and OS-related
programming ............................................................................................ 73
Interrupt functions ............................................................................. 73
Monitor functions ............................................................................... 76
Execution in RAM ................................................................................... 79
Position-independent code and read-only data ......................... 80
Drawbacks and limitations ................................................................. 80
Initialization of pointers ..................................................................... 81
Non-ROPI code in ROPI systems ...................................................... 81
Inlining functions ..................................................................................... 81
C versus C++ semantics ..................................................................... 82
Features controlling function inlining ................................................ 82

AFE1_AFE2-1:1
 Linking overview ............................................................................................. 85

Linking—an overview ............................................................................ 85

Segments and memory ........................................................................ 86
What is a segment? ............................................................................ 86
The linking process in detail .............................................................. 87
Placing code and data—the linker configuration file .............. 88
The contents of the linker configuration file ...................................... 89
Initialization at system startup ......................................................... 89
Static data memory segments ............................................................. 90
The initialization process ................................................................... 91
Stack usage analysis ............................................................................... 91
Introduction to stack usage analysis ................................................... 91
Performing a stack usage analysis ..................................................... 92
Result of an analysis—the map file contents ..................................... 93
Specifying additional stack usage information .................................. 95
Limitations ......................................................................................... 96
Situations where warnings are issued ................................................ 97
Call graph log ..................................................................................... 97

Linking your application .............................................................................. 101

Linking considerations ........................................................................ 101

Placing segments .............................................................................. 102
Placing data ...................................................................................... 104
Setting up stack memory .................................................................. 105
Setting up heap memory .................................................................. 106
Placing code ..................................................................................... 107
Keeping modules .............................................................................. 108
Keeping symbols and segments ....................................................... 109
Application startup ........................................................................... 109
Interaction between XLINK and your application ........................... 109
Producing other output formats than UBROF ................................. 110
Verifying the linked result of code and data placement ...... 110
Segment too long errors and range errors ........................................ 110
Linker map file ................................................................................. 110

IAR C/C++ Compiler User Guide

8 for MSP430

AFE1_AFE2-1:1
 Contents

Checking module consistency ......................................................... 111

Runtime model attributes ................................................................ 111
Using runtime model attributes ........................................................ 112
Predefined runtime attributes .......................................................... 113

The DLIB runtime environment ........................................................... 115

Introduction to the runtime environment ................................ 115

Runtime environment functionality ................................................. 115
Briefly about input and output (I/O) ................................................ 116
Briefly about C-SPY emulated I/O .................................................. 118
Briefly about retargeting .................................................................. 118
Setting up the runtime environment ........................................... 119
Setting up your runtime environment .............................................. 120
Retargeting—Adapting for your target system ............................... 122
Overriding library modules ............................................................. 123
Customizing and building your own runtime library ....................... 124
Additional information on the runtime environment .......... 126
Runtime library configurations ....................................................... 126
Prebuilt runtime libraries ................................................................. 127
Formatters for printf ......................................................................... 129
Formatters for scanf ........................................................................ 130
The C-SPY emulated I/O mechanism .............................................. 131
Math functions ................................................................................. 131
The Texas Instruments MathLib library .......................................... 134
System startup and termination ........................................................ 135
System initialization ......................................................................... 138
The DLIB low-level I/O interface .................................................... 139
abort ................................................................................................. 140
clock ................................................................................................. 140
__close ............................................................................................. 140
__exit ............................................................................................... 141
getenv ............................................................................................... 141
__getzone ......................................................................................... 142
__lseek ............................................................................................. 142

AFE1_AFE2-1:1
 __open .............................................................................................. 142
raise .................................................................................................. 143
__read .............................................................................................. 143
remove .............................................................................................. 144
rename .............................................................................................. 145
__ReportAssert ................................................................................ 145
signal ................................................................................................ 145
system ............................................................................................... 146
__time32, __time64 ......................................................................... 146
__write ............................................................................................. 146
Configuration symbols for printf and scanf ..................................... 148
Configuration symbols for file input and output .............................. 149
Locale ............................................................................................... 149
Strtod ................................................................................................ 151
Hardware multiplier support ............................................................ 151
MPU/IPE support ............................................................................. 152
Managing a multithreaded environment .................................... 154
Multithread support in the DLIB runtime environment ................... 154
Enabling multithread support ........................................................... 155
TLS in the linker configuration file ................................................. 160

The CLIB runtime environment ............................................................ 161

Using a prebuilt runtime library .................................................... 161

Choosing a runtime library .............................................................. 162
Runtime library filename syntax ...................................................... 162
Input and output ................................................................................... 162
Character-based I/O ......................................................................... 162
Formatters used by printf and sprintf ............................................... 163
Formatters used by scanf and sscanf ................................................ 164
System startup and termination .................................................... 165
System startup .................................................................................. 165
System termination .......................................................................... 166

IAR C/C++ Compiler User Guide

10 for MSP430

AFE1_AFE2-1:1
 Contents

Overriding default library modules .............................................. 166

Customizing system initialization ................................................. 166
C-SPY emulated I/O ........................................................................... 166
The debugger Terminal I/O window ................................................ 167
Termination ...................................................................................... 167
Hardware multiplier support .......................................................... 167
MPU/IPE support .................................................................................. 167
Assembler language interface ................................................................. 169

Mixing C and assembler ..................................................................... 169

Intrinsic functions ............................................................................ 169
Mixing C and assembler modules .................................................... 170
Inline assembler .............................................................................. 171
Reference information for inline assembler ..................................... 172
An example of how to use clobbered memory ................................ 177
Calling assembler routines from C ............................................... 178
Creating skeleton code ..................................................................... 178
Compiling the skeleton code ............................................................ 179
Calling assembler routines from C++ .......................................... 180
Calling convention ................................................................................ 181
Choosing a calling convention ......................................................... 182
Function declarations ...................................................................... 184
Using C linkage in C++ source code ............................................... 184
Preserved versus scratch registers ................................................... 184
Function entrance ............................................................................ 185
Function exit ................................................................................... 187
Restrictions for special function types ............................................. 188
Examples .......................................................................................... 188
Assembler instructions used for calling functions .................. 189
Normal (non-ROPI) code ................................................................. 189
Position-independent code and read-only data ................................ 190
Interrupt functions ............................................................................ 190
Module consistency .......................................................................... 191

11

AFE1_AFE2-1:1
 Memory access methods ................................................................... 191
The data16 memory access method ................................................. 192
The data20 memory access method ................................................. 192
Call frame information ....................................................................... 193
CFI directives ................................................................................... 193
Creating assembler source with CFI support ................................... 194

Using C ................................................................................................................ 197

C language overview ........................................................................... 197

Extensions overview ............................................................................ 198
Enabling language extensions .......................................................... 199
IAR C language extensions ............................................................... 199
Extensions for embedded systems programming ............................. 200
Relaxations to Standard C ................................................................ 202

Using C++ .......................................................................................................... 205

Overview—EC++ and EEC++ .......................................................... 205

Embedded C++ ................................................................................ 205
Extended Embedded C++ ................................................................ 206
Enabling support for C++ .................................................................. 207
EC++ feature descriptions ................................................................ 207
Using IAR attributes with classes .................................................... 207
Function types .................................................................................. 210
New and Delete operators ................................................................ 211
Using static class objects in interrupts ............................................. 212
Using New handlers ......................................................................... 213
Templates ........................................................................................ 213
Debug support in C-SPY .................................................................. 213
EEC++ feature description ............................................................... 214
Templates ......................................................................................... 214
Variants of cast operators ................................................................. 217
Mutable ............................................................................................ 218
Namespace ...................................................................................... 218
The STD namespace ........................................................................ 218

IAR C/C++ Compiler User Guide

12 for MSP430

AFE1_AFE2-1:1
 Contents

C++ language extensions ................................................................... 218

Application-related considerations ....................................................... 221

Stack considerations ........................................................................... 221

Stack size considerations ................................................................. 221
Heap considerations ............................................................................ 221
Heap segments in DLIB ................................................................... 222
Heap segments in CLIB .................................................................. 222
Heap size and standard I/O .............................................................. 222
Interaction between the tools and your application ............. 223
Checksum calculation for verifying image integrity .............. 224
Briefly about checksum calculation ................................................. 224
Calculating and verifying a checksum ............................................. 226
Troubleshooting checksum calculation ............................................ 231

Efficient coding for embedded applications ...................................... 233

Selecting data types ............................................................................. 233

Using efficient data types ................................................................. 233
Floating-point types ......................................................................... 233
Alignment of elements in a structure ............................................... 234
Anonymous structs and unions ........................................................ 235
Controlling data and function placement in memory .......... 236
Data placement at an absolute location ............................................ 237
Data and function placement in segments ....................................... 239
Controlling compiler optimizations ............................................. 240
Scope for performed optimizations .................................................. 240
Multi-file compilation units ............................................................. 241
Optimization levels .......................................................................... 242
Speed versus size ............................................................................. 242
Fine-tuning enabled transformations ............................................... 243
Facilitating good code generation ................................................. 245
Writing optimization-friendly source code ...................................... 246
Saving stack space and RAM memory ............................................ 246
Function prototypes .......................................................................... 247
Integer types and bit negation .......................................................... 248

13

AFE1_AFE2-1:1
 Protecting simultaneously accessed variables .................................. 248
Accessing special function registers ................................................ 249
Non-initialized variables .................................................................. 251
Efficient switch statements .............................................................. 252

Part 2. Reference information ........................................... 253

External interface details ............................................................................ 255

Invocation syntax ................................................................................. 255

Compiler invocation syntax ............................................................. 255
Passing options ................................................................................. 256
Environment variables ..................................................................... 256
Include file search procedure .......................................................... 256
Compiler output ................................................................................... 258
Error return codes ............................................................................. 258
Diagnostics .............................................................................................. 259
Message format ................................................................................ 259
Severity levels .................................................................................. 260
Setting the severity level .................................................................. 260
Internal error .................................................................................... 260

Compiler options ........................................................................................... 263

Options syntax ....................................................................................... 263

Types of options ............................................................................... 263
Rules for specifying parameters ....................................................... 263
Summary of compiler options ........................................................ 265
Descriptions of compiler options ................................................... 269
--c89 ................................................................................................. 269
--char_is_signed ............................................................................... 270
--char_is_unsigned ........................................................................... 270
--clib ................................................................................................. 270
--code_model ................................................................................... 270
--core ................................................................................................ 271
-D ..................................................................................................... 271

IAR C/C++ Compiler User Guide

14 for MSP430

AFE1_AFE2-1:1
 Contents

--data_model .................................................................................... 272

--debug, -r ......................................................................................... 272
--dependencies ................................................................................. 273
--diag_error ...................................................................................... 274
--diag_remark ................................................................................... 274
--diag_suppress ................................................................................ 275
--diag_warning ................................................................................. 275
--diagnostics_tables .......................................................................... 275
--discard_unused_publics ................................................................. 276
--dlib ................................................................................................. 276
--dlib_config ..................................................................................... 277
--double ............................................................................................ 277
-e ...................................................................................................... 278
--ec++ ............................................................................................... 278
--eec++ ............................................................................................. 279
--enable_multibytes .......................................................................... 279
--enable_restrict ............................................................................... 279
--error_limit ...................................................................................... 280
-f ....................................................................................................... 280
--guard_calls ..................................................................................... 280
--header_context ............................................................................... 281
--hw_workaround ............................................................................. 281
-I ....................................................................................................... 282
-l ....................................................................................................... 282
--library_module .............................................................................. 283
--lock_r4 ........................................................................................... 283
--lock_r5 ........................................................................................... 283
--macro_positions_in_diagnostics ................................................... 284
--mfc ................................................................................................. 284
--migration_preprocessor_extensions .............................................. 284
--module_name ................................................................................ 285
--multiplier ....................................................................................... 285
--no_call_frame_info ....................................................................... 286
--no_code_motion ............................................................................ 286

15

AFE1_AFE2-1:1
 --no_cse ............................................................................................ 286
--no_inline ........................................................................................ 287
--no_path_in_file_macros ................................................................ 287
--no_rw_dynamic_init ...................................................................... 287
--no_size_constraints ....................................................................... 288
--no_static_destruction ..................................................................... 288
--no_system_include ........................................................................ 288
--no_tbaa .......................................................................................... 289
--no_typedefs_in_diagnostics .......................................................... 289
--no_ubrof_messages ....................................................................... 290
--no_unroll ....................................................................................... 290
--no_warnings .................................................................................. 290
--no_wrap_diagnostics ..................................................................... 290
-O ..................................................................................................... 291
--omit_types ..................................................................................... 291
--only_stdout .................................................................................... 292
--output, -o ....................................................................................... 292
--pending_instantiations ................................................................... 292
--predef_macros ............................................................................... 293
--preinclude ..................................................................................... 293
--preprocess ...................................................................................... 293
--public_equ ..................................................................................... 294
--reduce_stack_usage ....................................................................... 294
--regvar_r4 ....................................................................................... 294
--regvar_r5 ....................................................................................... 295
--relaxed_fp ...................................................................................... 295
--remarks .......................................................................................... 296
--require_prototypes ......................................................................... 296
--ropi ................................................................................................. 296
--save_reg20 ..................................................................................... 297
--segment .......................................................................................... 297
--silent .............................................................................................. 299
--strict ............................................................................................... 299
--system_include_dir ........................................................................ 299

IAR C/C++ Compiler User Guide

16 for MSP430

AFE1_AFE2-1:1
 Contents

--use_c++_inline .............................................................................. 300

--version ........................................................................................... 300
--vla .................................................................................................. 300
--warn_about_c_style_casts ............................................................. 301
--warnings_affect_exit_code ............................................................ 301
--warnings_are_errors ...................................................................... 301

Data representation ...................................................................................... 303

Alignment ................................................................................................ 303

Alignment on the MSP430 microcontroller .................................... 304
Basic data types—integer types .................................................... 304
Integer types—an overview ............................................................. 304
Bool .................................................................................................. 305
The long long type .......................................................................... 305
The enum type .................................................................................. 305
The char type ................................................................................... 305
The wchar_t type ............................................................................. 305
Bitfields ............................................................................................ 306
Basic data types—floating-point types ....................................... 307
Floating-point environment .............................................................. 307
32-bit floating-point format ............................................................. 308
64-bit floating-point format ............................................................. 308
Representation of special floating-point numbers ........................... 308
Pointer types .......................................................................................... 309
Function pointers .............................................................................. 309
Data pointers .................................................................................... 309
Casting ............................................................................................. 310
Structure types ..................................................................................... 311
Alignment of structure types ............................................................ 311
General layout ................................................................................. 311
Packed structure types ..................................................................... 311
Type qualifiers ........................................................................................ 313
Declaring objects volatile ................................................................ 313
Declaring objects volatile and const ................................................ 314

17

AFE1_AFE2-1:1
 Declaring objects const .................................................................... 315
Data types in C++ ................................................................................. 315
Extended keywords ...................................................................................... 317

General syntax rules for extended keywords ........................... 317

Type attributes .................................................................................. 317
Object attributes .............................................................................. 319
Summary of extended keywords ................................................... 320
Descriptions of extended keywords ............................................. 321
__cc_rom ......................................................................................... 321
__cc_version1 .................................................................................. 322
__cc_version2 .................................................................................. 322
__data16 ........................................................................................... 322
__data20 ........................................................................................... 323
__interrupt ........................................................................................ 323
__intrinsic ........................................................................................ 324
__monitor ......................................................................................... 324
__no_alloc, __no_alloc16 ............................................................... 324
__no_alloc_str, __no_alloc_str16 ................................................... 325
__no_init .......................................................................................... 326
__no_multiplier ................................................................................ 326
__no_pic .......................................................................................... 326
__noreturn ........................................................................................ 327
__persistent ...................................................................................... 327
__ramfunc ........................................................................................ 327
__raw ............................................................................................... 328
__regvar ........................................................................................... 328
__root ............................................................................................... 328
__ro_placement ................................................................................ 329
__save_reg20 ................................................................................... 329
__task ............................................................................................... 330

IAR C/C++ Compiler User Guide

18 for MSP430

AFE1_AFE2-1:1
 Contents

Pragma directives ........................................................................................... 331

Summary of pragma directives ...................................................... 331

Descriptions of pragma directives ................................................ 333
basic_template_matching ................................................................. 333
bis_nmi_ie1 ...................................................................................... 334
bitfields ............................................................................................. 334
calls .................................................................................................. 335
call_graph_root ................................................................................ 335
constseg ............................................................................................ 336
data_alignment ................................................................................. 336
dataseg .............................................................................................. 337
default_function_attributes .............................................................. 337
default_variable_attributes ............................................................... 338
diag_default ...................................................................................... 339
diag_error ......................................................................................... 340
diag_remark ..................................................................................... 340
diag_suppress ................................................................................... 340
diag_warning .................................................................................... 341
error .................................................................................................. 341
include_alias ..................................................................................... 342
inline ................................................................................................. 342
language ........................................................................................... 343
location ............................................................................................. 344
message ............................................................................................ 344
no_epilogue ...................................................................................... 345
object_attribute ................................................................................. 345
optimize ............................................................................................ 346
pack ................................................................................................. 347
__printf_args .................................................................................... 348
public_equ ........................................................................................ 348
required ............................................................................................ 348
rtmodel ............................................................................................. 349
__scanf_args .................................................................................... 350

19

AFE1_AFE2-1:1
 segment ............................................................................................ 350
STDC CX_LIMITED_RANGE ....................................................... 351
STDC FENV_ACCESS ................................................................... 352
STDC FP_CONTRACT .................................................................. 352
type_attribute ................................................................................... 352
unroll ................................................................................................ 353
vector ................................................................................................ 354
weak ................................................................................................. 354

Intrinsic functions ........................................................................................... 355

Summary of intrinsic functions ....................................................... 355

Descriptions of intrinsic functions ................................................. 357
__bcd_add_type .............................................................................. 357
__bic_SR_register ............................................................................ 357
__bic_SR_register_on_exit .............................................................. 358
__bis_GIE_interrupt_state ............................................................... 358
__bis_SR_register ............................................................................ 358
__bis_SR_register_on_exit .............................................................. 358
__code_distance ............................................................................... 358
__data16_read_addr ......................................................................... 359
__data16_write_addr ....................................................................... 359
__data20_longjmp ........................................................................... 360
__data20_read_type ......................................................................... 360
__data20_setjmp .............................................................................. 360
__data20_write_type ........................................................................ 361
__delay_cycles ................................................................................. 361
__disable_interrupt .......................................................................... 361
__enable_interrupt ........................................................................... 362
__even_in_range .............................................................................. 362
__get_interrupt_state ....................................................................... 362
__get_R4_register ............................................................................ 363
__get_R5_register ............................................................................ 363
__get_SP_register ............................................................................ 363
__get_SR_register ............................................................................ 364

IAR C/C++ Compiler User Guide

20 for MSP430

AFE1_AFE2-1:1
 Contents

__get_SR_register_on_exit .............................................................. 364

__low_power_mode_n .................................................................... 364
__low_power_mode_off_on_exit .................................................... 364
__no_operation ................................................................................ 364
__op_code ........................................................................................ 364
__saturated_add_signed_type .......................................................... 365
__saturated_add_unsigned_type ...................................................... 365
__saturated_sub_signed_type .......................................................... 365
__saturated_sub_unsigned_type ...................................................... 365
__set_interrupt_state ........................................................................ 366
__set_R4_register ............................................................................ 366
__set_R5_register ............................................................................ 366
__set_SP_register ............................................................................ 367
__swap_bytes ................................................................................... 367

The preprocessor .......................................................................................... 369

Overview of the preprocessor ........................................................ 369

Description of predefined preprocessor symbols ................... 370
__BASE_FILE__ ............................................................................ 370
__BUILD_NUMBER__ .................................................................. 370
__CODE_MODEL__ ...................................................................... 370
__CORE__ ...................................................................................... 370
__COUNTER__ .............................................................................. 370
__cplusplus ...................................................................................... 370
__DATA_MODEL__ ...................................................................... 371
__DATE__ ...................................................................................... 371
__embedded_cplusplus .................................................................... 371
__FILE__ ......................................................................................... 371
__func__ .......................................................................................... 372
__FUNCTION__ ............................................................................. 372
__IAR_SYSTEMS_ICC__ ............................................................. 372
__ICC 430 __
.................................................................................... 372
__LINE__ ........................................................................................ 372
__POSITION_INDEPENDENT_CODE__ .................................... 372

21

AFE1_AFE2-1:1
 __PRETTY_FUNCTION__ ............................................................ 373
__REGISTER_MODEL__ .............................................................. 373
__REGISTER_R4__ ....................................................................... 373
__REGISTER_R5__ ....................................................................... 373
__ROPI__ ........................................................................................ 373
__STDC__ ....................................................................................... 373
__STDC_VERSION__ ................................................................... 374
__SUBVERSION__ ........................................................................ 374
__TIME__ ....................................................................................... 374
__TIMESTAMP__ .......................................................................... 374
__VER__ ......................................................................................... 374
Descriptions of miscellaneous preprocessor extensions ..... 374
NDEBUG ........................................................................................ 375
#warning message ........................................................................... 375

C/C++ standard library functions .......................................................... 377

C/C++ standard library overview ................................................. 377
Header files ...................................................................................... 378
Library object files ........................................................................... 378
Alternative more accurate library functions .................................... 378
Reentrancy ....................................................................................... 378
The longjmp function ....................................................................... 379
DLIB runtime environment—implementation details ......... 379
C header files ................................................................................... 380
C++ header files ............................................................................... 381
Library functions as intrinsic functions ........................................... 383
Added C functionality ...................................................................... 383
Symbols used internally by the library ............................................ 385
CLIB runtime environment—implementation details ......... 386
Library definitions summary ............................................................ 386

Segment reference ......................................................................................... 387

Summary of segments ...................................................................... 387

Descriptions of segments .................................................................. 389
BSLSIGNATURE ............................................................................ 389

IAR C/C++ Compiler User Guide

22 for MSP430

AFE1_AFE2-1:1
 Contents

CHECKSUM ................................................................................... 390

CODE ............................................................................................... 390
CODE_I ........................................................................................... 390
CODE_ID ......................................................................................... 391
CODE_PAD ..................................................................................... 391
CODE16 ........................................................................................... 391
CSTACK ......................................................................................... 391
CSTART .......................................................................................... 392
DATA16_AC ................................................................................... 392
DATA16_AN ................................................................................... 392
DATA16_C ...................................................................................... 392
DATA16_HEAP .............................................................................. 393
DATA16_I ....................................................................................... 393
DATA16_ID .................................................................................... 393
DATA16_N ...................................................................................... 394
DATA16_P ...................................................................................... 394
DATA16_Z ...................................................................................... 394
DATA20_AC ................................................................................... 395
DATA20_AN ................................................................................... 395
DATA20_C ...................................................................................... 395
DATA20_HEAP .............................................................................. 396
DATA20_I ....................................................................................... 396
DATA20_ID .................................................................................... 396
DATA20_N ...................................................................................... 397
DATA20_P ...................................................................................... 397
DATA20_Z ...................................................................................... 397
DIFUNCT ........................................................................................ 398
INFO ................................................................................................ 398
INFOA ............................................................................................. 398
INFOB .............................................................................................. 399
INFOC .............................................................................................. 399
INFOD ............................................................................................. 399
INTVEC .......................................................................................... 399
IPE_B1 ............................................................................................. 400

23

AFE1_AFE2-1:1
 IPE_B2 ............................................................................................. 400
IPECODE16 ..................................................................................... 400
IPEDATA16_C ................................................................................ 401
IPEDATA16_N ................................................................................ 401
IPESIGNATURE ............................................................................. 401
ISR_CODE ....................................................................................... 401
JTAGSIGNATURE ......................................................................... 402
MPU_B1 .......................................................................................... 402
MPU_B2 .......................................................................................... 402
REGVAR_AN ................................................................................. 402
RESET ............................................................................................. 403
SIGNATURE ................................................................................... 403
TLS16_I ........................................................................................... 403
TLS16_ID ........................................................................................ 404

The stack usage control file ...................................................................... 405

Overview .................................................................................................. 405

C++ names ....................................................................................... 405
Stack usage control directives ........................................................ 405
call graph root directive ................................................................... 405
check that directive .......................................................................... 406
exclude directive .............................................................................. 406
function directive ............................................................................. 407
max recursion depth directive .......................................................... 407
no calls from directive ...................................................................... 408
possible calls directive ..................................................................... 408
Syntactic components ........................................................................ 409
category ............................................................................................ 409
func-spec .......................................................................................... 409
module-spec ..................................................................................... 410
name ................................................................................................. 410
call-info ............................................................................................ 410
stack-size .......................................................................................... 411
size .................................................................................................... 411

IAR C/C++ Compiler User Guide

24 for MSP430

AFE1_AFE2-1:1
 Contents

Implementation-defined behavior for Standard C ........................ 413

Descriptions of implementation-defined behavior ................ 413

J.3.1 Translation ............................................................................... 413
J.3.2 Environment ............................................................................ 414
J.3.3 Identifiers ................................................................................. 415
J.3.4 Characters ................................................................................ 415
J.3.5 Integers .................................................................................... 417
J.3.6 Floating point ........................................................................... 417
J.3.7 Arrays and pointers .................................................................. 418
J.3.8 Hints ........................................................................................ 419
J.3.9 Structures, unions, enumerations, and bitfields ....................... 419
J.3.10 Qualifiers ............................................................................... 420
J.3.11 Preprocessing directives ........................................................ 420
J.3.12 Library functions ................................................................... 422
J.3.13 Architecture ........................................................................... 426
J.4 Locale ......................................................................................... 427

Implementation-defined behavior for C89 ....................................... 429

Descriptions of implementation-defined behavior ................ 429

Translation ....................................................................................... 429
Environment ..................................................................................... 429
Identifiers ......................................................................................... 430
Characters ......................................................................................... 430
Integers ............................................................................................. 431
Floating point ................................................................................... 432
Arrays and pointers .......................................................................... 433
Registers ........................................................................................... 433
Structures, unions, enumerations, and bitfields ............................... 433
Qualifiers .......................................................................................... 434
Declarators ....................................................................................... 434
Statements ........................................................................................ 434
Preprocessing directives ................................................................... 434
Library functions for the IAR DLIB runtime environment ............. 436
Library functions for the CLIB runtime environment ..................... 439

25

AFE1_AFE2-1:1
 Index ..................................................................................................................... 443

IAR C/C++ Compiler User Guide

26 for MSP430

AFE1_AFE2-1:1
Tables
1: Typographic conventions used in this guide ......................................................... 34
2: Naming conventions used in this guide ................................................................ 35
3: Memory types and their corresponding memory attributes .................................. 61
4: Data model characteristics .................................................................................... 66
5: Heaps supported in memory types ........................................................................ 70
6: Code models .......................................................................................................... 72
7: segments holding initialized data .......................................................................... 90
8: Example of runtime model attributes .................................................................. 112
9: Predefined runtime model attributes ................................................................... 113
10: Debug information and levels of C-SPY emulated I/O .................................... 120
11: Library configurations ....................................................................................... 127
12: Formatters for printf .......................................................................................... 129
13: Formatters for scanf .......................................................................................... 130
14: Extended command line files for the small math functions .............................. 132
15: DLIB low-level I/O interface functions ............................................................ 139
16: Descriptions of printf configuration symbols ................................................... 148
17: Descriptions of scanf configuration symbols .................................................... 148
18: Additional linker configuration files for the hardware multiplier ..................... 152
19: Library objects using TLS ................................................................................. 155
20: Macros for implementing TLS allocation ......................................................... 158
21: Inline assembler operand constraints ................................................................ 174
22: Supported constraint modifiers ......................................................................... 174
23: List of valid clobbers ......................................................................................... 176
24: Operand modifiers and transformations ............................................................ 177
25: Registers used for passing parameters .............................................................. 186
26: Registers used for returning values ................................................................... 187
27: Call frame information resources defined in a names block ............................. 193
28: Language extensions ......................................................................................... 199
29: Compiler optimization levels ............................................................................ 242
30: Compiler environment variables ....................................................................... 256
31: Error return codes .............................................................................................. 259

27

AFE1_AFE2-1:1
 32: Compiler options summary ............................................................................... 265
33: Integer types ...................................................................................................... 304
34: Floating-point types .......................................................................................... 307
35: Function pointers ............................................................................................... 309
36: Data pointers ..................................................................................................... 309
37: Extended keywords summary ........................................................................... 320
38: Pragma directives summary .............................................................................. 331
39: Intrinsic functions summary .............................................................................. 355
40: Functions for binary coded decimal operations ................................................ 357
41: Functions for reading data that has a 20-bit address ......................................... 360
42: Functions for writing data that has a 20-bit address ......................................... 361
43: Traditional Standard C header files—DLIB ..................................................... 380
44: C++ header files ................................................................................................ 381
45: Standard template library header files ............................................................... 382
46: New Standard C header files—DLIB ............................................................... 382
47: CLIB runtime environment header files ........................................................... 386
48: Segment summary ............................................................................................. 387
49: Message returned by strerror()—DLIB runtime environment .......................... 428
50: Message returned by strerror()—DLIB runtime environment .......................... 439
51: Message returned by strerror()—CLIB runtime environment .......................... 442

IAR C/C++ Compiler User Guide

28 for MSP430

AFE1_AFE2-1:1
 Preface
Welcome to the IAR C/C++ Compiler User Guide for MSP430. The purpose of
this guide is to provide you with detailed reference information that can help
you to use the compiler to best suit your application requirements. This guide
also gives you suggestions on coding techniques so that you can develop
applications with maximum efficiency.

Who should read this guide

Read this guide if you plan to develop an application using the C or C++ language for
the MSP430 microcontroller, and need detailed reference information on how to use the
compiler.

REQUIRED KNOWLEDGE
To use the tools in IAR Embedded Workbench, you should have working knowledge of:
● The architecture and instruction set of the MSP430 microcontroller (refer to the
chip manufacturer's documentation)
● The C or C++ programming language
● Application development for embedded systems
● The operating system of your host computer.
For more information about the other development tools incorporated in the IDE, refer
to their respective documentation, see Other documentation, page 31.

How to use this guide

When you start using the IAR C/C++ Compiler for MSP430, you should read Part 1.
Using the compiler in this guide.
When you are familiar with the compiler and have already configured your project, you
can focus more on Part 2. Reference information.
If you are new to using this product, we suggest that you first go through the tutorials,
which you can find in IAR Information Center in the product. They will help you get
started using IAR Embedded Workbench.

29

AFE1_AFE2-1:1
What this guide contains

What this guide contains

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

PART 1. USING THE COMPILER

● Introduction to the IAR build tools gives an introduction to the IAR build tools,
which includes an overview of the tools, the programming languages, the available
device support, and extensions provided for supporting specific features of the
MSP430 microcontroller.
● Developing embedded applications gives the information you need to get started
developing your embedded software using the IAR build tools.
● Data storage describes how to store data in memory.
● Functions gives a brief overview of function-related extensions—mechanisms for
controlling functions—and describes some of these mechanisms in more detail.
● Linking overview describes the linking process using the IAR XLINK Linker and
the related concepts.
● Linking your application lists aspects that you must consider when linking your
application, including using XLINK options and tailoring the linker configuration
file.
● The DLIB runtime environment describes the DLIB runtime environment in which
an application executes. It covers how you can modify it by setting options,
overriding default library modules, or building your own library. The chapter also
describes system initialization introducing the file cstartup, how to use modules
for locale, and file I/O.
● The CLIB runtime environment gives an overview of the CLIB runtime libraries and
how to customize them. The chapter also describes system initialization and
introduces the file cstartup.
● Assembler language interface contains information required when parts of an
application are written in assembler language. This includes the calling convention.
● Using C gives an overview of the two supported variants of the C language and an
overview of the compiler extensions, such as extensions to Standard C.
● Using C++ gives an overview of the two levels of C++ support: The
industry-standard EC++ and IAR Extended EC++.
● Application-related considerations discusses a selected range of application issues
related to using the compiler and linker.
● Efficient coding for embedded applications gives hints about how to write code that
compiles to efficient code for an embedded application.

IAR C/C++ Compiler User Guide

30 for MSP430

AFE1_AFE2-1:1
 Preface

PART 2. REFERENCE INFORMATION

● External interface details provides reference information about how the compiler
interacts with its environment—the invocation syntax, methods for passing options
to the compiler, environment variables, the include file search procedure, and the
different types of compiler output. The chapter also describes how the compiler’s
diagnostic system works.
● Compiler options explains how to set options, gives a summary of the options, and
contains detailed reference information for each compiler option.
● Data representation describes the available data types, pointers, and structure types.
This chapter also gives information about type and object attributes.
● Extended keywords gives reference information about each of the MSP430-specific
keywords that are extensions to the standard C/C++ language.
● Pragma directives gives reference information about the pragma directives.
● Intrinsic functions gives reference information about functions to use for accessing
MSP430-specific low-level features.
● The preprocessor gives a brief overview of the preprocessor, including reference
information about the different preprocessor directives, symbols, and other related
information.
● C/C++ standard library functions gives an introduction to the C or C++ library
functions, and summarizes the header files.
● Segment reference gives reference information about the compiler’s use of
segments.
● The stack usage control file describes the syntax and semantics of stack usage
control files.
● Implementation-defined behavior for Standard C describes how the compiler
handles the implementation-defined areas of Standard C.
● Implementation-defined behavior for C89 describes how the compiler handles the
implementation-defined areas of the C language standard C89.

Other documentation
User documentation is available as hypertext PDFs and as a context-sensitive online
help system in HTML format. You can access the documentation from the Information
Center or from the Help menu in the IAR Embedded Workbench IDE. The online help
system is also available via the F1 key.

31

AFE1_AFE2-1:1
Other documentation

USER AND REFERENCE GUIDES

The complete set of IAR Systems development tools is described in a series of guides.
Information about:
● System requirements and information about how to install and register the IAR
Systems products are available in the Installation and Licensing Quick Reference
Guide and the Licensing Guide.
● Using the IDE for project management and building, is available in the IDE Project
Management and Building Guide.
● Using the IAR C-SPY® Debugger, is available in the C-SPY® Debugging Guide
for MSP430.
● Programming for the IAR C/C++ Compiler for MSP430, is available in the IAR
C/C++ Compiler User Guide for MSP430.
● Using the IAR XLINK Linker, the IAR XAR Library Builder, and the IAR XLIB
Librarian, is available in the IAR Linker and Library Tools Reference Guide.
● Programming for the IAR Assembler for MSP430, is available in the IAR Assembler
User Guide for MSP430.
● Performing a static analysis using C-STAT and the required checks, is available in
the C-STAT® Static Analysis Guide.
● Developing safety-critical applications using the MISRA C guidelines, is available
in the IAR Embedded Workbench® MISRA C:2004 Reference Guide or the IAR
Embedded Workbench® MISRA C:1998 Reference Guide.
● Porting application code and projects created with a previous version of the IAR
Embedded Workbench for MSP430, is available in the IAR Embedded Workbench®
Migration Guide.
Note: Additional documentation might be available depending on your product
installation.

THE ONLINE HELP SYSTEM

The context-sensitive online help contains:
● Information about project management, editing, and building in the IDE
● Information about debugging using the IAR C-SPY® Debugger
● Reference information about the menus, windows, and dialog boxes in the IDE
● Compiler reference information
● Keyword reference information for the DLIB library functions. To obtain reference
information for a function, select the function name in the editor window and press
F1. Note that if you select a function name in the editor window and press F1 while

IAR C/C++ Compiler User Guide

32 for MSP430

AFE1_AFE2-1:1
 Preface

using the CLIB C standard library, you will get reference information for the DLIB
C standard library.

FURTHER READING
These books might be of interest to you when using the IAR Systems development tools:
● Barr, Michael, and Andy Oram, ed. Programming Embedded Systems in C and
C++. O’Reilly & Associates.
● Harbison, Samuel P. and Guy L. Steele (contributor). C: A Reference Manual.
Prentice Hall.
● Labrosse, Jean J. Embedded Systems Building Blocks: Complete and Ready-To-Use
Modules in C. R&D Books.
● Mann, Bernhard. C für Mikrocontroller. Franzis-Verlag. [Written in German.]
● Meyers, Scott. Effective C++. Addison-Wesley.
● Meyers, Scott. More Effective C++. Addison-Wesley.
● Meyers, Scott. Effective STL. Addison-Wesley.
● Sutter, Herb. Exceptional C++: 47 Engineering Puzzles, Programming Problems,
and Solutions. Addison-Wesley.
The web site isocpp.org also has a list of recommended books about C++ programming.

WEB SITES
Recommended web sites:
● The Texas Instruments web site, www.ti.com, that contains information and news
about the MSP430 microcontrollers.
● The IAR Systems web site, www.iar.com, that holds application notes and other
product information.
● The web site of the C standardization working group,
www.open-std.org/jtc1/sc22/wg14.
● The web site of the C++ Standards Committee, www.open-std.org/jtc1/sc22/wg21.
● The C++ programming language web site, isocpp.org. This web site also has a list
of recommended books about C++ programming.
● The C and C++ reference web site, en.cppreference.com.

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

33

AFE1_AFE2-1:1
Document conventions

When referring to a directory in your product installation, for example 430\doc, the full
path to the location is assumed, for example c:\Program Files\IAR
Systems\Embedded Workbench N.n\430\doc, where the initial digit of the version
number reflects the initial digit of the version number of the IAR Embedded Workbench
shared components.

TYPOGRAPHIC CONVENTIONS
The IAR Systems documentation set uses the following typographic conventions:
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 stack usage control directive, where [ and ] are
not part of the actual directive, but any [, ], {, or } are part of the
directive syntax.
{option} A mandatory part of a stack usage control directive, where { and } are
not part of the actual directive, but any [, ], {, or } are part of the
directive syntax.
[option] An optional part of a command line option, pragma directive, or library
filename.
[a|b|c] An optional part of a command line option, pragma directive, or library
filename with alternatives.
{a|b|c} A mandatory part of a command line option, pragma directive, or
library filename 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.

Table 1: Typographic conventions used in this guide

IAR C/C++ Compiler User Guide

34 for MSP430

AFE1_AFE2-1:1
 Preface

Style Used for

Identifies warnings.

Table 1: Typographic conventions used in this guide (Continued)

NAMING CONVENTIONS
The following naming conventions are used for the products and tools from IAR
Systems®, when referred to in the documentation:
Brand name Generic term
IAR Embedded Workbench® for MSP430 IAR Embedded Workbench®
IAR Embedded Workbench® IDE for MSP430 the IDE
IAR C-SPY® Debugger for MSP430 C-SPY, the debugger
IAR C-SPY® Simulator the simulator
IAR C/C++ Compiler™ for MSP430 the compiler
IAR Assembler™ for MSP430 the assembler
IAR XLINK Linker™ XLINK, the linker
IAR XAR Library Builder™ the library builder
IAR XLIB Librarian™ the librarian
IAR CLIB Runtime Environment™ the CLIB runtime environment
IAR DLIB Runtime Environment™ the DLIB runtime environment
Table 2: Naming conventions used in this guide

35

AFE1_AFE2-1:1
Document conventions

IAR C/C++ Compiler User Guide

36 for MSP430

AFE1_AFE2-1:1
Part 1. Using the compiler
This part of the IAR C/C++ Compiler User Guide for MSP430 includes these
chapters:

● Introduction to the IAR build tools

● Developing embedded applications

● Data storage

● Functions

● Linking overview

● Linking your application

● The DLIB runtime environment

● The CLIB runtime environment

● Assembler language interface

● Using C

● Using C++

● Application-related considerations

● Efficient coding for embedded applications

37
38
 Introduction to the IAR
build tools
● The IAR build tools—an overview

● IAR language overview

● Device support

● Special support for embedded systems

The IAR build tools—an overview

In the IAR product installation you can find a set of tools, code examples, and user
documentation, all suitable for developing software for MSP430-based embedded
applications. The tools allow you to develop your application in C, C++, or in assembler
language.
IAR Embedded Workbench® is a powerful Integrated Development Environment (IDE)
that allows you to develop and manage complete embedded application projects. It
provides an easy-to-learn and highly efficient development environment with maximum
code inheritance capabilities, and comprehensive and specific target support. IAR
Embedded Workbench promotes a useful working methodology, and therefore a
significant reduction in development time.
For information about the IDE, see the IDE Project Management and Building Guide.
The compiler, assembler, and linker can also be run from a command line environment,
if you want to use them as external tools in an already established project environment.

THE IAR C/C++ COMPILER

The IAR C/C++ Compiler for MSP430 is a state-of-the-art compiler that offers the
standard features of the C and C++ languages, plus extensions designed to take
advantage of the MSP430-specific facilities.

THE IAR ASSEMBLER

The IAR Assembler for MSP430 is a powerful relocating macro assembler with a
versatile set of directives and expression operators. The assembler features a built-in C
language preprocessor, and supports conditional assembly.

39

AFE1_AFE2-1:1
IAR language overview

The IAR Assembler for MSP430 uses the same mnemonics and operand syntax as the
Texas Instruments MSP430 Assembler, which simplifies the migration of existing code.
For more information, see the IAR Assembler User Guide for MSP430.

THE IAR XLINK LINKER

The IAR XLINK Linker is a powerful, flexible software tool for use in the development
of embedded controller applications. It is equally well suited for linking small,
single-file, absolute assembler programs as it is for linking large, relocatable input,
multi-module, C/C++, or mixed C/C++ and assembler programs.
To handle libraries, the library tools XAR and XLIB are included.

EXTERNAL TOOLS
For information about how to extend the tool chain in the IDE, see the IDE Project
Management and Building Guide.

IAR language overview

The IAR C/C++ Compiler for MSP430 supports:
● C, the most widely used high-level programming language in the embedded systems
industry. You can build freestanding applications that follow these standards:
● Standard C—also known as C99. Hereafter, this standard is referred to as
Standard C in this guide.
● C89—also known as C94, C90, C89, and ANSI C. This standard is required
when MISRA C is enabled.
● C++, a modern object-oriented programming language with a full-featured library
well suited for modular programming. Any of these standards can be used:
● Embedded C++ (EC++)—a subset of the C++ programming standard, which is
intended for embedded systems programming. It is defined by an industry
consortium, the Embedded C++ Technical committee. See the chapter Using
C++.
● IAR Extended Embedded C++ (EEC++)—EC++ with additional features such
as full template support, multiple inheritance, namespace support, the new cast
operators, as well as the Standard Template Library (STL).
Each of the supported languages can be used in strict or relaxed mode, or relaxed with
IAR extensions enabled. The strict mode adheres to the standard, whereas the relaxed
mode allows some common deviations from the standard.
For more information about C, see the chapter Using C.

IAR C/C++ Compiler User Guide

40 for MSP430

AFE1_AFE2-1:1
 Introduction to the IAR build tools

For more information about Embedded C++ and Extended Embedded C++, see the
chapter Using C++.
For information about how the compiler handles the implementation-defined areas of
the languages, see the chapter Implementation-defined behavior for Standard C.
It is also possible to implement parts of the application, or the whole application, in
assembler language. See the IAR Assembler User Guide for MSP430.

Device support
To get a smooth start with your product development, the IAR product installation
comes with a wide range of device-specific support.

SUPPORTED MSP430 DEVICES

The IAR C/C++ Compiler for MSP430 supports all devices based on the standard Texas
Instruments MSP430 microcontroller, which includes both the MSP430 architecture
and the MSP430X architecture. In addition, the application can use the hardware
multiplier if available on the device.
Note: Unless otherwise stated, in this guide all references to the MSP430
microcontroller refer to both the MSP430 and the MSP430X microcontroller.

PRECONFIGURED SUPPORT FILES

The IAR product installation contains preconfigured files for supporting different
devices. If you need additional files for device support, they can be created using one of
the provided ones as a template.

Header files for I/O

Standard peripheral units are defined in device-specific I/O header files with the
filename extension h. The product package supplies I/O files for all devices that are
available at the time of the product release. You can find these files in the 430\inc
directory. Make sure to include the appropriate include file in your application source
files. If you need additional I/O header files, they can be created using one of the
provided ones as a template.
There are two types of I/O header files:
● Files named iodevice.h (for example io430x44x.h and io430fr5969.h) use C
unions and structures with bitfields to describe special function registers and the
individual fields.

41

AFE1_AFE2-1:1
Special support for embedded systems

● Files named mspdevice.h (for example msp430f449.h and cc430f5123.h) use

the Texas Instruments style definitions, where special function registers are defined
using plain integer types and individual bits are defined using preprocessor macros.
The generic I/O header files io430.h and msp430.h can be used for including the
correct I/O header file for the device that is used. A preprocessor symbol on the form
__DEVICE__ (for example __MSP430SL5438A__) must be defined. When used in IAR
Embedded Workbench, this preprocessor symbol is automatically defined.
For more information, see Accessing special function registers, page 249.

Linker configuration files

The 430\config directory contains ready-made linker configuration files for all
supported devices. The files have the filename extension xcl and contain the
information required by the linker. For more information about the linker configuration
file, see Placing code and data—the linker configuration file, page 88 as well as the IAR
Linker and Library Tools Reference Guide.

Device description files

The debugger handles several of the device-specific requirements, such as definitions of
available memory areas, peripheral registers and groups of these, by using device
description files. These files are located in the 430\config directory and they have the
filename extension ddf. The peripheral registers and groups of these can be defined in
separate files (filename extension sfr), which in that case are included in the ddf file.
For more information about these files, see the C-SPY® Debugging Guide for MSP430.

EXAMPLES FOR GETTING STARTED

The 430\examples directory contains several examples of working applications to
give you a smooth start with your development. Examples are provided for most of the
supported device families.

Special support for embedded systems

This section briefly describes the extensions provided by the compiler to support
specific features of the MSP430 microcontroller.

EXTENDED KEYWORDS
The compiler provides a set of keywords that can be used for configuring how the code
is generated. For example, there are keywords for controlling how to access and store
data objects, as well as for controlling how a function should work internally and how
it should be called/returned.

IAR C/C++ Compiler User Guide

42 for MSP430

AFE1_AFE2-1:1
 Introduction to the IAR build tools

By default, language extensions are enabled in the IDE.

The command line option -e makes the extended keywords available, and reserves them
so that they cannot be used as variable names. See -e, page 278 for additional
information.
For more information, see the chapter Extended keywords. See also Data storage and
Functions.

PRAGMA DIRECTIVES
The pragma directives control the behavior of the compiler, for example how it allocates
memory, whether it allows extended keywords, and whether it issues warning messages.
The pragma directives are always enabled in the compiler. They are consistent with
standard C, and are useful when you want to make sure that the source code is portable.
For more information about the pragma directives, see the chapter Pragma directives.

PREDEFINED SYMBOLS
With the predefined preprocessor symbols, you can inspect your compile-time
environment, for example time of compilation or the build number of the compiler.
For more information about the predefined symbols, see the chapter The preprocessor.

ACCESSING LOW-LEVEL FEATURES

For hardware-related parts of your application, accessing low-level features is essential.
The compiler supports several ways of doing this: intrinsic functions, mixing C and
assembler modules, and inline assembler. For information about the different methods,
see Mixing C and assembler, page 169.

43

AFE1_AFE2-1:1
Special support for embedded systems

IAR C/C++ Compiler User Guide

44 for MSP430

AFE1_AFE2-1:1
 Developing embedded
applications
● Developing embedded software using IAR build tools

● The build process—an overview

● Application execution—an overview

● Building applications—an overview

● Basic project configuration

Developing embedded software using IAR build tools

Typically, embedded software written for a dedicated microcontroller is designed as an
endless loop waiting for some external events to happen. The software is located in
ROM and executes on reset. You must consider several hardware and software factors
when you write this kind of software. To assist you, compiler options, extended
keywords, pragma directives, etc., are included.

CPU FEATURES AND CONSTRAINTS

Some of the basic features of the MSP430 microcontroller is ultra low-power mode
support and a wide range of devices targeted at specific kinds of embedded systems.
When developing software for the MSP430 microcontroller, you must consider some
CPU constraints, such as the instruction set and features like hardware multiplier,
memory protection unit, and memory configuration.
The compiler supports this by means of compiler options, extended keywords, pragma
directives, etc.

MAPPING OF MEMORY
Embedded systems typically contain various types of memory, such as RAM, FRAM,
ROM, EEPROM, or flash memory.
As an embedded software developer, you must understand the features of the different
types of memory. For example, on-chip RAM is often faster than other types of
memories, and variables that are accessed often would in time-critical applications

45

AFE1_AFE2-1:1
Developing embedded software using IAR build tools

benefit from being placed here. Conversely, some configuration data might be seldom
accessed but must maintain its value after power off, so it should be saved in EEPROM
or flash memory.
For efficient memory usage, the compiler provides several mechanisms for controlling
placement of functions and data objects in memory. For more information, see
Controlling data and function placement in memory, page 236.
The linker places sections of code and data in memory according to the directives you
specify in the linker configuration file, see Placing code and data—the linker
configuration file, page 88.

COMMUNICATION WITH PERIPHERAL UNITS

If external devices are connected to the microcontroller, you might need to initialize and
control the signaling interface, for example by using chip select pins, and detect and
handle external interrupt signals. Typically, this must be initialized and controlled at
runtime. The normal way to do this is to use special function registers (SFR). These are
typically available at dedicated addresses, containing bits that control the chip
configuration.
Standard peripheral units are defined in device-specific I/O header files with the
filename extension h. See Device support, page 41. For an example, see Accessing
special function registers, page 249.

EVENT HANDLING
In embedded systems, using interrupts is a method for handling external events
immediately, for example, detecting that a button was pressed. In general, when an
interrupt occurs in the code, the microcontroller immediately stops executing the code
it runs, and starts executing an interrupt routine instead.
The compiler provides various primitives for managing hardware and software
interrupts, which means that you can write your interrupt routines in C, see Primitives
for interrupts, concurrency, and OS-related programming, page 73.

SYSTEM STARTUP
In all embedded systems, system startup code is executed to initialize the system—both
the hardware and the software system—before the main function of the application is
called.
As an embedded software developer, you must ensure that the startup code is located at
the dedicated memory addresses, or can be accessed using a pointer from the vector
table. This means that startup code and the initial vector table must be placed in
non-volatile memory, such as ROM, EPROM, or flash.

IAR C/C++ Compiler User Guide

46 for MSP430

AFE1_AFE2-1:1
 Developing embedded applications

A C/C++ application further needs to initialize all global variables. This initialization is
handled by the linker in conjunction with the system startup code. For more information,
see Application execution—an overview, page 50.

REAL-TIME OPERATING SYSTEMS

In many cases, the embedded application is the only software running in the system.
However, using an RTOS has some advantages.
For example, the timing of high-priority tasks is not affected by other parts of the
program which are executed in lower priority tasks. This typically makes a program
more deterministic and can reduce power consumption by using the CPU efficiently and
putting the CPU in a lower-power state when idle.
Using an RTOS can make your program easier to read and maintain, and in many cases
smaller as well. Application code can be cleanly separated into tasks that are
independent of each other. This makes teamwork easier, as the development work can
be easily split into separate tasks which are handled by one developer or a group of
developers.
Finally, using an RTOS reduces the hardware dependence and creates a clean interface
to the application, making it easier to port the program to different target hardware.
See also Managing a multithreaded environment, page 154.

The build process—an overview

This section gives an overview of the build process—how the various build tools
(compiler, assembler, and linker) fit together, going from source code to an executable
image.
To become familiar with the process in practice, you should go through the tutorials
available from the IAR Information Center.

THE TRANSLATION PROCESS

There are two tools in the IDE that translate application source files to intermediary
object files—the IAR C/C++ Compiler and the IAR Assembler. Both produce
relocatable object files in the IAR UBROF format.
Note: The compiler can also be used for translating C source code into assembler source
code. If required, you can modify the assembler source code which can then be
assembled into object code. For more information about the IAR Assembler, see the IAR
Assembler User Guide for MSP430.

47

AFE1_AFE2-1:1
The build process—an overview

This illustration shows the translation process:

After the translation, you can choose to pack any number of modules into an archive, or
in other words, a library. The important reason you should use libraries is that each
module in a library is conditionally linked in the application, or in other words, is only
included in the application if the module is used directly or indirectly by a module
supplied as an object file. Optionally, you can create a library, then use the IAR XAR
Library Builder or the IAR XLIB Librarian.

THE LINKING PROCESS

The relocatable modules in object files and libraries, produced by the IAR compiler and
assembler cannot be executed as is. To become an executable application, they must be
linked.
The IAR XLINK Linker (xlink.exe) is used for building the final application.
Normally, the linker requires the following information as input:
● Several object files and possibly certain libraries
● The standard library containing the runtime environment and the standard language
functions
● A program start label (set by default)
● The linker configuration file that describes placement of code and data in the
memory of the target system
● Information about the output format.

IAR C/C++ Compiler User Guide

48 for MSP430

AFE1_AFE2-1:1
 Developing embedded applications

The IAR XLINK Linker produces output according to your specifications. Choose
the output format that suits your purpose. You might want to load the output to a
debugger—which means that you need output with debug information. Alternatively,
you might want to load output to a flash loader or a PROM programmer—in which
case you need output without debug information, such as Intel hex or Motorola S–
records. The option -F can be used for specifying the output format.
This illustration shows the linking process:

Note: The Standard C/C++ library contains support routines for the compiler, and the
implementation of the C/C++ standard library functions.
While linking, the linker might produce error messages and logging messages on
stdout and stderr. The log messages are useful for understanding why an application
was linked the way it was, for example, why a module was included or a section
removed.
For more information about the procedure performed by the linker, see the IAR Linker
and Library Tools Reference Guide.

49

AFE1_AFE2-1:1
Application execution—an overview

AFTER LINKING
The IAR XLINK Linker produces an absolute object file in the output format you
specify. After linking, the produced absolute executable image can be used for:
● Loading into the IAR C-SPY Debugger or any other compatible external debugger
that reads UBROF.
● Programming to a flash/PROM using a flash/PROM programmer.
This illustration shows the possible uses of the absolute output files:

Application execution—an overview

This section gives an overview of the execution of an embedded application divided into
three phases, the:
● Initialization phase
● Execution phase
● Termination phase.

THE INITIALIZATION PHASE

Initialization is executed when an application is started (the CPU is reset) but before the
main function is entered. The initialization phase can for simplicity be divided into:

● Hardware initialization, which generally at least initializes the stack pointer.

The hardware initialization is typically performed in the system startup code
cstartup.s43 and if required, by an extra low-level routine that you provide. It
might include resetting/starting the rest of the hardware, setting up the CPU, etc, in
preparation for the software C/C++ system initialization.

IAR C/C++ Compiler User Guide

50 for MSP430

AFE1_AFE2-1:1
 Developing embedded applications

● Software C/C++ system initialization

Typically, this includes assuring that every global (statically linked) C/C++ symbol
receives its proper initialization value before the main function is called.
● Application initialization
This depends entirely on your application. It can include setting up an RTOS kernel
and starting initial tasks for an RTOS-driven application. For a bare-bone application,
it can include setting up various interrupts, initializing communication, initializing
devices, etc.
For a ROM/flash-based system, constants and functions are already placed in ROM. All
symbols placed in RAM must be initialized before the main function is called. The
linker has already divided the available RAM into different areas for variables, stack,
heap, etc.
The following sequence of illustrations gives a simplified overview of the different
stages of the initialization.
1 When an application is started, the system startup code first performs hardware
initialization, such as initialization of the stack pointer to point at the end of the
predefined stack area:

51

AFE1_AFE2-1:1
Application execution—an overview

2 Then, memories that should be zero-initialized are cleared, in other words, filled with
zeros:

Typically, this is data referred to as zero-initialized data—variables declared as, for

example, int i = 0;
3 For initialized data, data declared, for example, like int i = 6; the initializers are
copied from ROM to RAM:

IAR C/C++ Compiler User Guide

52 for MSP430

AFE1_AFE2-1:1
 Developing embedded applications

4 Finally, the main function is called:

For more information about each stage, see System startup and termination, page 135.
For more information about initialization of data, see Initialization at system startup,
page 89.

THE EXECUTION PHASE

The software of an embedded application is typically implemented as a loop which is
either interrupt-driven or uses polling for controlling external interaction or internal
events. For an interrupt-driven system, the interrupts are typically initialized at the
beginning of the main function.
In a system with real-time behavior and where responsiveness is critical, a multi-task
system might be required. This means that your application software should be
complemented with a real-time operating system. In this case, the RTOS and the
different tasks must also be initialized at the beginning of the main function.

THE TERMINATION PHASE

Typically, the execution of an embedded application should never end. If it does, you
must define a proper end behavior.
To terminate an application in a controlled way, either call one of the Standard C library
functions exit, _Exit, or abort, or return from main. If you return from main, the
exit function is executed, which means that C++ destructors for static and global
variables are called (C++ only) and all open files are closed.

53

AFE1_AFE2-1:1
Building applications—an overview

Of course, in case of incorrect program logic, the application might terminate in an

uncontrolled and abnormal way—a system crash.
For more information about this, see System termination, page 137.

Building applications—an overview

In the command line interface, the following line compiles the source file myfile.c
into the object file myfile.r43 using the default settings:
icc430 myfile.c

You must also specify some critical options, see Basic project configuration, page 54.
On the command line, the following line can be used for starting the linker:
xlink myfile.r43 myfile2.r43 -o a.d43 -f my_configfile.xcl -r

In this example, myfile.r43 and myfile2.r43 are object files, and

my_configfile.xcl is the linker configuration file. The option -o specifies the name
of the output file. The option -r is used for specifying the output format UBROF, which
can be used for debugging in C-SPY®.
Note: By default, the label where the application starts is __program_start. You can
use the -s command line option to change this.
When building a project, the IAR Embedded Workbench IDE can produce extensive
build information in the Build messages window. This information can be useful, for
example, as a base for producing batch files for building on the command line. You can
copy the information and paste it in a text file. To activate extensive build information,
right-click in the Build messages window, and select All on the context menu.

Basic project configuration

This section gives an overview of the basic settings needed to generate the best code for
the MSP430 device you are using. You can specify the options either from the command
line interface or in the IDE. On the command line, you must specify each option
separately, but if you use the IDE, many options will be set automatically, based on your
settings of some of the fundamental options.
You need to make settings for:
● Processor configuration
● Data model (only for MSP430X)
● Code model (only for MSP430X)
● Size of double floating-point type

IAR C/C++ Compiler User Guide

54 for MSP430

AFE1_AFE2-1:1
 Developing embedded applications

● Optimization settings
● Runtime environment, see Setting up the runtime environment, page 119
● Position-independent code and read-only data
● Customizing the XLINK configuration, see the chapter Linking your application.
In addition to these settings, you can use many other options and settings to fine-tune
the result even further. For information about how to set options and for a list of all
available options, see the chapter Compiler options and the IDE Project Management
and Building Guide, respectively.

PROCESSOR CONFIGURATION
To make the compiler generate optimum code, you should configure it for the MSP430
microcontroller you are using.

Core
The compiler supports both the MSP430 architecture that has 64 Kbytes of addressable
memory and the MSP430X architecture that has the extended instruction set and 1
Mbyte of addressable memory.
Use the --core={430|430X} option to select the architecture for which the code will
be generated.
In the IDE, choose Project>Options>General Options>Target and choose an
appropriate device from the Device drop-down list. The core option will then be
automatically selected.
Note: Device-specific configuration files for the linker and the debugger will also be
automatically selected.

Hardware multiplier
Some MSP430 devices contain a hardware multiplier. The IAR C/C++ Compiler for
MSP430 can generate code that accesses this unit. In addition, the runtime library
contains hardware multiplier-aware modules that can be used instead of the normal
arithmetical routines.
To direct the compiler to take advantage of the unit, choose Project>Options>General
Options>Target and choose a device from the Device drop-down menu that contains a
hardware multiplier unit.
To use the hardware multiplier, enable it on the command line using the --multiplier
(and in some cases also the--multiplier_location) option. You must also, in

55

AFE1_AFE2-1:1
Basic project configuration

addition to the runtime library object file, extend the linker command line with one of
these configuration files:
-f multiplier.xcl
-f multiplier32.xcl

For more information, see Hardware multiplier support, page 151.

DATA MODEL (MSP430X ONLY)

In the MSP430X architecture, there is a trade-off in how memory is accessed. You can
use 16-bit addressing which is cheaper but can only access the first 64 Kbytes of
memory, or 20-bit addressing which is often more expensive, but can access the full 1
Mbyte of memory.
In the compiler, you can control the trade-off between access methods by selecting a
data model. These data models are supported:
● The Small data model uses only 16-bit addressing, so it can access the first 64
Kbytes of memory. The 20-bit registers are treated as 16 bits wide. To save stack
space, the most significant 4 bits of the registers are not preserved across function
calls, including interrupt handlers. The only way to access the full 1-Mbyte memory
range is to use intrinsic functions.
● The Medium data model uses 16-bit addressing by default, but also allows 20-bit
addressing, so the full 1 Mbyte of memory can be accessed. When mandated by the
calling convention, the full 20 bits of the registers are preserved across function
calls.
● The Large data model uses 20-bit addressing by default, and allows 16-bit
addressing. The full 1 Mbyte of memory can be accessed.
The chapter Data storage covers data models in greater detail. The chapter also covers
how to override the default access method for individual variables.

CODE MODEL (MSP430X ONLY)

The compiler supports code models to control the call and return sequences. These code
models are available:
● The Small code model uses 16-bit instructions CALL and RET, and reaches 64
Kbytes of memory. Function pointers are 2 bytes.
● The Large code model uses 20-bit instructions CALLA and RETA, and reaches 1 MB
of memory. Function pointers are 4 bytes. This is the default code model.
The main differences between the code models is that the Small code model is slightly
faster and requires less runtime stack. However, code placement is restricted to the first
64 Kbytes.

IAR C/C++ Compiler User Guide

56 for MSP430

AFE1_AFE2-1:1
 Developing embedded applications

Note: The call and return sequences are different if --ropi is used.
For more information about the code models, see the chapter Functions.

SIZE OF DOUBLE FLOATING-POINT TYPE

Floating-point values are represented by 32- and 64-bit numbers in standard IEEE 754
format. If you use the compiler option --double={32|64}, you can choose whether
data declared as double should be represented with 32 bits or 64 bits. The data type
float is always represented using 32 bits.

OPTIMIZATION FOR SPEED AND SIZE

The compiler’s optimizer performs, among other things,
You can choose between several optimization levels, and for the highest level you can
choose between different optimization goals—size, speed, or balanced. Most
optimizations will make the application both smaller and faster. However, when this is
not the case, the compiler uses the selected optimization goal to decide how to perform
the optimization.
The optimization level and goal can be specified for the entire application, for individual
files, and for individual functions. In addition, some individual optimizations, such as
function inlining, can be disabled.
For information about compiler optimizations and for more information about efficient
coding techniques, see the chapter Efficient coding for embedded applications.

NORMAL OR POSITION-INDEPENDENT CODE

Most applications are designed to be placed at a fixed position in memory. However,
sometimes it is useful to instead not decide until at runtime where to place the
application. By enabling the compiler option --ropi, you can make the compiler
generate position-independent code and read-only data (ROPI). ROPI allows the
application image to execute correctly even if it is placed at a different location than
where it was linked. For more information, see Position-independent code and
read-only data, page 80.

57

AFE1_AFE2-1:1
Basic project configuration

IAR C/C++ Compiler User Guide

58 for MSP430

AFE1_AFE2-1:1
 Data storage
● Introduction

● Memory types (MSP430X only)

● Data models

● Storage of auto variables and parameters

● Dynamic memory on the heap

Introduction
The compiler supports MSP430 devices with both the MSP430 instruction set and the
MSP430X extended instruction set, which means that 64 Kbytes and 1 Mbyte of
continuous memory can be used, respectively.
Different types of physical memory can be placed in the memory range. A typical
application will have both read-only memory (ROM or flash) and read/write memory
(RAM). In addition, some parts of the memory range contain processor control registers
and peripheral units.
Some devices support FRAM, a memory type that can be written to like RAM, but
retains its contents after a power-down like traditional read-only memories. FRAM can
be partitioned to contain read-only segments and read/write segments.
The MSP430X architecture can access the lower 64 Kbyte using normal instructions and
the entire memory range using more expensive extended instructions. The compiler
supports this by means of memory types, where data16 memory corresponds to the
lower 64 Kbytes and the data20 memory the entire 1 Mbyte memory range. For more
information about this, see Memory types (MSP430X only), page 60.
Placing read-only (constant) data in data20 memory is useful for most MSP430X
devices. However, using data20 memory for read/write data only makes sense if the
device has RAM or FRAM memory above the first 64 Kbytes.

59

AFE1_AFE2-1:1
Memory types (MSP430X only)

DIFFERENT WAYS TO STORE DATA

In a typical application, data can be stored in memory in three different ways:
● Auto variables
All variables that are local to a function, except those declared static, are stored either
in registers or on the stack. These variables can be used as long as the function
executes. When the function returns to its caller, the memory space is no longer valid.
For more information, see Storage of auto variables and parameters, page 68.
● Global variables, module-static variables, and local variables declared static
In this case, the memory is allocated once and for all. The word static in this context
means that the amount of memory allocated for this kind of variables does not change
while the application is running. For more information, see Memory types (MSP430X
only), page 60.
● Dynamically allocated data
An application can allocate data on the heap, where the data remains valid until it is
explicitly released back to the system by the application. This type of memory is
useful when the number of objects is not known until the application executes.
Note: There are potential risks connected with using dynamically allocated data in
systems with a limited amount of memory, or systems that are expected to run for a
long time. For more information, see Dynamic memory on the heap, page 69.

Memory types (MSP430X only)

This section describes the concept of memory types used for accessing data by the
compiler. For each memory type, the capabilities and limitations are discussed.

INTRODUCTION TO MEMORY TYPES

The compiler uses different memory types to access data that is placed in different areas
of the memory. There are different methods for reaching memory areas, and they have
different costs when it comes to code space, execution speed, and register usage. The
access methods range from generic but expensive methods that can access the full
memory space, to cheap methods that can access limited memory areas. Each memory
type corresponds to one memory access method. If you map different memories—or
part of memories—to memory types, the compiler can generate code that can access
data efficiently.
For example, the memory accessed using 16-bit addressing is called data16 memory.
To choose a default memory type that your application will use, select a data model.
However, it is possible to specify—for individual variables or pointers—different
memory types. This makes it possible to create an application that can contain a large

IAR C/C++ Compiler User Guide

60 for MSP430

AFE1_AFE2-1:1
 Data storage

amount of data, and at the same time make sure that variables that are used often are
placed in memory that can be efficiently accessed.
Below is an overview of the memory types.

Data16
The data16 memory consists of the low 64 Kbytes of data memory. In hexadecimal
notation, this is the address range 0x0000-0xFFFF.
A pointer to data16 memory is 16 bits and occupies two bytes when stored in memory.
Direct accesses to data16 memory are performed using normal (non-extended)
instructions. This means a smaller footprint for the application, and faster execution at
runtime.

Data20
Using the data20 memory type, you can place the data objects anywhere in the entire
memory range 0x00000–0xFFFFF. This requires the extended instructions of the
MSP430X architecture, which are more expensive. Note that a pointer to data20
memory will occupy four bytes of memory, which is twice the amount needed for data16
memory.
Note: Data20 is not available in the Small data model.

USING DATA MEMORY ATTRIBUTES

The compiler provides a set of extended keywords, which can be used as data memory
attributes. These keywords let you override the default memory type for individual data
objects and pointers, which means that you can place data objects in other memory areas
than the default memory. This also means that you can fine-tune the access method for
each individual data object, which results in smaller code size.
This table summarizes the available memory types and their corresponding keywords:

Default in
Memory type Keyword Address range Pointer size
data model
Data16 __data16 0x0-0xFFFF 16 bits Small and
Medium
Data20 __data20 0x0-0xFFFFF 32 bits Large
Table 3: Memory types and their corresponding memory attributes

The keywords are only available if language extensions are enabled in the compiler.
In the IDE, language extensions are enabled by default.

61

AFE1_AFE2-1:1
Memory types (MSP430X only)

Use the -e compiler option to enable language extensions. See -e, page 278 for
additional information.
For more information about each keyword, see Descriptions of extended keywords, page
321.

Syntax for type attributes used on data objects

Type attributes use almost the same syntax rules as the type qualifiers const and
volatile. For example:

__data16 int i;
int __data16 j;

Both i and j are placed in data16 memory.

Unlike const and volatile, when a type attribute is used before the type specifier in
a derived type, the type attribute applies to the object, or typedef itself, except in
structure member declarations.

int __data16 * p; /* pointer to integer in data16 memory */

int * __data16 p; /* pointer in data16 memory */

__data16 int * p; /* pointer in data16 memory */

In all cases, if a memory attribute is not specified, an appropriate default memory type
is used, which depends on the data model in use.
Using a type definition can sometimes make the code clearer:
typedef __data16 int d16_int;
d16_int *q1;

d16_int is a typedef for integers in data16 memory. The variable q1 can point to such
integers.
You can also use the #pragma type_attributes directive to specify type attributes
for a declaration. The type attributes specified in the pragma directive are applied to the
data object or typedef being declared.
#pragma type_attribute=__data16
int * q2;

The variable q2 is placed in data16 memory.

For more examples of using memory attributes, see More examples, page 64.

IAR C/C++ Compiler User Guide

62 for MSP430

AFE1_AFE2-1:1
 Data storage

Type definitions
Storage can also be specified using type definitions. These two declarations are
equivalent:
/* Defines via a typedef */
typedef char __data20 D20Byte;
typedef D20Byte *D20BytePtr;
D20Byte aByte;
D20BytePtr aBytePointer;

/* Defines directly */
__data20 char aByte;
char __data20 *aBytePointer;

POINTERS AND MEMORY TYPES

Pointers are used for referring to the location of data. In general, a pointer has a type.
For example, a pointer that has the type int * points to an integer.
In the compiler, a pointer also points to some type of memory. The memory type is
specified using a keyword before the asterisk. For example, a pointer that points to an
integer stored in data20 memory is declared by:
int __data20 * myPtr;

Note that the location of the pointer variable myPtr is not affected by the keyword. In
the following example, however, the pointer variable myPtr2 is placed in data20
memory. Like myPtr, myPtr2 points to a character in data16 memory.
char __data16 * __data20 myPtr2;

For example, the functions in the standard library are all declared without explicit
memory types.

Differences between pointer types

A pointer must contain information needed to specify a memory location of a certain
memory type. This means that the pointer sizes are different for different memory types.
In the IAR C/C++ Compiler for MSP430, the size of the data16 and data20 pointers are
16 and 20 bits, respectively. However, when stored in memory they occupy two and four
bytes, respectively.
In the compiler, it is illegal to convert a data20 pointer to a data16 pointer without an
explicit cast.
For more information about pointers, see Pointer types, page 309.

63

AFE1_AFE2-1:1
Memory types (MSP430X only)

STRUCTURES AND MEMORY TYPES

For structures, the entire object is placed in the same memory type. It is not possible to
place individual structure members in different memory types.
In the example below, the variable gamma is a structure placed in data16 memory.
struct MyStruct
{
int mAlpha;
int mBeta;
};

__data16 struct MyStruct gamma;

This declaration is incorrect:

struct MyStruct
{
int mAlpha;
__data16 int mBeta; /* Incorrect declaration */
};

MORE EXAMPLES
The following is a series of examples with descriptions. First, some integer variables are
defined and then pointer variables are introduced. Finally, a function accepting a pointer
to an integer in data16 memory is declared. The function returns a pointer to an integer

IAR C/C++ Compiler User Guide

64 for MSP430

AFE1_AFE2-1:1
 Data storage

in data20 memory. It makes no difference whether the memory attribute is placed before
or after the data type.

int myA; A variable stored in default memory

determined by the data model in use.
int __data16 myB; A variable stored in data16 memory.
__data20 int myC; A variable stored in data20 memory.
int * myD; A pointer stored in default memory. The
pointer points to an integer in default memory.
int __data16 * myE; A pointer stored in default memory. The
pointer points to an integer in data16 memory.
int __data16 * __data20 myF; A pointer stored in data20 memory pointing to
an integer stored in data16 memory.
int __data20 * MyFunction( A declaration of a function that takes a
int __data16 *); parameter which is a pointer to an integer
stored in data16 memory. The function returns
a pointer to an integer stored in data20
memory.

C++ AND MEMORY TYPES

Instances of C++ classes are placed into a memory (just like all other objects) either
implicitly, or explicitly using memory type attributes or other IAR language extensions.
Non-static member variables, like structure fields, are part of the larger object and
cannot be placed individually into specified memories.
In non-static member functions, the non-static member variables of a C++ object can be
referenced via the this pointer, explicitly or implicitly. The this pointer is of the
default data pointer type unless class memory is used, see Using IAR attributes with
classes, page 207.
In the Medium data model, this means that unless class memory is used, objects of
classes with a member function can only be placed in the default memory type
(__data16).
Static member variables can be placed individually into a data memory in the same way
as free variables.
For more information about C++ classes, see Using IAR attributes with classes, page
207.

65

AFE1_AFE2-1:1
Data models

Data models
Data models are only available for the MSP430X architecture.
Use data models to specify in which part of memory the compiler should place static
and global variables by default. This means that the data model controls:
● The default memory type
● The default placement of static and global variables, and constant literals
● The placement of dynamically allocated data, for example data allocated with
malloc, or, in C++, the operator new
● The default pointer type
The data model specifies the default memory type. In the Small data model, only the
data16 memory type is available. In the Medium and Large data models, you can
explicitly override the default memory type for individual variables and pointers. For
information about how to specify a memory type for individual objects, see Using data
memory attributes, page 61.
Note: Your choice of data model does not affect the placement of code.

SPECIFYING A DATA MODEL

Three data models are implemented: Small, Medium, and Large. These models are
controlled by the --data_model option. Each model has a default memory type and a
default pointer size. If you do not specify a data model option, the compiler will use the
Small data model.
Your project can only use one data model at a time, and the same model must be used
by all user modules and all library modules. However, you can override the default
memory type for individual data objects and pointers by explicitly specifying a memory
attribute, see Using data memory attributes, page 61.
This table summarizes the different data models:

Data model name Default memory attribute Data20 available

Small __data16 No
Medium __data16 Yes
Large __data20 Yes
Table 4: Data model characteristics

See the IDE Project Management and Building Guide for information about setting
options in the IDE.

IAR C/C++ Compiler User Guide

66 for MSP430

AFE1_AFE2-1:1
 Data storage

Use the --data_model option to specify the data model for your project; see
--data_model, page 272.

The Small data model

The Small data model is designed to save stack space when you do not need to put any
data outside the low 64 Kbytes of memory. It uses the data16 memory type only. The
data20 memory type is not allowed. This means that normal (non-extended) instructions
are used for all memory accesses. However, the compiler can use extended instructions
when they are more efficient, for other types of operations, like for example shifts.
The 20-bit registers in the MSP430X architecture are treated as if they were 16 bits wide,
and the compiler assumes that the most significant 4 bits are never used. Only the least
significant 16 bits are preserved across function calls when mandated by the calling
convention. In practice, an interrupt handler could clear those upper 4 bits at any time.*
Note: There are ways to make interrupt handlers in the Small data model preserve the
full 20 bits of every register, see --save_reg20, page 297 and __save_reg20, page 329.
However, because these are rather inefficient, you should consider selecting the Medium
data model instead if you need the full 20 bits of registers to be preserved.
If the Small data model is used in combination with the Large code model, 20-bit
function pointers are passed as pairs of two 16-bit registers in the calling convention.
To access data outside the low 64 Kbytes of memory in the Small data model, you must
use intrinsic functions.

The Medium data model

The Medium data model provides good efficiency when most but not all data is placed
in the low 64 Kbytes of memory, and has a natural way to access the data that is outside
the low 64 Kbytes. It uses the data16 memory type by default, but you can use the data20
memory type through explicit overrides on individual variables and pointers. This
means that normal (non-extended) instructions are used for all memory accesses except
those where you have specified that the data could be placed outside the low 64 Kbytes
of memory.
The compiler is aware that the most significant 4 bits of the registers can contain valid
data, and preserves the full 20 bits across function calls when mandated by the calling
convention. Because of this, the Medium data model often uses more stack space than
the Small data model.
Function pointers are always passed in a single register in the calling convention,
regardless of the selected code model.

67

AFE1_AFE2-1:1
Storage of auto variables and parameters

The Large data model

The Large data model automatically allows data to be placed outside the low 64 Kbytes
of memory, but requires careful tuning to be really efficient. It uses the data20 memory
type by default, but you can use the data16 memory type through explicit overrides on
individual variables and pointers. This means that extended instructions will be used for
most memory accesses, unless you have specified that the data will be placed in the low
64 Kbytes.
The compiler is aware that the most significant 4 bits of the registers can contain valid
data, and preserves the full 20 bits across function calls when mandated by the calling
convention.
Function pointers are always passed in a single register in the calling convention,
regardless of the selected code model.

Storage of auto variables and parameters

Variables that are defined inside a function—and not declared static—are named auto
variables by the C standard. A few of these variables are placed in processor registers,
while the rest are placed on the stack. From a semantic point of view, this is equivalent.
The main differences are that accessing registers is faster, and that less memory is
required compared to when variables are located on the stack.
Auto variables can only live as long as the function executes—when the function
returns, the memory allocated on the stack is released.

THE STACK
The stack can contain:
● Local variables and parameters not stored in registers
● Temporary results of expressions
● The return value of a function (unless it is passed in registers)
● Processor state during interrupts
● Processor registers that should be restored before the function returns (callee-save
registers).
The stack is a fixed block of memory, divided into two parts. The first part contains
allocated memory used by the function that called the current function, and the function
that called it, etc. The second part contains free memory that can be allocated. The
borderline between the two areas is called the top of stack and is represented by the stack
pointer, which is a dedicated processor register. Memory is allocated on the stack by
moving the stack pointer.

IAR C/C++ Compiler User Guide

68 for MSP430

AFE1_AFE2-1:1
 Data storage

A function should never refer to the memory in the area of the stack that contains free
memory. The reason is that if an interrupt occurs, the called interrupt function can
allocate, modify, and—of course—deallocate memory on the stack.
See also Stack considerations, page 221 and Setting up stack memory, page 105.

Advantages
The main advantage of the stack is that functions in different parts of the program can
use the same memory space to store their data. Unlike a heap, a stack will never become
fragmented or suffer from memory leaks.
It is possible for a function to call itself either directly or indirectly—a recursive
function—and each invocation can store its own data on the stack.

Potential problems
The way the stack works makes it impossible to store data that is supposed to live after
the function returns. The following function demonstrates a common programming
mistake. It returns a pointer to the variable x, a variable that ceases to exist when the
function returns.
int *MyFunction()
{
int x;
/* Do something here. */
return &x; /* Incorrect */
}

Another problem is the risk of running out of stack space. This will happen when one
function calls another, which in turn calls a third, etc., and the sum of the stack usage of
each function is larger than the size of the stack. The risk is higher if large data objects
are stored on the stack, or when recursive functions are used.

Dynamic memory on the heap

Memory for objects allocated on the heap will live until the objects are explicitly
released. This type of memory storage is very useful for applications where the amount
of data is not known until runtime.
In C, memory is allocated using the standard library function malloc, or one of the
related functions calloc and realloc. The memory is released again using free.
In C++, a special keyword, new, allocates memory and runs constructors. Memory
allocated with new must be released using the keyword delete.

69

AFE1_AFE2-1:1
Dynamic memory on the heap

The compiler supports heaps in more than one memory types:

Used by default in
Memory type Memory attribute Section name
data model
data16 __data16 DATA16_HEAP Small and Medium
data20 __data20 DATA20_HEAP Large
Table 5: Heaps supported in memory types

In DLIB, to use a specific heap, add the memory attribute in front of malloc, free,
alloc, and realloc, for example __data16_malloc. The default functions will use
of the specific heap variants, depending on project settings such as data model.
For information about how to set up the size for heap memory, see Setting up heap
memory, page 106.

POTENTIAL PROBLEMS
Applications that use heap-allocated data objects must be carefully designed, as it is
easy to end up in a situation where it is not possible to allocate objects on the heap.
The heap can become exhausted if your application uses too much memory. It can also
become full if memory that no longer is in use was not released.
For each allocated memory block, a few bytes of data for administrative purposes is
required. For applications that allocate a large number of small blocks, this
administrative overhead can be substantial.
There is also the matter of fragmentation; this means a heap where small sections of free
memory is separated by memory used by allocated objects. It is not possible to allocate
a new object if no piece of free memory is large enough for the object, even though the
sum of the sizes of the free memory exceeds the size of the object.
Unfortunately, fragmentation tends to increase as memory is allocated and released. For
this reason, applications that are designed to run for a long time should try to avoid using
memory allocated on the heap.

IAR C/C++ Compiler User Guide

70 for MSP430

AFE1_AFE2-1:1
 Functions
● Function-related extensions

● Code models (MSP430X only)

● Primitives for interrupts, concurrency, and OS-related programming

● Execution in RAM

● Position-independent code and read-only data

● Inlining functions

Function-related extensions
In addition to supporting Standard C, the compiler provides several extensions for
writing functions in C. Using these, you can:
● Control call and return sequences
● Execute functions in RAM
● Use primitives for interrupts, concurrency, and OS-related programming
● Control function inlining
● Facilitate function optimization
● Access hardware features.
The compiler uses compiler options, extended keywords, pragma directives, and
intrinsic functions to support this.
For more information about optimizations, see Efficient coding for embedded
applications, page 233. For information about the available intrinsic functions for
accessing hardware operations, see the chapter Intrinsic functions.

Code models (MSP430X only)

Use code models to specify how functions are called. Technically, the code models
control the following:
● The instruction sequences used for calling and returning from functions
● The memory range where functions can be stored

71

AFE1_AFE2-1:1
Code models (MSP430X only)

● The size of function pointers.

Your project can only use one code model at a time, and the same model must be used
by all user modules and all library modules.
Note: Your choice of code model does not affect the placement of data.
These code models are available:
Code model name Instructions Memory range Function pointer size
Small CALL, RET 64 Kbytes 2 bytes
Large (default) CALLA, RETA 1 Mbyte 4 bytes
Table 6: Code models

If you do not specify a code model, the compiler will use the Large code model as
default.
See the IDE Project Management and Building Guide for information about specifying
a code model in the IDE.
Use the --code_model option to specify the code model for your project; see
--code_model, page 270.

THE SMALL CODE MODEL

The Small code model uses standard 16-bit instructions for call and return. Functions
must be placed in the first 64 Kbytes of memory.
The function pointers are 2 bytes in memory.

THE LARGE CODE MODEL

The Large code model uses extended 20-bit instructions for call and return. Functions
can be placed anywhere in the 1 Mbyte of memory.
In the Small data model, a function pointer is treated as a 32-bit value. It occupies 4
bytes of memory and a pair of registers is required to hold it.
In the Medium and Large data models, a function pointer is a 20-bit value. In memory,
it occupies 4 bytes but it fits into one 20-bit register.

COMPARING THE CODE MODELS

The main difference between the code models is that the Small code model is slightly
faster, it requires less runtime stack, and pointers are smaller and require less memory.
However, in the Small code model code placement is restricted to the first 64 Kbytes.

IAR C/C++ Compiler User Guide

72 for MSP430

AFE1_AFE2-1:1
 Functions

Primitives for interrupts, concurrency, and OS-related programming

The IAR C/C++ Compiler for MSP430 provides the following primitives related to
writing interrupt functions, concurrent functions, and OS-related functions:
● The extended keywords: __interrupt, __task, __monitor, __raw,
__save_reg20
● The pragma directives: #pragma no_epilogue, #pragma vector
● The intrinsic functions: __enable_interrupt, __disable_interrupt.
● The compiler option --save_reg20.

INTERRUPT FUNCTIONS
In embedded systems, using interrupts is a method for handling external events
immediately; for example, detecting that a button was pressed.

Interrupt service routines

In general, when an interrupt occurs in the code, the microcontroller immediately stops
executing the code it runs, and starts executing an interrupt routine instead. It is
important that the environment of the interrupted function is restored after the interrupt
is handled (this includes the values of processor registers and the processor status
register). This makes it possible to continue the execution of the original code after the
code that handled the interrupt was executed.
The MSP430 microcontroller supports many interrupt sources. For each interrupt
source, an interrupt routine can be written. Each interrupt routine is associated with a
vector number, which is specified in the MSP430 microcontroller documentation from
the chip manufacturer. If you want to handle several different interrupts using the same
interrupt routine, you can specify several interrupt vectors.

Interrupt vectors and the interrupt vector table

The interrupt vector is the offset into the interrupt vector table.
For the MSP430 microcontroller, the interrupt vector table can for example contain 16
vectors and the table starts at the address 0xFFE0. However, some devices contain more
than 16 vectors, in which case the vectors start at a lower address. For example, if the
device has 32 vectors, the table starts at address 0xFFC0.
The interrupt vectors are placed in the segment INTVEC. The last entry in the table
contains the reset vector, which is placed in a separate linker segment—RESET.
If a vector is specified in the definition of an interrupt function, the processor interrupt
vector table is populated. It is also possible to define an interrupt function without a

73

AFE1_AFE2-1:1
Primitives for interrupts, concurrency, and OS-related programming

vector. This is useful if an application is capable of populating or changing the interrupt

vector table at runtime.
The header files iodevice.h and mspdevice.h, where device corresponds to the
selected device, contain predefined names for the existing interrupt vectors.

Defining an interrupt function—an example

To define an interrupt function, the __interrupt keyword and the #pragma vector
directive can be used. For example:
#pragma vector = TIMERA0_VECTOR /* Defined in I/O header file */
__interrupt void MyInterruptRoutine(void)
{
/* Do something */
}

Note: An interrupt function must have the return type void, and it cannot specify any
parameters.

Interrupt and C++ member functions

Only static member functions can be interrupt functions. When a non-static member
function is called, it must be applied to an object. When an interrupt occurs and the
interrupt function is called, there is no object available to apply the member function to.

Preventing registers from being saved at function entrance

As noted, the interrupt function preserves the content of all used processor register at the
entrance and restores them at exit. However, for some very special applications, it can
be desirable to prevent the registers from being saved at function entrance.
This can be accomplished by the use of the extended keyword __raw, for example:
__raw __interrupt void my_interrupt_function()

This creates an interrupt service routine where you must make sure that the code within
the routine does not affect any of the registers used by the interrupted environment.
Typically, this is useful for applications that have an empty foreground loop and use
interrupt routines to perform all work.
Note: The same effect can be achieved for normal functions by using the __task
keyword.

Interrupt Vector Generator interrupt functions

The compiler provides a way to write very efficient interrupt service routines for the
modules that has Interrupt Vector Generators, this includes Timer A (TAIV), Timer B
(TBIV), the I2C module (I2CIV), and the ADC12 module.

IAR C/C++ Compiler User Guide

74 for MSP430

AFE1_AFE2-1:1
 Functions

The interrupt vector register contains information about the interrupt source, and the
interrupt service routine normally uses a switch statement to find out which interrupt
source issued the interrupt. To help the compiler generate optimal code for the switch
statement, the intrinsic function __even_in_range can be used. This example defines
a Timer A interrupt routine:
#pragma vector=TIMERA1_VECTOR
__interrupt void Timer_A1_ISR(void)
{
switch (__even_in_range(TAIV, 10))
{
case 2: P1POUT ˆ= 0x04;
break;
case 4: P1POUT ˆ= 0x02;
break;
case 10: P1POUT ˆ= 0x01;
break;
}
}

The intrinsic function __even_in_range requires two parameters, the interrupt vector
register and the last value in the allowed range, which in this example is 10. The effect
of the intrinsic function is that the generated code can only handle even values within
the given range, which is exactly what is required in this case as the interrupt vector
register for Timer A can only be 0, 2, 4, 6, 8, or 10.
If the __even_in_range intrinsic function is applied to any other value, the effect is
undefined and the application will most likely fail.
For more information about the intrinsic keyword, see __even_in_range, page 362.

Interrupt functions for the MSP430X architecture

When compiling for the MSP430X architecture, all interrupt functions are automatically
placed in the segment ISR_CODE, which must be located in the lower 64 Kbytes of
memory. If you are using one of the linker configuration files for an MSP430X device
that are delivered with the product, the segment will be correctly located.
In the Small data model, interrupt routines preserve the low 16 bits of all registers.
However, the upper 4 bits could be cleared. Therefore, if you have assembler routines
that use the upper 4 bits of the registers, you must use either the __save_reg20
keyword on all your interrupt functions, alternatively the --save_reg20 compiler
option. This will ensure that the interrupt functions will save and restore all 20 bits of
any 20-bit registers that are used. The drawback is that the entry and leave sequences
will become slower and consume more stack space.
Note: If a __save_reg20 function, compiled using either the --lock_R4 or the
--lock_R5 option, calls another function that is not __save_reg20 declared and does

75

AFE1_AFE2-1:1
Primitives for interrupts, concurrency, and OS-related programming

not lock R4/R5, the upper four bits of R4/R5 might be destroyed. For this reason, it is not
recommended to use different settings of the --lock_R4/R5 option for different
modules.

MONITOR FUNCTIONS
A monitor function causes interrupts to be disabled during execution of the function. At
function entry, the status register is saved and interrupts are disabled. At function exit,
the original status register is restored, and thereby the interrupt status that existed before
the function call is also restored.
To define a monitor function, you can use the __monitor keyword. For more
information, see __monitor, page 324.
Avoid using the __monitor keyword on large functions, since the interrupt will
otherwise be turned off for a significant period of time.

Example of implementing a semaphore in C

In the following example, a binary semaphore—that is, a mutex—is implemented using
one static variable and two monitor functions. A monitor function works like a critical
region, that is no interrupt can occur and the process itself cannot be swapped out. A
semaphore can be locked by one process, and is used for preventing processes from
simultaneously using resources that can only be used by one process at a time, for
example a USART. The __monitor keyword assures that the lock operation is atomic;
in other words it cannot be interrupted.

IAR C/C++ Compiler User Guide

76 for MSP430

AFE1_AFE2-1:1
 Functions

/* This is the lock-variable. When non-zero, someone owns it. */

static volatile unsigned int sTheLock = 0;

/* Function to test whether the lock is open, and if so take it.

* Returns 1 on success and 0 on failure.
*/

__monitor int TryGetLock(void)

{
if (sTheLock == 0)
{
/* Success, nobody has the lock. */

sTheLock = 1;
return 1;
}
else
{
/* Failure, someone else has the lock. */

return 0;
}
}

/* Function to unlock the lock.

* It is only callable by one that has the lock.
*/

__monitor void ReleaseLock(void)

{
sTheLock = 0;
}

/* Function to take the lock. It will wait until it gets it. */

void GetLock(void)
{
while (!TryGetLock())
{
/* Normally, a sleep instruction is used here. */
}
}

77

AFE1_AFE2-1:1
Primitives for interrupts, concurrency, and OS-related programming

/* An example of using the semaphore. */

void MyProgram(void)
{
GetLock();

/* Do something here. */

ReleaseLock();
}

Example of implementing a semaphore in C++

In C++, it is common to implement small methods with the intention that they should be
inlined. However, the compiler does not support inlining of functions and methods that
are declared using the __monitor keyword.
In the following example in C++, an auto object is used for controlling the monitor
block, which uses intrinsic functions instead of the __monitor keyword.
#include <intrinsics.h>

/* Class for controlling critical blocks. */

class Mutex
{
public:
Mutex()
{
// Get hold of current interrupt state.
mState = __get_interrupt_state();

// Disable all interrupts.

__disable_interrupt();
}

~Mutex()
{
// Restore the interrupt state.
__set_interrupt_state(mState);
}

IAR C/C++ Compiler User Guide

78 for MSP430

AFE1_AFE2-1:1
 Functions

private:
__istate_t mState;
};

class Tick
{
public:
// Function to read the tick count safely.
static long GetTick()
{
long t;

// Enter a critical block.

{
Mutex m;

// Get the tick count safely,

t = smTickCount;
}
// and return it.
return t;
}

private:
static volatile long smTickCount;
};

volatile long Tick::smTickCount = 0;

extern void DoStuff();

void MyMain()
{
static long nextStop = 100;

if (Tick::GetTick() >= nextStop)

{
nextStop += 100;
DoStuff();
}
}

Execution in RAM
The __ramfunc keyword makes a function execute in RAM. The function is copied
from ROM to RAM by cstartup, see System startup and termination, page 135.

79

AFE1_AFE2-1:1
Position-independent code and read-only data

The keyword is specified before the return type:

__ramfunc void foo(void);

If the whole memory area used for code and constants is disabled—for example, when
the whole flash memory is being erased—only functions and data stored in RAM can be
used. Interrupts must be disabled unless the interrupt vector and the interrupt service
routines are also stored in RAM.

Position-independent code and read-only data

Most applications are designed to be placed at a fixed position in memory. The exact
placement of each function and variable is decided at link time. However, sometimes it
is useful to instead decide at runtime where to place the application, for example in
certain systems where applications are loaded dynamically.
The compiler supports a feature known as position-independent code and read-only
data (ROPI). When the --ropi option is specified, the compiler generates code that
uses PC-relative references for addressing code and read-only data. This means that,
even though the linker places the code and read-only data at fixed locations, the
application can still be executed correctly when the linked image is placed at a different
address than where it was linked.
Note: Only functions and read-only data are affected—variables in RAM are never
position-independent. This usually means that only one ROPI application at a time can
execute.

DRAWBACKS AND LIMITATIONS

There are some drawbacks and limitations to bear in mind when using ROPI:
● The code generated for function calls and accesses to read-only data will be
somewhat larger
● Data initialization at startup might be somewhat slower, and the initialization data
might be somewhat larger
● Read-only global or static pointer variables that point to read-only data are not
supported
● C++ is not supported
● Interrupt handlers that use the #pragma vector directive are not handled
automatically
● The CLIB runtime library cannot be used
● The object attributes __ramfunc and __persistent are not supported.

IAR C/C++ Compiler User Guide

80 for MSP430

AFE1_AFE2-1:1
 Functions

Note: In some cases, there is an alternative to ROPI that avoids these limitations and
drawbacks: If there is only a small number of possible placements for the application,
you can compile the application without --ropi and link it multiple times, once for
each possible placement. Then you can choose the correct image at load time. When
applicable, this approach makes better use of the available hardware resources than
using ROPI.

INITIALIZATION OF POINTERS
In a ROPI application, the actual addresses of read-only data variables are only known
at runtime. A pointer to data always holds the actual address, so that it can be used
efficiently in indirect and indexed addressing modes. This means that pointers to
read-only data cannot be initialized statically (by copying from ROM at startup). For
non-constant global and static pointer variables, the compiler automatically rewrites
static initializations to dynamic ones, where the actual address is computed at program
startup. This rewriting can be disabled if you prefer the compiler to issue an error
message at compile-time, see --no_rw_dynamic_init, page 287.
Unlike data pointers, function pointers in a ROPI application hold the linked address of
a function, and the actual address is only computed when the function is called. This
means that function pointers work as usual without limitations.

NON-ROPI CODE IN ROPI SYSTEMS

In a system with ROPI applications, there might be a small amount of non-ROPI code
that handles startup, dynamic loading of applications, shared firmware functions, etc.
Such code must be compiled and linked separately from the ROPI applications. You can
use the function type attribute __no_pic to inform the compiler that a function pointer
holds the actual address of a non-ROPI function. This allows a ROPI application to call
non-ROPI functions via __no_pic function pointers. See __no_pic, page 326.

Inlining functions
Function inlining means that a function, whose definition is known at compile time, is
integrated into the body of its caller to eliminate the overhead of the function call. This
optimization, which is performed at optimization level High, normally reduces
execution time, but might increase the code size. The resulting code might become more
difficult to debug. Whether the inlining actually occurs is subject to the compiler’s
heuristics.
The compiler heuristically decides which functions to inline. Different heuristics are
used when optimizing for speed, size, or when balancing between size and speed.
Normally, code size does not increase when optimizing for size.

81

AFE1_AFE2-1:1
Inlining functions

C VERSUS C++ SEMANTICS

In C++, all definitions of a specific inline function in separate translation units must be
exactly the same. If the function is not inlined in one or more of the translation units,
then one of the definitions from these translation units will be used as the function
implementation.
In C, you must manually select one translation unit that includes the non-inlined version
of an inline function. You do this by explicitly declaring the function as extern in that
translation unit. If you declare the function as extern in more than one translation unit,
the linker will issue a multiple definition error. In addition, in C, inline functions cannot
refer to static variables or functions.
For example:
// In a header file.
static int sX;
inline void F(void)
{
//static int sY; // Cannot refer to statics.
//sX; // Cannot refer to statics.
}

// In one source file.

// Declare this F as the non-inlined version to use.
extern inline void F();

FEATURES CONTROLLING FUNCTION INLINING

There are several mechanisms for controlling function inlining:
● The inline keyword advises the compiler that the function defined immediately
after the directive should be inlined.
If you compile your function in C or C++ mode, the keyword will be interpreted
according to its definition in Standard C or Standard C++, respectively.
The main difference in semantics is that in Standard C you cannot (in general) simply
supply an inline definition in a header file. You must supply an external definition in
one of the compilation units, by designating the inline definition as being external in
that compilation unit.
● #pragma inline is similar to the inline keyword, but with the difference that the
compiler always uses C++ inline semantics.
By using the #pragma inline directive you can also disable the compiler’s
heuristics to either force inlining or completely disable inlining. For more
information, see inline, page 342.

IAR C/C++ Compiler User Guide

82 for MSP430

AFE1_AFE2-1:1
 Functions

● --use_c++_inline forces the compiler to use C++ semantics when compiling a

Standard C source code file.
● --no_inline, #pragma optimize=no_inline, and #pragma inline=never
all disable function inlining. By default, function inlining is enabled at optimization
level High.
The compiler can only inline a function if the definition is known. Normally, this is
restricted to the current translation unit. However, when the --mfc compiler option for
multi-file compilation is used, the compiler can inline definitions from all translation
units in the multi-file compilation unit. For more information, see Multi-file compilation
units, page 241.
For more information about the function inlining optimization, see Function inlining,
page 244.

83

AFE1_AFE2-1:1
Inlining functions

IAR C/C++ Compiler User Guide

84 for MSP430

AFE1_AFE2-1:1
 Linking overview
● Linking—an overview

● Segments and memory

● The linking process in detail

● Placing code and data—the linker configuration file

● Initialization at system startup

● Stack usage analysis

Linking—an overview
The IAR XLINK Linker is a powerful, flexible software tool for use in the development
of embedded applications. It is equally well suited for linking small, single-file, absolute
assembler programs as it is for linking large, relocatable, multi-module, C/C++, or
mixed C/C++ and assembler programs.
The linker combines one or more relocatable object files—produced by the IAR
Systems compiler or assembler—with required parts of object libraries to produce an
executable image containing machine code for the microcontroller you are using.
XLINK can generate more than 30 industry-standard loader formats, in addition to the
proprietary format UBROF which is used by the C-SPY debugger.
The linker will automatically load only those library modules that are actually needed
by the application you are linking. Furthermore, the linker eliminates segment parts that
are not required. During linking, the linker performs a full C-level type checking across
all modules.
The linker uses a configuration file where you can specify separate locations for code
and data areas of your target system memory map.
The final output produced by the linker is an absolute, target-executable object file that
can be downloaded to the microcontroller, to C-SPY, or to a compatible hardware
debugging probe. Optionally, the output file can contain debug information depending
on the output format you choose.
To handle libraries, the library tools XAR and XLIB can be used.

85

AFE1_AFE2-1:1
Segments and memory

Segments and memory

In an embedded system, there might be many different types of physical memory. Also,
it is often critical where parts of your code and data are located in the physical memory.
For this reason it is important that the development tools meet these requirements.

WHAT IS A SEGMENT?
A segment is a container for pieces of data or code that should be mapped to a location
in physical memory. Each segment consists of one or more segment parts. Normally,
each function or variable with static storage duration is placed in its own segment part.
A segment part is the smallest linkable unit, which allows the linker to include only
those segment parts that are referred to. A segment can be placed either in RAM or in
ROM. Segments that are placed in RAM generally do not have any content, they only
occupy space.
Note: Here, ROM memory means all types of read-only memory, including flash
memory.
The compiler uses several predefined segments for different purposes. Each segment is
identified by a name that typically describes the contents of the segment, and has a
segment memory type. In addition to the predefined segments, you can also define your
own segments.
At compile time, the compiler assigns code and data to the various segments. The IAR
XLINK Linker is responsible for placing the segments in the physical memory range, in
accordance with the rules specified in the linker configuration file. Ready-made linker
configuration files are provided, but, if necessary, they can be modified according to the
requirements of your target system and application. It is important to remember that,
from the linker's point of view, all segments are equal; they are simply named parts of
memory.

Segment memory type

Each segment always has an associated segment memory type. In some cases, an
individual segment has the same name as the segment memory type it belongs to, for
example CODE. Make sure not to confuse the segment name with the segment memory
type in those cases.
XLINK supports more segment memory types than the ones described above. However,
they exist to support other types of microcontrollers.
For more information about individual segments, see the chapter Segment reference.

IAR C/C++ Compiler User Guide

86 for MSP430

AFE1_AFE2-1:1
 Linking overview

The linking process in detail

The relocatable modules in object files and libraries, produced by the IAR compiler and
assembler, cannot be executed as is. To make an application executable, the object files
must be linked.
The IAR XLINK Linker is used for the link process. It normally performs the following
procedure (note that some of the steps can be turned off by command line options or by
directives in the linker configuration file):
● Determines which modules to include in the application. Program modules are
always included. Library modules are only included if they provide a definition for
a global symbol that is referenced from an included module. If the object files
containing library modules contain multiple definitions of variables or functions,
only the first definition will be included. This means that the linking order of the
object files is important.
● Determines which segment parts from the included modules to include in the
application. Only those segments that are actually needed by the application are
included. There are several ways to determine of which segment parts that are
needed, for example, the __root object attribute, the #pragma required
directive, and the -g linker option.
● Divides each segment that will be initialized by copying into two segments, one for
the ROM part and one for the RAM part. The RAM part contains the label and the
ROM part the actual bytes. The bytes are conceptually linked as residing in RAM.
● Determines where to place each segment according to the segment placement
directives in the linker configuration file.
● Produces an absolute file that contains the executable image and any debug
information. The contents of each needed segment in the relocatable input files is
calculated using the relocation information supplied in its file and the addresses
determined when placing segments. This process can result in one or more range
errors if some of the requirements for a particular segment are not met, for instance
if placement resulted in the destination address for a PC-relative jump instruction
being out of range for that instruction.
● Optionally, produces a map file that lists the result of the segment placement, the
address of each global symbol, and finally, a summary of memory usage for each
module.

87

AFE1_AFE2-1:1
Placing code and data—the linker configuration file

This illustration shows the linking process:

During the linking, XLINK might produce error messages and optionally a map file. In
the map file you can see the result of the actual linking and is useful for understanding
why an application was linked the way it was, for example, why a segment part was
included. If a segment part is not included although you expect it to be, the reason is
always that the segment part was not referenced to from an included part.
Note: To inspect the actual content of the object files, use XLIB. See the IAR Linker and
Library Tools Reference Guide.

Placing code and data—the linker configuration file

The placement of segments in memory is performed by the IAR XLINK Linker. It uses
a linker configuration file that contains command line options which specify the
locations where the segments can be placed, thereby assuring that your application fits
on the target microcontroller. To use the same source code with different devices, just
rebuild the code with the appropriate linker configuration file.
In particular, the linker configuration file specifies:
● The placement of segments in memory
● The maximum stack size
● The maximum heap size.

IAR C/C++ Compiler User Guide

88 for MSP430

AFE1_AFE2-1:1
 Linking overview

The file consists of a sequence of linker commands. This means that the linking process
will be governed by all commands in sequence.

THE CONTENTS OF THE LINKER CONFIGURATION FILE

Among other things, the linker configuration file contains three different types of
XLINK command line options:
● The CPU used:
-cmsp430
This specifies your target microcontroller. (It is the same for both the MSP430 and
the MSP430X architecture.)
● Definitions of constants used in the file. These are defined using the XLINK option
-D. Symbols defined using -D can also be accessed from your application.
● The placement directives (the largest part of the linker configuration file). Segments
can be placed using the -Z and -P options. The former will place the segment parts
in the order they are found, while the latter will try to rearrange them to make better
use of the memory. The -P option is useful when the memory where the segment
should be placed is not continuous.
In the linker configuration file, numbers are generally specified in hexadecimal format.
However, neither the prefix 0x nor the suffix h is necessarily used.
Note: The supplied linker configuration file includes comments explaining the contents.
For more information about the linker configuration file and how to customize it, see
Linking considerations, page 101.
See also the IAR Linker and Library Tools Reference Guide.

Initialization at system startup

In Standard C, all static variables—variables that are allocated at a fixed memory
address—must be initialized by the runtime system to a known value at application
startup. Static variables can be divided into these categories:
● Variables that are initialized to a non-zero value
● Variables that are initialized to zero
● Variables that are located by use of the @ operator or the #pragma location
directive
● Variables that are declared as const and therefore can be stored in ROM
● Variables defined with the __no_init keyword, meaning that they should not be
initialized at all.

89

AFE1_AFE2-1:1
Initialization at system startup

STATIC DATA MEMORY SEGMENTS

The compiler generates a specific type of segment for each type of variable
initialization.
The names of the segments consist of two parts—the segment group name and a suffix—
for instance, DATA16_Z. There is a segment group for each memory type, where each
segment in the group holds different categories of declared data. The names of the
segment groups are derived from the memory type and the corresponding keyword, for
example DATA16 and __data16.
Some of the declared data is placed in non-volatile memory, for example ROM/flash,
and some of the data is placed in RAM. For this reason, it is also important to know the
XLINK segment memory type of each segment. For more information about segment
memory types, see Segment memory type, page 86.
This table summarizes the different suffixes, which XLINK segment memory type they
are, and which category of declared data they denote:

Categories of Segment
Source Segment type Segment name*
declared data content
Zero-initialized int i; Read/write MEMATTR_Z None
data data, zero-init
Zero-initialized int i = 0; Read/write MEMATTR_Z None
data data, zero-init
Initialized data int i = 6; Read/write MEMATTR_I None
(non-zero) data
Initialized data int i = 6; Read-only data MEMATTR_ID Initializer data
(non-zero) for
MEMATTR_I
Constants const int i = 6; Read-only data MEMATTR_C The constant
Persistent data __persistent int Read-only MEMATTR_P The constant
i = 6; data†
Non-initialized __no_init int Read/write MEMATTR_AN None
absolute i @ 0x200; data
addressed data
Constant const int Read-only data MEMATTR_AC The constant
absolute i @ 0x200 =
addressed data 10000;
Non-initialized __no_init int i; Read/write MEMATTR_N None
data data
Table 7: segments holding initialized data

IAR C/C++ Compiler User Guide

90 for MSP430

AFE1_AFE2-1:1
 Linking overview

* The actual segment group name—MEMATTR—depends on the memory where the

variable is placed. See Memory types (MSP430X only), page 60.
† Only read-only segments can contain data, even though the application can write to
--persistent data.

For more information about each segment, see the chapter Segment reference.

THE INITIALIZATION PROCESS

Initialization of data is handled by the system startup code. If you add more segments,
you must update the system startup code accordingly.
To configure the initialization of variables, you must consider these issues:
● Segments that should be zero-initialized should only be placed in RAM.
● Segments that should be initialized, except for zero-initialized segments:
The system startup code initializes the non-zero variables by copying a block of
ROM to the location of the variables in RAM. This means that the data in the ROM
segment with the suffix ID is copied to the corresponding I segment.
This works when both segments are placed in continuous memory. However, if one
of the segments is divided into smaller pieces, it is very important that:
● The other segment is divided in exactly the same way
● It is legal to read and write the memory that represents the gaps in the sequence.
● Segments that contain constants do not need to be initialized; they should only be
placed in flash/ROM
● Segments holding __no_init declared variables should not be initialized.
● Finally, global C++ object constructors are called.
For more information about and examples of how to configure the initialization, see
Linking considerations, page 101.

Stack usage analysis

This section describes how to perform a stack usage analysis using the linker.
In the 430\src directory, you can find an example project that demonstrates stack
usage analysis.

INTRODUCTION TO STACK USAGE ANALYSIS

Under the right circumstances, the linker can accurately calculate the maximum stack
usage for each call graph, starting from the program start, interrupt functions, tasks etc.
(each function that is not called from another function, in other words, the root).

91

AFE1_AFE2-1:1
Stack usage analysis

If you enable stack usage analysis, a stack usage chapter will be added to the linker map
file, listing for each call graph root the particular call chain which results in the
maximum stack depth.
The analysis is only accurate if there is accurate stack usage information for each
function in the application.
In general, the compiler will generate this information for each C function, but if there
are indirect calls—calls using function pointers—in your application, you must supply
a list of possible functions that can be called from each calling function.
If you use a stack usage control file, you can also supply stack usage information for
functions in modules that do not have stack usage information.
You can use the check that directive in your stack usage control file to check that the
stack usage calculated by the linker does not exceed the stack space you have allocated.

PERFORMING A STACK USAGE ANALYSIS

1 Enable stack usage analysis:
In the IDE, choose Project>Options>Linker>Stack Usage>Enable stack usage
analysis.
On the command line, use the linker option --enable_stack_usage.
See the IAR Linker and Library Tools Reference Guide for information about the linker
option --enable_stack_usage.
2 Enable the linker map file:
In the IDE, choose Project>Options>Linker>List>Generate linker listing

On the command line, use the linker option -l

3 Link your project.

Note: The linker will issue warnings related to stack usage under certain circumstances,
see Situations where warnings are issued, page 97.
4 Review the linker map file, which now contains a stack usage chapter with a summary
of the stack usage for each call graph root. For more information, see Result of an
analysis—the map file contents, page 93.
5 For more details, analyze the call graph log, see Call graph log, page 97.
Note: There are limitations and sources of inaccuracy in the analysis, see Limitations,
page 96.

IAR C/C++ Compiler User Guide

92 for MSP430

AFE1_AFE2-1:1
 Linking overview

You might need to specify more information to the linker to get a more representative
result. See Specifying additional stack usage information, page 95
In the IDE, choose Project>Options>Linker>Stack Usage>Enable stack usage
analysis>Control file.
On the command line, use the linker option --stack_usage_control.
See the IAR Linker and Library Tools Reference Guide for information about the linker
option --stack_usage_control.
6 To add an automatic check that you have allocated memory enough for the stack, use
the check that directive in your stack usage control file. For example, assuming a
stack segment named MY_STACK, you can write like this:
check that size("MY_STACK") >=maxstack("Program entry")
+ totalstack("interrupt") + 100;

When linking, the linker emits an error if the check fails. In this example, an error will
be emitted if the sum of the following exceeds the size of the MY_STACK segment:
● The maximum stack usage in the category Program entry (the main program).
● The sum of each individual maximum stack usage in the category interrupt
(assuming that all interrupt routines need space at the same time).
● A safety margin of 100 bytes (to account for stack usage not visible to the analysis).
See also check that directive, page 406 and Stack considerations, page 221.

RESULT OF AN ANALYSIS—THE MAP FILE CONTENTS

When stack usage analysis is enabled, the linker map file contains a stack usage chapter
with a summary of the stack usage for each call graph root category, and lists the call

93

AFE1_AFE2-1:1
Stack usage analysis

chain that results in the maximum stack depth for each call graph root. This is an
example of what the stack usage chapter in the map file might look like:
*****************************************************
* *
* STACK USAGE ANALYSIS *
* *
*****************************************************

Call Graph Root Category Max Use Total Use

------------------------ ------- ---------
interrupt 4 4
Program entry 350 350

Program entry
"__program_start": 0x0000c0f8

Maximum call chain 350 bytes

"__program_start" 0
"main" 4
"WriteObject" 24
"DumpObject" 0
"PrintObject" 8
"fprintf" 4
"_PrintfLarge" 126
"_PutstrLarge" 100
"pad" 14
"_PutcharsLarge" 10
"_FProut" 6
"fputc" 6
"_Fwprep" 6
"fseek" 4
"_Fspos" 14
"fflush" 6
"fflushOne" 6
"__write" 0
"__dwrite" 10
"__DebugBreak" 2

interrupt
"DoStuff()": 0x0000e9ee

Maximum call chain 4 bytes

"DoStuff()" 4

IAR C/C++ Compiler User Guide

94 for MSP430

AFE1_AFE2-1:1
 Linking overview

The summary contains the depth of the deepest call chain in each category as well as the
sum of the depths of the deepest call chains in that category.
Each call graph root belongs to a call graph root category to enable convenient
calculations in check that directives.

SPECIFYING ADDITIONAL STACK USAGE INFORMATION

To specify additional stack usage information you can use either a stack usage control
file (suc) where you specify stack usage control directives or annotate the source code.
You can:
● Specify complete stack usage information (call graph root category, stack usage,
and possible calls) for a function, by using the stack usage control directive
function. Typically, you do this if stack usage information is missing, for example
in an assembler module. In your suc file you can, for example, write like this:
function MyFunc: 32,
calls MyFunc2,
calls MyFunc3, MyFunc4: 16;

function [interrupt] MyInterruptHandler: 44;

See also function directive, page 407.
● Exclude certain functions from stack usage analysis, by using the stack usage
control directive exclude. In your suc file you can, for example, write like this:
exclude MyFunc5, MyFunc6;
See also exclude directive, page 406.
● Specify a list of possible destinations for indirect calls in a function, by using the
stack usage control directive possible calls. Use this for functions which are
known to perform indirect calls and where you know exactly which functions that
might be called in this particular application. In your suc file you can, for example,
write like this:
possible calls MyFunc7: MyFunc8, MyFunc9;
If the information about which functions that might be called is available at compile
time, consider using the #pragma calls directive instead.
See also possible calls directive, page 408 and calls, page 335.
● Specify that functions are call graph roots, including an optional call graph root
category, by using the stack usage control directive call graph root or the
#pragma call_graph_root directive. In your suc file you can, for example,
write like this:
call graph root [task]: MyFunc10, MyFunc11;

95

AFE1_AFE2-1:1
Stack usage analysis

If your interrupt functions have not already been designated as call graph roots by the
compiler, you must do so manually. You can do this either by using the #pragma
call_graph_root directive in your source code or by specifying a directive in your
suc file, for example:
call graph root [interrupt]: Irq1Handler, Irq2Handler;
See also call graph root directive, page 405 and call_graph_root, page 335.
● Specify a maximum number of iterations through any of the cycles in the recursion
nest of which the function is a member. In your suc file you can, for example, write
like this:
max recursion depth MyFunc12: 10;
● Selectively suppress the warning about unmentioned functions referenced by a
module for which you have supplied stack usage information in the stack usage
control file. Use the no calls from directive in your suc file, for example, like
this:
no calls from [file.r43] to MyFunc13, MyFunc14;
● Instead of specifying stack usage information about assembler modules in a stack
usage control file, you can annotate the assembler source with call frame
information. For more information, see the IAR Assembler User Guide for MSP430.
For more information, see the chapter The stack usage control file.

LIMITATIONS
Apart from missing or incorrect stack usage information, there are also other sources of
inaccuracy in the analysis:
● The linker cannot always identify all functions in object modules that lack stack
usage information. In particular, this might be a problem with object modules
written in assembler language. You can provide stack usage information for such
modules using a stack usage control file, and for assembler language modules you
can also annotate the assembler source code with CFI directives to provide stack
usage information. See the IAR Assembler User Guide for MSP430.
● If you use inline assembler to change the frame size or to perform function calls,
this will not be reflected in the analysis.
● Extra space consumed by other sources (the processor, an operating system, etc) is
not accounted for.
● The support for C++ is very incomplete. In particular virtual function calls, dynamic
objects, and various indirect calls from the standard library (like the functions set up
by set_new_handler and register_callback) are not supported at all.
● If you use other forms of function calls, they will not be reflected in the call graph.

IAR C/C++ Compiler User Guide

96 for MSP430

AFE1_AFE2-1:1
 Linking overview

● Using multi-file compilation (--mfc) can interfere with using a stack usage control
file to specify properties of module-local functions in the involved files.
Note: Stack usage analysis produces a worst case result. The program might not actually
ever end up in the maximum call chain, by design, or by coincidence.
Stack usage analysis is only a complement to actual measurement. If the result is
important, you need to perform independent validation of the results of the analysis.

SITUATIONS WHERE WARNINGS ARE ISSUED

When stack usage analysis is enabled in the linker, warnings will be generated in the
following circumstances:
● There is a function without stack usage information.
● There is an indirect call site in the application for which a list of possible called
functions has not been supplied.
● There are no known indirect calls, but there is an uncalled function that is not
known to be a call graph root.
● The application contains recursion (a cycle in the call graph) for which no
maximum recursion depth has been supplied, or which is of a form for which the
linker is unable to calculate a reliable estimate of stack usage.
● There are calls to a function declared as a call graph root.
● You have used the stack usage control file to supply stack usage information for
functions in a module that does not have such information, and there are functions
referenced by that module which have not been mentioned as being called in the
stack usage control file.

CALL GRAPH LOG

To help you interpret the results of the stack usage analysis, there is a log output option
that produces a simple text representation of the call graph (--log stack_usage).

97

AFE1_AFE2-1:1
Stack usage analysis

Example output:
Program entry:
0 __program_start [350]
0 __data16_memzero [2]
2 - [0]
0 __data16_memcpy [2]
0 memcpy [2]
2 - [0]
2 - [0]
0 main [350]
4 ParseObject [52]
28 GetObject [28]
34 getc [22]
38 _Frprep [18]
44 malloc [12]
44 __data16_malloc [12]
48 __data16_findmem [8]
52 __data16_free [4]
56 - [0]
52 __data16GetMemChunk [2]
54 - [0]
46 - [0]
44 __read [12]
54 __DebugBreak [2]
56 - [0]
36 - [0]
34 CreateObject [18]
40 malloc [12] ***
4 ProcessObject [326]
8 ProcessHigh [76]
34 ProcesMedium [50]
60 ProcessLow [24]
84 - [0]
8 DumpObject [322]
8 PrintObject [322]
16 fprintf [314]
20 _PrintfLarge [310]
10 - [0]
4 WriteObject [346]
28 DumpObject [322] ***
4 DestroyObject [28]
28 free [4]
28 __data16_free [4] ***
30 - [0]
0 exit [38]
0 _exit [38]
4 _Close_all [34]

IAR C/C++ Compiler User Guide

98 for MSP430

AFE1_AFE2-1:1
 Linking overview

8 fclose [30]
14 _Fofree [4]
14 free [4] ***
16 - [0]
14 fflush [24] ***
14 free [4] ***
14 __close [8]
20 __DebugBreak [2] ***
14 remove [8]
20 __DebugBreak [2] ***
8 __write [12] ***
2 __exit [8]
8 __DebugBreak [2] ***
2 - [0]

Each line consists of this information:

● The stack usage at the point of call of the function
● The name of the function, or a single '-' to indicate usage in a function at a point
with no function call (typically in a leaf function)
● The stack usage along the deepest call chain from that point. If no such value could
be calculated, "[---]" is output instead. "***" marks functions that have already
been shown.

99

AFE1_AFE2-1:1
Stack usage analysis

IAR C/C++ Compiler User Guide

100 for MSP430

AFE1_AFE2-1:1
 Linking your application
● Linking considerations

● Verifying the linked result of code and data placement

● Checking module consistency

Linking considerations
When you set up your project in the IAR Embedded Workbench IDE, a default linker
configuration file is automatically used based on your project settings and you can
simply link your application. For the majority of all projects it is sufficient to configure
the vital parameters that you find in Project>Options>Linker>Config.
When you build from the command line, you can use a ready-made linker command file
provided with your product package.
The config directory contains the information required by XLINK, and are ready to be
used as is. The only change, if any, you will normally have to make to the supplied
configuration file is to customize it so it fits the target system memory map. If, for
example, your application uses additional external RAM, you must also add details
about the external RAM memory area.
To edit a linker configuration file, use the editor in the IDE, or any other suitable editor.
Do not change the original template file. We recommend that you make a copy in the
working directory, and modify the copy instead.
If you find that the default linker configuration file does not meet your requirements, you
might want to consider:
● Placing segments
● Placing data
● Setting up stack memory
● Setting up heap memory
● Placing code
● Keeping modules
● Keeping symbols and segments
● Application startup
● Interaction between XLINK and your application
● Producing other output formats than UBROF

101

AFE1_AFE2-1:1
Linking considerations

PLACING SEGMENTS
The placement of segments in memory is performed by the IAR XLINK Linker.
This section describes the most common linker commands and how to customize the
linker configuration file to suit the memory layout of your target system. In
demonstrating the methods, fictitious examples are used.
In demonstrating the methods, fictitious examples are used based on this memory
layout:
● There is 1 Mbyte addressable memory.
● There is ROM memory in the address ranges 0x0000–0x1FFF, 0x3000–0x4FFF,
and 0x10000–0x1FFFF.
● There is RAM memory in the address ranges 0x8000–0xAFFF, 0xD000–0xFFFF,
and 0x20000–0x27FFF.
● There are two addressing modes for data, one for data16 memory and one for
data20 memory.
● There is one stack and one heap.
● There are two addressing modes for code, one for near_func memory and one for
far_func memory.
Note: Even though you have a different memory map, for example if you have
additional memory spaces (EEPROM) and additional segments, you can still use the
methods described in the following examples.
The ROM can be used for storing CONST and CODE segment memory types. The RAM
memory can contain segments of DATA type. The main purpose of customizing the linker
configuration file is to verify that your application code and data do not cross the
memory range boundaries, which would lead to application failure.
For the result of each placement directive after linking, inspect the segment map in the
list file (created by using the command line option -x).

General hints for placing segments

When you consider where in memory you should place your segments, it is typically a
good idea to start placing large segments first, then placing small segments.
In addition, you should consider these aspects:
● Start placing the segments that must be placed on a specific address. This is, for
example, often the case with the segment holding the reset vector.
● Then consider placing segments that hold content that requires continuous memory
addresses, for example the segments for the stack and heap.

IAR C/C++ Compiler User Guide

102 for MSP430

AFE1_AFE2-1:1
 Linking your application

● When placing code and data segments for different addressing modes, make sure to
place the segments in size order (the smallest memory type first).
Note: Before the linker places any segments in memory, the linker will first place the
absolute segments.

Using the -Z command for sequential placement

Use the -Z command when you must keep a segment in one consecutive chunk, when
you must preserve the order of segment parts in a segment, or, more unlikely, when you
must put segments in a specific order.
The following illustrates how to use the -Z command to place the segment MYSEGMENTA
followed by the segment MYSEGMENTB in CONST memory (that is, ROM) in the memory
range 0x0000-0x1FFF.
-Z(CONST)MYSEGMENTA,MYSEGMENTB=0000-1FFF

To place two segments of different types contiguous in the same memory area, do not
specify a range for the second segment. In the following example, the MYSEGMENTA
segment is first located in memory. Then, the rest of the memory range could be used by
MYCODE.

-Z(CONST)MYSEGMENTA=0000-1FFF
-Z(CODE)MYCODE

Two memory ranges can overlap. This allows segments with different placement
requirements to share parts of the memory space; for example:
-Z(CONST)MYSMALLSEGMENT=0000-01FF
-Z(CONST)MYLARGESEGMENT=0000-1FFF

Even though it is not strictly required, make sure to always specify the end of each
memory range. If you do this, the IAR XLINK Linker will alert you if your segments do
not fit in the available memory.

Using the -P command for packed placement

The -P command differs from -Z in that it does not necessarily place the segments (or
segment parts) sequentially. With -P it is possible to put segment parts into holes left by
earlier placements.
The following example illustrates how the XLINK -P option can be used for making
efficient use of the memory area. This command will place the data segment MYDATA in
DATA memory (that is, in RAM) in a fictitious memory range:
-P(DATA)MYDATA=8000-AFFF,D000-FFFF

103

AFE1_AFE2-1:1
Linking considerations

If your application has an additional RAM area in the memory range 0x6000-0x67FF,
you can simply add that to the original definition:
-P(DATA)MYDATA=8000-AFFF,D000-FFFF,6000–67FF

The linker can then place some parts of the MYDATA segment in the first range, and some
parts in the second range. If you had used the -Z command instead, the linker would
have to place all segment parts in the same range.
Note: Copy initialization segments—BASENAME_I and BASENAME_ID—and dynamic
initialization segments must be placed using -Z. For code placed in RAM, see Code in
RAM, page 108.

PLACING DATA
Static memory is memory that contains variables that are global or declared static.

Placing static memory data segments

Depending on their memory attribute, static data is placed in specific segments. For
information about the segments used by the compiler, see Static data memory segments,
page 90.
For example, these commands can be used to place the static data segments:
/* First, the segments to be placed in ROM are defined. */
-Z(CONST)DATA16_C=0000-1FFF,3000-4FFF
-Z(CONST)DATA20_C=0000-1FFF,3000-4FFF,10000-1FFFF
-Z(CONST)DATA16_ID,DATA20_ID=010000-1FFFF

/* Then, the RAM data segments are placed in memory. */

-Z(DATA)DATA16_I,DATA16_Z,DATA16_N=8000-AFFF
-Z(DATA)DATA20_I,DATA20_Z,DATA20_N=20000-27FFF

All the data segments are placed in the area used by on-chip RAM.

Placing located data

A variable that is explicitly placed at an address, for example by using the #pragma
location directive or the @ operator, is placed in for example either the DATA16_AC or
the DATA16_AN segment. The former is used for constant-initialized data, and the latter
for items declared as __no_init. The individual segment part of the segment knows its
location in the memory space, and it does not have to be specified in the linker
configuration file.

IAR C/C++ Compiler User Guide

104 for MSP430

AFE1_AFE2-1:1
 Linking your application

Placing user-defined segments

If you create your own segments by using for example the #pragma location directive
or the @ operator, these segments must also be defined in the linker configuration file
using the -Z or -P segment control directives.

SETTING UP STACK MEMORY

In this example, the data segment for holding the stack is called CSTACK. The system
startup code initializes the stack pointer to point to the end of the stack segment.
Allocating a memory area for the stack is performed differently when using the
command line interface, as compared to when using the IDE.
For more information about stack memory, see Stack considerations, page 221.

Stack size allocation in the IDE

Choose Project>Options. In the General Options category, click the Stack/Heap tab.
Add the required stack size in the dedicated text box.

Stack size allocation from the command line

The size of the CSTACK segment is defined in the linker configuration file.
The linker configuration file sets up a constant, representing the size of the stack, at the
beginning of the file. Specify the appropriate size for your application, in this example
512 bytes:
-D_CSTACK_SIZE=200 /* 512 bytes of stack size */

Note that the size is written hexadecimally, but not necessarily with the 0x notation.
In many linker configuration files provided with IAR Embedded Workbench, this line is
prefixed with the comment character // because the IDE controls the stack size
allocation. To make the directive take effect, remove the comment character.

Placing the stack segment

Further down in the linker configuration file, the actual stack segment is defined in the
memory area available for the stack:
-Z(DATA)CSTACK+_CSTACK_SIZE#8000-AFFF

Note:
● This range does not specify the size of the stack; it specifies the range of the
available memory.

105

AFE1_AFE2-1:1
Linking considerations

● The # allocates the CSTACK segment at the end of the memory area. Typically, this
means that the stack will get all remaining memory at the same time as it is
guaranteed that it will be at least _CSTACK_SIZE bytes in size.

SETTING UP HEAP MEMORY

The heap contains dynamic data allocated by the C function malloc (or a corresponding
function) or the C++ operator new.
If your application uses dynamic memory allocation, you should be familiar with:
● The linker segments used for the heap, see Dynamic memory on the heap, page 69
● The steps for allocating the heap size, which differs depending on which build
interface you are using
● The steps involved for placing the heap segments in memory.
See also Heap considerations, page 221.
In this example, the data segment for holding the heap is called HEAP.

Heap size allocation in the IDE

Choose Project>Options. In the General Options category, click the Stack/Heap tab.
Add the required heap size in the dedicated text box.

Heap size allocation from the command line

The size of the HEAP segment is defined in the linker configuration file.
The linker configuration file sets up a constant, representing the size of the heap, at the
beginning of the file. Specify the appropriate size for your application, in this example
1024 bytes:
-D_HEAP_SIZE=400 /* 1024 bytes for heap memory */

Note that the size is written hexadecimally, but not necessarily with the 0x notation.
In many linker configuration files provided with IAR Embedded Workbench, these lines
are prefixed with the comment character // because the IDE controls the heap size
allocation. To make the directive take effect, remove the comment character.
If you use a heap, you should allocate at least 512 bytes for it, to make it work properly.

Placing the heap segment

The actual HEAP segment is allocated in the memory area available for the heap:
-Z(DATA)HEAP+_HEAP_SIZE=8000-AFFF

IAR C/C++ Compiler User Guide

106 for MSP430

AFE1_AFE2-1:1
 Linking your application

Note: This range does not specify the size of the heap; it specifies the range of the
available memory.

PLACING CODE
This section contains descriptions of the segments used for storing code and the
interrupt vector table. For information about all segments, see Summary of segments,
page 387.

Startup code
In this example, the segment CSTART contains code used during system startup and
termination, see System startup and termination, page 135. The segment parts must also
be placed into one continuous memory space, which means that the -P segment
directive cannot be used.
This line will place the CSTART segment at the address 0x1100:
-Z(CODE)CSTART=1100

Code for MSP430

Code for normal functions and interrupt functions is placed in the CODE segment. Again,
this is a simple operation in the linker configuration file:
/* MSP430 devices */
-Z(CODE)CODE=0000-1FDF,3000-4FFF

Code for MSP430X

In the Small code model, normal code is placed in the CODE16 segment. In the Large
code model, CODE is used. Interrupt functions are placed in ISR_CODE. This too is a
simple operation in the linker configuration file:
-Z(CODE)CODE16,ISR_CODE=0000-1FDF,3000-4FFF
-Z(CODE)CODE=0000-1FDF,3000-4FFF,10000-FFFFF

Interrupt vectors
The interrupt vector table contains pointers to interrupt routines, including the reset
routine. In this example, the table is placed in the segment INTVEC. For the MSP430
microcontroller, it typically ends at address 0xFFFF. For a device with 16 interrupt
vectors, this means that the segment should start at the address 0xFFE0, for example:
-Z(CONST)INTVEC=FFE0-FFFF

The system startup code places the reset vector in the RESET segment; the INTVEC
segment cannot be used by the system startup code because the size of the interrupt

107

AFE1_AFE2-1:1
Linking considerations

vector table varies between different devices. In the linker configuration file it can look
like this:
-Z(CONST)RESET=FFFE-FFFF

An application that does not use the standard startup code can either use the RESET
segment, or define an interrupt function on the reset vector, in which case the INTVEC
segment is used.
For more information about the interrupt vectors, see Interrupt vectors and the interrupt
vector table, page 73.

Code in RAM
The segment CODE_I holds code which executes in RAM and which was initialized by
CODE_ID.

The linker configuration file uses the XLINK option -Q to specify automatic setup for
copy initialization of segments. This will cause the linker to generate a new initializer
segment into which it will place all data content of the code segment. Everything else,
such as symbols and debugging information, will still be associated with the code
segment. Code in the application must at runtime copy the contents of the initializer
segment in ROM to the code segment in RAM. This is very similar to how initialized
variables are treated.
-QCODE_I=CODE_ID

/* __ramfunc code copied to and executed from RAM */

-Z(DATA)CODE_I=RAMSTART-RAMEND
-Z(CODE)CODE_ID=ROMSTART-ROMEND

C++ dynamic initialization

In C++, all global objects are created before the main function is called. The creation of
objects can involve the execution of a constructor.
The DIFUNCT segment contains a vector of addresses that point to initialization code.
All entries in the vector are called when the system is initialized.
For example:
-Z(CONST)DIFUNCT=0000-1FFF,3000-4FFF

DIFUNCT must be placed using -Z. For more information, see DIFUNCT, page 398.

KEEPING MODULES
If a module is linked as a program module, it is always kept. That is, it will contribute
to the linked application. However, if a module is linked as a library module, it is

IAR C/C++ Compiler User Guide

108 for MSP430

AFE1_AFE2-1:1
 Linking your application

included only if it is symbolically referred to from other parts of the application that
have been included. This is true, even if the library module contains a root symbol. To
assure that such a library module is always included, use the linker option -A to make
all modules in the file be treaded as if they were program modules:
-A file.r43

Use -C to makes all modules in the file be treated as if they were library modules:
-C file.r43

KEEPING SYMBOLS AND SEGMENTS

By default, XLINK removes any segments, segment parts, and global symbols that are
not needed by the application. To retain a symbol that does not appear to be needed—or
actually, the segment part it is defined in—you can either use the __root attribute on
the symbol in your C/C++ source code or ROOT in your assembler source code, or use
the XLINK option -g.
For information about included and excluded symbols and segment parts, inspect the
map file (created by using the XLINK option -xm).
For more information about the linking procedure for keeping symbols and sections, see
The linking process in detail, page 87.

APPLICATION STARTUP
By default, the point where the application starts execution is defined by the
__program_start label, which is defined to point at the start of code. The label is also
communicated via the debugger information to any debugger.
To change the start point of the application to another label, use the XLINK option -s.

INTERACTION BETWEEN XLINK AND YOUR APPLICATION

Use the XLINK option -D to define symbols that can be used for controlling your
application. You can also use symbols to represent the start and end of a continuous
memory area that is defined in the linker configuration file.
To change a reference to one symbol to another symbol, use the XLINK command line
option -e. This is useful, for example, to redirect a reference from a non-implemented
function to a stub function, or to choose one of several different implementations of a
certain function.
For information about the addresses and sizes of all global (statically linked) symbols,
inspect the entry list in the map file (the XLINK option -xm).

109

AFE1_AFE2-1:1
Verifying the linked result of code and data placement

PRODUCING OTHER OUTPUT FORMATS THAN UBROF

XLINK can generate more than 30 industry-standard loader formats, in addition to the
proprietary format UBROF which is used by the C-SPY debugger. For a complete list,
see the IAR Linker and Library Tools Reference Guide. To specify a different output
format than the default, use the XLINK option -F. For example:
-Fintel-standard

Note that it can be useful to use the XLINK -O option to produce two output files, one
for debugging and one for burning to ROM/flash.
Note also that if you choose to enable debug support using the -r option for certain
low-level I/O functionality for mechanisms like file operations on the host computer etc,
such debug support might have an impact on the performance and responsiveness of
your application. In this case, the debug build will differ from your release build due to
the debug modules included.

Verifying the linked result of code and data placement

The linker has several features that help you to manage code and data placement, for
example, messages at link time and the linker map file.

SEGMENT TOO LONG ERRORS AND RANGE ERRORS

Code or data that is placed in a relocatable segment will have its absolute address
resolved at link time. Note that it is not known until link time whether all segments will
fit in the reserved memory ranges. If the contents of a segment do not fit in the address
range defined in the linker configuration file, XLINK will issue a segment too long error.
Some instructions do not work unless a certain condition holds after linking, for
example that a branch must be within a certain distance or that an address must be even.
XLINK verifies that the conditions hold when the files are linked. If a condition is not
satisfied, XLINK generates a range error or warning and prints a description of the
error.
For more information about these types of errors, see the IAR Linker and Library Tools
Reference Guide.

LINKER MAP FILE

XLINK can produce an extensive cross-reference listing, which can optionally contain
the following information:
● A segment map which lists all segments in address order

IAR C/C++ Compiler User Guide

110 for MSP430

AFE1_AFE2-1:1
 Linking your application

● A module map which lists all segments, local symbols, and entries (public symbols)
for every module in the program. All symbols not included in the output can also be
listed
● A module summary which lists the contribution (in bytes) from each module
● A symbol list which contains every entry (global symbol) in every module.
Use the option Generate linker listing in the IDE, or the option -x on the command
line, and one of their suboptions to generate a linker listing.
Normally, XLINK will not generate an output file if any errors, such as range errors,
occur during the linking process. Use the option Always generate output in the IDE,
or the option -B on the command line, to generate an output file even if a non-fatal error
was encountered.
For more information about the listing options and the linker listing, see the IAR Linker
and Library Tools Reference Guide, and the IDE Project Management and Building
Guide.

Checking module consistency

This section introduces the concept of runtime model attributes, a mechanism used by
the tools provided by IAR Systems to ensure that modules that are linked into an
application are compatible, in other words, are built using compatible settings. The tools
use a set of predefined runtime model attributes. You can use these predefined attributes
or define your own to ensure that incompatible modules are not used together.
For example, in the compiler, it is possible to specify the size of the double
floating-point type. If you write a routine that only works for 64-bit doubles, it is
possible to check that the routine is not used in an application built using 32-bit doubles.

RUNTIME MODEL ATTRIBUTES

A runtime attribute is a pair constituted of a named key and its corresponding value. Two
modules can only be linked together if they have the same value for each key that they
both define.
There is one exception: if the value of an attribute is *, then that attribute matches any
value. The reason for this is that you can specify this in a module to show that you have
considered a consistency property, and this ensures that the module does not rely on that
property.

111

AFE1_AFE2-1:1
Checking module consistency

Example
In this table, the object files could (but do not have to) define the two runtime attributes
color and taste:

Object file Color Taste

file1 blue not defined
file2 red not defined
file3 red *
file4 red spicy
file5 red lean
Table 8: Example of runtime model attributes

In this case, file1 cannot be linked with any of the other files, since the runtime
attribute color does not match. Also, file4 and file5 cannot be linked together,
because the taste runtime attribute does not match.
On the other hand, file2 and file3 can be linked with each other, and with either
file4 or file5, but not with both.

USING RUNTIME MODEL ATTRIBUTES

To ensure module consistency with other object files, use the #pragma rtmodel
directive to specify runtime model attributes in your C/C++ source code. For example,
if you have a UART that can run in two modes, you can specify a runtime model
attribute, for example uart. For each mode, specify a value, for example mode1 and
mode2. Declare this in each module that assumes that the UART is in a particular mode.
This is how it could look like in one of the modules:
#pragma rtmodel="uart", "mode1"

Alternatively, you can also use the rtmodel assembler directive to specify runtime
model attributes in your assembler source code. For example:
rtmodel "uart", "mode1"

Note: Key names that start with two underscores are reserved by the compiler. For more
information about the syntax, see rtmodel, page 349 and the IAR Assembler User Guide
for MSP430.
Note: The predefined runtime attributes all start with two underscores. Any attribute
names you specify yourself should not contain two initial underscores in the name, to
eliminate any risk that they will conflict with future IAR runtime attribute names.
At link time, the IAR XLINK Linker checks module consistency by ensuring that
modules with conflicting runtime attributes will not be used together. If conflicts are
detected, an error is issued.

IAR C/C++ Compiler User Guide

112 for MSP430

AFE1_AFE2-1:1
 Linking your application

PREDEFINED RUNTIME ATTRIBUTES

The table below shows the predefined runtime model attributes that are available for the
compiler. These can be included in assembler code or in mixed C/C++ and assembler
code.

Runtime model attribute Value Description

__rt_version This runtime key is always present in all
modules generated by the compiler. If a
major change in the runtime characteristics
occurs, the value of this key changes.
Table 9: Predefined runtime model attributes

The easiest way to find the proper settings of the RTMODEL directive is to compile a C or
C++ module to generate an assembler file, and then examine the file.
If you are using assembler routines in the C or C++ code, see the chapter Assembler
directives in the IAR Assembler User Guide for MSP430.

113

AFE1_AFE2-1:1
Checking module consistency

IAR C/C++ Compiler User Guide

114 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime
environment
● Introduction to the runtime environment

● Setting up the runtime environment

● Additional information on the runtime environment

● Managing a multithreaded environment

DLIB can be used with both the C and the C++ languages. CLIB, on the other
hand, can only be used with the C language. For more information about CLIB,
see the chapter The CLIB runtime environment.

Introduction to the runtime environment

A runtime environment is the environment in which your application executes.
This section contains information about:
● Runtime environment functionality, page 115
● Briefly about input and output (I/O), page 116
● Briefly about C-SPY emulated I/O, page 118
● Briefly about retargeting, page 118

RUNTIME ENVIRONMENT FUNCTIONALITY

The DLIB runtime environment supports Standard C and C++ and consists of:
● The C/C++ standard library, both its interface (provided in the system header files)
and its implementation.
● Startup and exit code.
● Low-level I/O interface for managing input and output (I/O).
● Special compiler support, for instance functions for switch handling or integer
arithmetics.

115

AFE1_AFE2-1:1
Introduction to the runtime environment

● Support for hardware features:

● Direct access to low-level processor operations by means of intrinsic functions,
such as functions for interrupt mask handling
● Peripheral unit registers and interrupt definitions in include files
● The MSP430 hardware multiplier peripheral unit
● Memory protection unit (MPU) and intellectual property encapsulation (IPE).
Runtime environment functions are provided in one or more runtime libraries.
The runtime library is delivered both as prebuilt libraries and (depending on your
product package) as source files. The prebuilt libraries are available in different
configurations to meet various needs, see Runtime library configurations, page 126.
You can find the libraries in the product subdirectories 430\lib and 430\src\lib,
respectively.
For more information about the library, see the chapter C/C++ standard library
functions.

BRIEFLY ABOUT INPUT AND OUTPUT (I/O)

Every application must communicate with its environment. The application might for
example display information on an LCD, read a value from a sensor, get the current date
from the operating system, etc. Typically, your application performs I/O via the C/C++
standard library or some third-party library.
There are many functions in the C/C++ standard library that deal with I/O, including
functions for: standard character streams, file system access, time and date,
miscellaneous system actions, and termination and assert. This set of functions is
referred to as the standard I/O interface.
On a desktop computer or a server, the operating system is expected to provide I/O
functionality to the application via the standard I/O interface in the runtime
environment. However, in an embedded system, the runtime library cannot assume that
such functionality is present, or even that there is an operating system at all. Therefore,

IAR C/C++ Compiler User Guide

116 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime environment

the low-level part of the standard I/O interface is not completely implemented by
default:

To make the standard I/O interface work, you can:

● Let the C-SPY debugger emulate I/O operations on the host computer, see Briefly
about C-SPY emulated I/O, page 118
● Retarget the standard I/O interface to your target system by providing a suitable
implementation of the interface, see Briefly about retargeting, page 118.
It is possible to mix these two approaches. You can, for example, let debug printouts and
asserts be emulated by the C-SPY debugger, but implement your own file system. The
debug printouts and asserts are useful during debugging, but no longer needed when
running the application stand-alone (not connected to the C-SPY debugger).

117

AFE1_AFE2-1:1
Introduction to the runtime environment

BRIEFLY ABOUT C-SPY EMULATED I/O

C-SPY emulated I/O is a mechanism which lets the runtime environment interact with
the C-SPY debugger to emulate I/O actions on the host computer:

For example, when C-SPY emulated I/O is enabled:

● Standard character streams are directed to the C-SPY Terminal I/O window
● File system operations are performed on the host computer
● Time and date functions return the time and date of the host computer
● The C-SPY debugger notifies when the application terminates or an assert fails.
This behavior can be valuable during the early development of an application, for
example in an application that uses file I/O before any flash file system I/O drivers are
implemented, or if you need to debug constructions in your application that use stdin
and stdout without the actual hardware device for input and output being available.
See Setting up your runtime environment, page 120 and The C-SPY emulated I/O
mechanism, page 131.

BRIEFLY ABOUT RETARGETING

Retargeting is the process where you adapt the runtime environment so that your
application can execute I/O operations on your target system.
The standard I/O interface is large and complex. To make retargeting easier, the DLIB
runtime environment is designed so that it performs all I/O operations through a small
set of simple functions, which is referred to as the DLIB low-level I/O interface. By

IAR C/C++ Compiler User Guide

118 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime environment

default, the functions in the low-level interface lack usable implementations. Some are
unimplemented, others have stub implementations that do not perform anything except
returning error codes.
To retarget the standard I/O interface, all you have to do is to provide implementations
for the functions in the DLIB low-level I/O interface.

For example, if your application calls the functions printf and fputc in the standard
I/O interface, the implementations of those functions both call the low-level function
__write to output individual characters. To make them work, you just need to provide
an implementation of the __write function—either by implementing it yourself, or by
using a third-party implementation.
For information about how to override library modules with your own implementations,
see Overriding library modules, page 123. See also The DLIB low-level I/O interface,
page 139 for information about the functions that are part of the interface.

Setting up the runtime environment

This section contains these tasks:
● Setting up your runtime environment, page 120
A runtime environment with basic project settings to be used during the initial phase
of development.
● Retargeting—Adapting for your target system, page 122
● Overriding library modules, page 123

119

AFE1_AFE2-1:1
Setting up the runtime environment

● Customizing and building your own runtime library, page 124

See also:
● Managing a multithreaded environment, page 154 for information about how to
adapt the runtime environment to treat all library objects according to whether they
are global or local to a thread.

SETTING UP YOUR RUNTIME ENVIRONMENT

You can set up the runtime environment based on some basic project settings. It is also
often convenient to let the C-SPY debugger manage things like standard streams, file
I/O, and various other system interactions. This basic runtime environment can be used
for simulation before you have any target hardware.
To set up the runtime environment:
1 Before you build your project, choose Project>Options>General Options to open the
Options dialog box.
2 On the Library Configuration page, verify the following settings:
● Library: choose which library and library configuration to use. Typically, choose
Normal DLIB or Full DLIB.
For information about the various library configurations, see Runtime library
configurations, page 126.
3 On the Library Options page, select Auto for both Printf formatter and Scanf
formatter. This means that the linker will automatically choose the appropriate
formatters based on information from the compiler. For more information about the
available formatters and how to choose one manually, see Formatters for printf, page
129 and Formatters for scanf, page 130, respectively.
4 To enable C-SPY emulated I/O, choose Project>Options>Linker>Output and select
the Format option that matches the level of support you need. See Briefly about C-SPY
emulated I/O, page 118. Choose between:

Linker
Linker option in the
command line Description
IDE
option
Debug information -Fubrof Debug support for C-SPY, but without any support
for C-SPY for C-SPY emulated I/O.
With runtime -r The same as -Fubrof but also limited support for
control modules C-SPY emulated I/O handling program abort, exit,
and assertions.
Table 10: Debug information and levels of C-SPY emulated I/O

IAR C/C++ Compiler User Guide

120 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime environment

Linker
Linker option in the
command line Description
IDE
option
With I/O emulation -rt Full support for C-SPY emulated I/O, which means
modules the same as -r, but also support for I/O handling,
and accessing files on the host computer during
debugging.
Table 10: Debug information and levels of C-SPY emulated I/O (Continued)

Note: The C-SPY Terminal I/O window is not opened automatically; you must open it
manually. For more information about this window, see the C-SPY® Debugging Guide
for MSP430.
5 On some systems, terminal output might be slow because the host computer and the
target system must communicate for each character.
For this reason, a replacement for the __write function called __write_buffered is
included in the runtime library. This module buffers the output and sends it to the
debugger one line at a time, speeding up the output. Note that this function uses about
80 bytes of RAM memory.
To use this feature in the IDE, choose Project>Options>Linker>Output and select the
option Buffered terminal output.
To enable this function on the command line, add this to the linker command line:
-e__write_buffered=__write

6 Some math functions are available in different versions: default versions, smaller than
the default versions, and larger but more accurate than default versions. Consider
which versions you should use.
To specify which set of the math functions to use, choose Project>Options>General
Options>Library Options>Math functions and choose which set to use. You can also
specify individual functions.
For more information, see Math functions, page 131.
7 When you build your project, a suitable prebuilt library and library configuration file
are automatically used based on the project settings you made.
For information about which project settings affect the choice of library file, see
Runtime library configurations, page 126.
You have now set up a runtime environment that can be used while developing your
application source code.

121

AFE1_AFE2-1:1
Setting up the runtime environment

RETARGETING—ADAPTING FOR YOUR TARGET SYSTEM

Before you can run your application on your target system, you must adapt some parts
of the runtime environment, typically the system initialization and the DLIB low-level
I/O interface functions.
To adapt your runtime environment for your target system:
1 Adapt system initialization.
It is likely that you must adapt the system initialization, for example, your application
might need to initialize interrupt handling, I/O handling, watchdog timers, etc. You do
this by implementing the routine __low_level_init, which is executed before the
data segments are initialized. See System startup and termination, page 135 and System
initialization, page 138.
Note: You can find device-specific examples on this in the example projects provided in
the product installation, see the Information Center.
2 Adapt the runtime library for your target system. To implement such functions, you
need a good understanding of the DLIB low-level I/O interface, see Briefly about
retargeting, page 118.
Typically, you must implement your own functions if your application uses:
● Standard streams for input and output
If any of these streams are used by your application, for example by the functions
printf and scanf, you must implement your versions of the low-level functions
__read and __write.
The low-level functions identify I/O streams, such as an open file, with a file handle
that is a unique integer. The I/O streams normally associated with stdin, stdout,
and stderr have the file handles 0, 1, and 2, respectively. When the handle is -1,
all streams should be flushed. Streams are defined in stdio.h.
● File input and output
The library contains a large number of powerful functions for file I/O operations,
such as fopen, fclose, fprintf, fputs, etc. All these functions call a small set of
low-level functions, each designed to accomplish one particular task, for example,
__open opens a file, and __write outputs characters. Implement your version of
these low-level functions.
● signal and raise
If the default implementation of these functions does not provide the functionality
you need, you can implement your own versions.

IAR C/C++ Compiler User Guide

122 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime environment

● Time and date

To make the time and date functions work, you must implement the functions clock,
__time32, __time64, and __getzone. Whether you use __time32 or __time64
depends on which interface you use for time_t, see time.h, page 384.
● Assert, see __ReportAssert, page 145.
● Environment interaction
If the default implementation of system or getenv does not provide the
functionality you need, you can implement your own versions.
For more information about the functions, see The DLIB low-level I/O interface, page
139.
The library files that you can override with your own versions are located in the
430\src\lib directory.

3 When you have implemented your functions of the low-level I/O interface, you must
add your version of these functions to your project. For information about this, see
Overriding library modules, page 123.
Note: If you have implemented a DLIB low-level I/O interface function and added it to
a project that you have built with support for C-SPY emulated I/O, your low-level
function will be used and not the functions provided with C-SPY emulated I/O. For
example, if you implement your own version of __write, output to the C-SPY
Terminal I/O window will not be supported. See Briefly about C-SPY emulated I/O,
page 118.
4 Before you can execute your application on your target system, you must rebuild your
project with a Release build configuration. This means that the linker will not include
the C-SPY emulated I/O mechanism and the low-level I/O functions it provides. If your
application calls any of the low-level functions of the standard I/O interface, either
directly or indirectly, and your project does not contain these, the linker will issue an
error for every missing low-level function.
Note: By default, the NDEBUG symbol is defined in a Release build configuration, which
means asserts will no longer be checked. For more information, see __ReportAssert,
page 145.

OVERRIDING LIBRARY MODULES

To override a library function and replace it with your own
implementation:
1 Use a template source file—a library source file or another template—and place a copy
of it in your project directory.

123

AFE1_AFE2-1:1
Setting up the runtime environment

The library files that you can override with your own versions are located in the
430\src\lib directory.

2 Modify the file.

Note: To override the functions in a module, you must provide alternative
implementations for all the needed symbols in the overridden module. Otherwise you
will get error messages about duplicate definitions.
3 Add the modified file to your project, like any other source file.
Note: If you have implemented a DLIB low-level I/O interface function and added it to
a project that you have built with support for C-SPY emulated I/O, your low-level
function will be used and not the functions provided with C-SPY emulated I/O. For
example, if you implement your own version of __write, output to the C-SPY
Terminal I/O window will not be supported. See Briefly about C-SPY emulated I/O,
page 118.
You have now finished the process of overriding the library module with your version.

CUSTOMIZING AND BUILDING YOUR OWN RUNTIME

LIBRARY
If the prebuilt library configurations do not meet your requirements, you can customize
your own library configuration, but that requires that you rebuild the library.
Building a customized library is a complex process. Therefore, consider carefully
whether it is really necessary. You must build your own runtime library when:
● There is no prebuilt library for the required combination of compiler options or
hardware support, for example, locked registers
● You want to build a library with direct support for the hardware multiplier
● You want to define your own library configuration with support for locale, file
descriptors, multibyte characters, etc. This will include or exclude certain parts of
the DLIB runtime environment.
In those cases, you must:
● Make sure that you have installed the library source code (scr\lib). If not already
installed, you can install it using the IAR License Manager, see the Installation and
Licensing Guide.
● Set up a library project
● Make the required library customizations
● Build your customized runtime library
● Finally, make sure your application project will use the customized runtime library.

IAR C/C++ Compiler User Guide

124 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime environment

To set up a library project:

1 In the IDE, choose Project>Create New Project and use any of the library project
templates that are available for the prebuilt libraries and that matches the project
settings you need as closely as possible. See Prebuilt runtime libraries, page 127.
Note that when you create a new library project from a template, the majority of the files
included in the new project are the original installation files. If you are going to modify
these files, make copies of them first and replace the original files in the project with
these copies.
2 Modify the generic options in the created library project to suit your application, see
Basic project configuration, page 54.
To customize the library functionality:
1 The library functionality is determined by a set of configuration symbols. The default
values of these symbols are defined in the file DLib_Defaults.h which you can find
in 430\inc\c. This read-only file describes the configuration possibilities. Note that
you should not modify this file.
In addition, your custom library has its own library configuration file
libraryname.h—which you can find in 430\config\template\project—and
which sets up that specific library with the required library configuration. Customize
this file by setting the values of the configuration symbols according to the application
requirements. For example, to enable the ll qualifier in printf format strings, write in
your library configuration file:
#define _DLIB_PRINTF_LONG_LONG 1

For information about configuration symbols that you might want to customize, see:
● Configuration symbols for printf and scanf, page 148
● Configuration symbols for file input and output, page 149
● Locale, page 149
● Strtod, page 151
● Managing a multithreaded environment, page 154
2 When you are finished, build your library project with the appropriate project options.
After you build your library, you must make sure to use it in your application project.
To build IAR Embedded Workbench projects from the command line, use the IAR
Command Line Build Utility (iarbuild.exe). However, no make or batch files for
building the library from the command line are provided.For information about the build
process and the IAR Command Line Build Utility, see the IDE Project Management and
Building Guide.

125

AFE1_AFE2-1:1
Additional information on the runtime environment

To use the customized runtime library in your application project:

1 In the IDE, choose Project>Options>General Options and click the Library
Configuration tab.
2 From the Library drop-down menu, choose Custom DLIB.
3 In the Library file text box, locate your library file.
4 In the Configuration file text box, locate your library configuration file.

Additional information on the runtime environment

This section gives additional information on the runtime environment:
● Runtime library configurations, page 126
● Prebuilt runtime libraries, page 127
● Formatters for printf, page 129
● Formatters for scanf, page 130
● The C-SPY emulated I/O mechanism, page 131
● Math functions, page 131
● The Texas Instruments MathLib library, page 134
● System startup and termination, page 135
● System initialization, page 138
● The DLIB low-level I/O interface, page 139
● Configuration symbols for printf and scanf, page 148
● Configuration symbols for file input and output, page 149
● Locale, page 149
● Strtod, page 151
● Hardware multiplier support, page 151
● MPU/IPE support, page 152

RUNTIME LIBRARY CONFIGURATIONS

The runtime library is provided with different library configurations, where each
configuration is suitable for different application requirements.
The runtime library configuration is defined in the library configuration file. It contains
information about what functionality is part of the runtime environment. The less
functionality you need in the runtime environment, the smaller the environment
becomes.

IAR C/C++ Compiler User Guide

126 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime environment

These predefined library configurations are available:

Library configuration Description
Normal DLIB (default) C locale, but no locale interface, no file descriptor support, no
multibyte characters in printf and scanf, and no hexadecimal
floating-point numbers in strtod.
Full DLIB Full locale interface, C locale, file descriptor support, and optionally
multibyte characters in printf and scanf, and hexadecimal
floating-point numbers in strtod.
Table 11: Library configurations

Note: In addition to these predefined library configurations, you can provide your own
configuration, see Customizing and building your own runtime library, page 124
If you do not specify a library configuration explicitly you will get the default
configuration. If you use a prebuilt runtime library, a configuration file that matches the
runtime library file will automatically be used. See Setting up the runtime environment,
page 119.
To override the default library configuration, use one of these methods:
1 Use a prebuilt configuration of your choice—to specify a runtime configuration
explicitly:
Choose Project>Options>General Options>Library Configuration>Library and
change the default setting.
Use the --dlib_config compiler option, see --dlib_config, page 277.
The prebuilt libraries are based on the default configurations, see Runtime library
configurations, page 126.
2 If you have built your own customized library, choose Project>Options>General
Options>Library Configuration>Library and choose Custom to use your own
configuration. For more information, see Customizing and building your own runtime
library, page 124.

PREBUILT RUNTIME LIBRARIES

The prebuilt runtime libraries are configured for different combinations of these options:
● Core
● Data model
● Code model
● Size of the double floating-point type
● Library configuration—Normal or Full

127

AFE1_AFE2-1:1
Additional information on the runtime environment

● Position-independent code and read-only data (ROPI)

● Support for multithreading.

To choose a library from the command line:

If you build your application from the command line, make the following settings:
● Specify which library object file to use on the XLINK command line, like:
dllibname.r43
● If you do not specify a library configuration, the default configuration will be used.
However, you can specify the library configuration explicitly for the compiler:
--dlib_config C:\...\dllibname.h

Note: All modules in the library have a name that starts with the character ? (question
mark).
You can find the library object files in the subdirectory 430\lib\dlib and the library
configuration files in the 430\inc\dlib subdirectory.

Library filename syntax

The names of the libraries are constructed from these elements:

{lib} is dl for the IAR DLIB runtime environment

{core} is either 430 or 430x
{code_model} is empty for MSP430 devices. For MSP430X devices, it is
one of s or l for the Small and Large code model,
respectively.
{data_model} is empty for MSP430 devices. For MSP430X devices, it is
one of s, m, or l for the Small, Medium, and Large data
model, respectively
{size_of_double} is either f for 32 bits or d for 64 bits
{lib_config} is one of n or f for normal, and full, respectively.
{ropi} is r when position-independent code and read-only data is
enabled, otherwise it is empty.
{threads} is t when support for multithreading is enabled, otherwise
empty.

For example, the library dl430xsmdfrt.r43 is configured for DLIB, the MSP430X
core, the Small code model, the Medium data model, 64-bit double, the full library

IAR C/C++ Compiler User Guide

128 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime environment

configuration, position-independent code and read-only data is enabled, and

multithreading is enabled.
Note: The library configuration file has the same base name as the library.

FORMATTERS FOR PRINTF

The printf function uses a formatter called _Printf. The full version is quite large,
and provides facilities not required in many embedded applications. To reduce the
memory consumption, three smaller, alternative versions are also provided. Note that
the wprintf variants are not affected.
This table summarizes the capabilities of the different formatters:

Small/ Large/ Full/

Formatting capabilities Tiny
SmallNoMb† LargeNoMb† FullNoMb†
Basic specifiers c, d, i, o, p, s, u, X, x, and % Yes Yes Yes Yes
Multibyte support No Yes/No Yes/No Yes/No
Floating-point specifiers a, and A No No No Yes
Floating-point specifiers e, E, f, F, g, and G No No Yes Yes
Conversion specifier n No No Yes Yes
Format flag +, -, #, 0, and space No Yes Yes Yes
Length modifiers h, l, L, s, t, and Z No Yes Yes Yes
Field width and precision, including * No Yes Yes Yes
long long support No No Yes Yes
Table 12: Formatters for printf

† NoMb means without multibytes.

Note: It is possible to optimize these functions even further, but that requires that you
rebuild the library. See Configuration symbols for printf and scanf, page 148.
The compiler can automatically detect which formatting capabilities are needed in a
direct call to printf, if the formatting string is a string literal. This information is
passed to the linker, which combines the information from all modules to select a
suitable formatter for the application. However, if the formatting string is a variable, or
if the call is indirect through a function pointer, the compiler cannot perform the
analysis, forcing the linker to select the Full formatter. In this case, you might want to
override the automatically selected printf formatter.
To override the automatically selected printf formatter in the IDE:
1 Choose Project>Options>General Options to open the Options dialog box.
2 On the Library Options page, select the appropriate formatter.

129

AFE1_AFE2-1:1
Additional information on the runtime environment

To override the automatically selected printf formatter from the command

line:
1 Add one of these lines in the linker configuration file you are using:
-e_PrintfFull=_Printf
-e_PrintfFullNoMb=_Printf
-e_PrintfLarge=_Printf
-e_PrintfLargeNoMb=_Printf
_e_PrintfSmall=_Printf
-e_PrintfSmallNoMb=_Printf
-e_PrintfTiny=_Printf
-e_PrintfTinyNoMb=_Printf

FORMATTERS FOR SCANF

In a similar way to the printf function, scanf uses a common formatter, called
_Scanf. The full version is quite large, and provides facilities that are not required in
many embedded applications. To reduce the memory consumption, two smaller,
alternative versions are also provided. Note that the wscanf versions are not affected.
This table summarizes the capabilities of the different formatters:

Small/ Large/ Full/

Formatting capabilities
SmallNoMb† LargeNoMb† FullNoMb†
Basic specifiers c, d, i, o, p, s, u, X, x, and % Yes Yes Yes
Multibyte support Yes/No Yes/No Yes/No
Floating-point specifiers a, and A No No Yes
Floating-point specifiers e, E, f, F, g, and G No No Yes
Conversion specifier n No No Yes
Scan set [ and ] No Yes Yes
Assignment suppressing * No Yes Yes
long long support No No Yes
Table 13: Formatters for scanf

† NoMb means without multibytes.

Note: It is possible to optimize these functions even further, but that requires that you
rebuild the library. See Configuration symbols for printf and scanf, page 148.
The compiler can automatically detect which formatting capabilities are needed in a
direct call to scanf, if the formatting string is a string literal. This information is passed
to the linker, which combines the information from all modules to select a suitable
formatter for the application. However, if the formatting string is a variable, or if the call
is indirect through a function pointer, the compiler cannot perform the analysis, forcing

IAR C/C++ Compiler User Guide

130 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime environment

the linker to select the full formatter. In this case, you might want to override the
automatically selected scanf formatter.
To manually specify the scanf formatter in the IDE:
1 Choose Project>Options>General Options to open the Options dialog box.
2 On the Library Options page, select the appropriate formatter.
To manually specify the scanf formatter from the command line:
1 Add one of these lines in the linker configuration file you are using:
-e_ScanfFull=_Scanf
-e_ScanfFullNoMb=_Scanf
-e_ScanfLarge=_Scanf
-e_ScanfLargeNoMb=_Scanf
_e_ScanfSmall=_Scanf
_e_ScanfSmallNoMb=_Scanf

THE C-SPY EMULATED I/O MECHANISM

The C-SPY emulated I/O mechanism works as follows:
1 The debugger will detect the presence of the function __DebugBreak, which will
be part of the application if you linked it with the linker option for C-SPY emulated
I/O.
2 In this case, the debugger will automatically set a breakpoint at the __DebugBreak
function.
3 When your application calls a function in the DLIB low-level I/O interface, for
example, open, the __DebugBreak function is called, which will cause the
application to stop at the breakpoint and perform the necessary services.
4 The execution will then resume.
See also Briefly about C-SPY emulated I/O, page 118.

MATH FUNCTIONS
Some C/C++ standard library math functions are available in different versions:
● The default versions
● Smaller versions (but less accurate)
● More accurate versions (but larger).

131

AFE1_AFE2-1:1
Additional information on the runtime environment

Smaller versions
The functions cos, exp, log, log2, log10, __iar_Log (a help function for log, log2,
and log10), pow, sin, tan, and __iar_Sin (a help function for sin and cos) exist in
additional, smaller versions in the library. They are about 20% smaller and about 20%
faster than the default versions. The functions handle INF and NaN values. The
drawbacks are that they almost always lose some precision and they do not have the
same input range as the default versions.
The names of the functions are constructed like:
__iar_xxx_small<f|l>

where f is used for float variants, l is used for long double variants, and no suffix
is used for double variants.
To specify which set of math functions to use:
1 Choose Project>Options>General Options>Library Options>Math functions and
choose which set to use.
2 Link your application and the chosen set will be used.
To specify a complete set of math functions from the command line:
1 Use the -f option to extend the XLINK command line with the appropriate file:

double
Extended command line file Texas Instruments MathLib is used
size
dlib_small_math.xcl no any
dlib_small_math_mathlib32.xcl yes 32 bits
dlib_small_math_mathlib64.xcl yes 64 bits
Table 14: Extended command line files for the small math functions

2 Link your application and the complete set will be used.

IAR C/C++ Compiler User Guide

132 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime environment

To specify individual math functions from the command line:

1 Redirect the default function names to these names when linking, using these options:
-e__iar_sin_small=sin
-e__iar_cos_small=cos
-e__iar_tan_small=tan
-e__iar_log_small=log
-e__iar_log2_small=log2
-e__iar_log10_small=log10
-e__iar_exp_small=exp
-e__iar_pow_small=pow
-e__iar_Sin_small=__iar_Sin
-e__iar_Log_small=__iar_Log

-e__iar_sin_smallf=sinf
-e__iar_cos_smallf=cosf
-e__iar_tan_smallf=tanf
-e__iar_log_smallf=logf
-e__iar_log2_smallf=log2f
-e__iar_log10_smallf=log10f
-e__iar_exp_smallf=expf
-e__iar_pow_smallf=powf
-e__iar_Sin_smallf=__iar_Sinf
-e__iar_Log_smallf=__iar_Logf

-e__iar_sin_smalll=sinl
-e__iar_cos_smalll=cosl
-e__iar_tan_smalll=tanl
-e__iar_log_smalll=logl
-e__iar_log2_smalll=log2l
-e__iar_log10_smalll=log10l
-e__iar_exp_smalll=expl
-e__iar_pow_smalll=powl
-e__iar_Sin_smalll=__iar_Sinl
-e__iar_Log_smalll=__iar_Logl

Note that if you want to redirect any of the functions sin, cos, or __iar_Sin, you must
redirect all three functions.
Note that if you want to redirect any of the functions log, log2, log10, or __iar_Log,
you must redirect all four functions.

More accurate versions

The functions cos, pow, sin, and tan, and the help functions __iar_Sin and
__iar_Pow exist in versions in the library that are more exact and can handle larger

133

AFE1_AFE2-1:1
Additional information on the runtime environment

argument ranges. The drawback is that they are larger and slower than the default
versions.
The names of the functions are constructed like:
__iar_xxx_accurate<f|l>

where f is used for float variants, l is used for long double variants, and no suffix
is used for double variants.
To specify individual math functions from the command line:
1 Redirect the default function names to these names when linking, using these options:
-e__iar_sin_accurate=sin
-e__iar_cos_accurate=cos
-e__iar_tan_accurate=tan
-e__iar_pow_accurate=pow
-e__iar_Sin_accurate=__iar_Sin
-e__iar_Pow_accurate=__iar_Pow

-e__iar_sin_accuratef=sinf
-e__iar_cos_accuratef=cosf
-e__iar_tan_accuratef=tanf
-e__iar_pow_accuratef=powf
-e__iar_Sin_accuratef=__iar_Sinf
-e__iar_Pow_accuratef=__iar_Powf

-e__iar_sin_accuratel=sinl
-e__iar_cos_accuratel=cosl
-e__iar_tan_accuratel=tanl
-e__iar_pow_accuratel=powl
-e__iar_Sin_accuratel=__iar_Sinl
-e__iar_Pow_accuratel=__iar_Powl

Note that if you want to redirect any of the functions sin, cos, or __iar_Sin, you must
redirect all three functions.
Note that if you want to redirect any of the functions pow or __iar_Pow, you must
redirect both functions.

THE TEXAS INSTRUMENTS MATHLIB LIBRARY

Texas Instruments provides a library with a handful of hand-optimized 32-bit
floating-point functions that use the hardware multiplier.
The MathLib library requires that the hardware multiplier is enabled. However, MathLib
cannot be used in combination with position-independent code and read-only data
(ROPI).

IAR C/C++ Compiler User Guide

134 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime environment

To use the MathLib library, choose Project>Options>General Options>Library

Configuration and select MathLib.
To use the MathLib library on the command line, include the runtime library that
corresponds to your device and project settings from 430\lib\MathLib. Note that, to
take effect, the MathLib library must be specified before the runtime library on the
command line.
When you are using the MathLib library functions, interrupts are disabled while the
hardware multiplier is used.

SYSTEM STARTUP AND TERMINATION

This section describes the runtime environment actions performed during startup and
termination of your application.
The code for handling startup and termination is located in the source files
cstartup.s43, and low_level_init.c located in the 430\src\lib directory.

For information about how to customize the system startup code, see System
initialization, page 138.

System startup
During system startup, an initialization sequence is executed before the main function
is entered. This sequence performs initializations required for the target hardware and
the C/C++ environment.
For the hardware initialization, it looks like this:

● When the CPU is reset it will start executing at the program entry label
__program_start in the system startup code.

135

AFE1_AFE2-1:1
Additional information on the runtime environment

● The stack pointer (SP) is initialized

● If MPU support is included, the function __iar_430_mpu_init is called to
initialize the MPU.
● The function __low_level_init is called if you defined it, giving the application
a chance to perform early initializations. (Make sure that the MSP430 Watchdog
mechanism is disabled during initialization.)
For the C/C++ initialization, it looks like this:

● The RAM area of __ramfunc functions is initialized

● Static and global variables are initialized. That is, zero-initialized variables are
cleared and the values of other initialized variables are copied from ROM to RAM
memory. This step is skipped if __low_level_init returns zero. For more
information, see Initialization at system startup, page 89.
● Static C++ objects are constructed
● The main function is called, which starts the application.

IAR C/C++ Compiler User Guide

136 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime environment

System termination
This illustration shows the different ways an embedded application can terminate in a
controlled way:

An application can terminate normally in two different ways:

● Return from the main function
● Call the exit function.
Because the C standard states that the two methods should be equivalent, the system
startup code calls the exit function if main returns. The parameter passed to the exit
function is the return value of main.
The default exit function is written in C. It calls a small assembler function _exit that
will:
● Call functions registered to be executed when the application ends. This includes
C++ destructors for static and global variables, and functions registered with the
standard function atexit.
● Close all open files
● Call __exit
● When __exit is reached, stop the system.
An application can also exit by calling the abort or the _Exit function. The abort
function just calls __exit to halt the system, and does not perform any type of cleanup.
The _Exit function is equivalent to the abort function, except for the fact that _Exit
takes an argument for passing exit status information.
If you want your application to do anything extra at exit, for example resetting the
system (and if using atexit is not sufficient), you can write your own implementation
of the __exit(int) function.

137

AFE1_AFE2-1:1
Additional information on the runtime environment

The library files that you can override with your own versions are located in the
430\src\lib directory. See Overriding library modules, page 123.

C-SPY debugging support for system termination

If you have enabled C-SPY emulated I/O during linking, the normal __exit and abort
functions are replaced with special ones. C-SPY will then recognize when those
functions are called and can take appropriate actions to emulate program termination.
For more information, see Briefly about C-SPY emulated I/O, page 118.

SYSTEM INITIALIZATION
It is likely that you need to adapt the system initialization. For example, your application
might need to initialize memory-mapped special function registers (SFRs), or omit the
default initialization of data segments performed by the system startup code.
You can do this by implementing your own version of the routine __low_level_init,
which is called from the cstartup.s43 file before the data segments are initialized.
Modifying the cstartup.s43 file directly should be avoided.
The code for handling system startup is located in the source files cstartup.s43 and
low_level_init.c, located in the 430\src\lib directory.

Note that normally, you do not need to customize either of the files cstartup.s43 or
cexit.s43.

Note: Regardless of whether you implement your own version of __low_level_init

or the file cstartup.s43, you do not have to rebuild the library.

Customizing __low_level_init
The value returned by __low_level_init determines whether or not data segments
should be initialized by the system startup code. If the function returns 0, the data
segments will not be initialized.
Note: The file intrinsics.h must be included by low_level_init.c to assure
correct behavior of the __low_level_init routine.

Modifying the cstartup file

As noted earlier, you should not modify the cstartup.s43 file if implementing your
own version of __low_level_init is enough for your needs. However, if you do need
to modify the cstartup.s43 file, we recommend that you follow the general procedure
for creating a modified copy of the file and adding it to your project, see Overriding
library modules, page 123.

IAR C/C++ Compiler User Guide

138 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime environment

Note: You must make sure that the linker uses the start label used in your version of
cstartup.s43. For information about how to change the start label used by the linker,
read about the -s option in the IAR Linker and Library Tools Reference Guide.

THE DLIB LOW-LEVEL I/O INTERFACE

The runtime library uses a set of low-level functions—which are referred to as the DLIB
low-level I/O interface—to communicate with the target system. Most of the low-level
functions have no implementation.
For more information about this, see Briefly about input and output (I/O), page 116.
This table lists the functions in the DLIB low-level I/O interface:

Function in DLIB low-level I/O interface Defined in source file

abort abort.c
clock clock.c
__close close.c
__exit xxexit.c
getenv getenv.c
__getzone getzone.c
__lseek lseek.c
__open open.c
raise raise.c
__read read.c
remove remove.c
rename rename.c
__ReportAssert xreportassert.c
signal signal.c
system system.c
__time32, __time64 time.c, time64.c
__write write.c
Table 15: DLIB low-level I/O interface functions

Note: You should not use the low-level functions prefixed with __ directly in your
application. Instead you should use the standard library functions that use these
functions. For example, to write to stdout, you should use standard library functions
like printf or puts, which in turn calls the low-level function __write. If you have
forgot to implement a low-level function and your application will call that function via

139

AFE1_AFE2-1:1
Additional information on the runtime environment

a standard library function, the linker will issues an error when you link in release build
configuration.
Note: If you implement your own variants of the functions in this interface, your
variants will be used even though you have enabled C-SPY emulated I/O, see Briefly
about C-SPY emulated I/O, page 118.

abort
Source file 430\src\lib\dlib\abort.c

Description Standard C library function that aborts execution.

C-SPY debug action Notifies that the application has called abort.

Default implementation Calls __exit(EXIT_FAILURE).

See also Briefly about retargeting, page 118

System termination, page 137.

clock
Source file 430\src\lib\dlib\clock.c

Description Standard C library function that accesses the processor time.

C-SPY debug action Returns the clock on the host computer.

Default implementation Returns -1 to indicate that processor time is not available.

See also Briefly about retargeting, page 118.

__close
Source file 430\src\lib\dlib\close.c

Description Low-level function that closes a file.

C-SPY debug action Closes the associated host file on the host computer.

Default implementation None.

IAR C/C++ Compiler User Guide

140 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime environment

See also Briefly about retargeting, page 118.

__exit
Source file 430\src\lib\dlib\xxexit.c

Description Low-level function that halts execution.

C-SPY debug action Notifies that the end of the application was reached.

Default implementation Loops forever.

See also Briefly about retargeting, page 118

System termination, page 137.

getenv
Source file 430\src\lib\dlib\getenv.c
430\src\lib\dlib\environ.c

C-SPY debug action Accesses the host environment.

Default implementation The getenv function in the library searches the string pointed to by the global variable
__environ, for the key that was passed as argument. If the key is found, the value of it
is returned, otherwise 0 (zero) is returned. By default, the string is empty.
To create or edit keys in the string, you must create a sequence of null-terminated strings
where each string has the format:
key=value\0

End the string with an extra null character (if you use a C string, this is added
automatically). Assign the created sequence of strings to the __environ variable.
For example:
const char MyEnv[] = "Key=Value\0Key2=Value2\0";
__environ = MyEnv;

If you need a more sophisticated environment variable handling, you should implement
your own getenv, and possibly putenv function.
Note: The putenv function is not required by the standard, and the library does not
provide an implementation of it.

141

AFE1_AFE2-1:1
Additional information on the runtime environment

See also Briefly about retargeting, page 118.

__getzone
Source file 430\src\lib\dlib\getzone.c

Description Low-level function that returns the current time zone.

C-SPY debug action Not applicable.

Default implementation Returns ":".

See also Briefly about retargeting, page 118.

__lseek
Source file 430\src\lib\dlib\lseek.c

Description Low-level function for changing the location of the next access in an open file.

C-SPY debug action Searches in the associated host file on the host computer.

Default implementation None.

See also Briefly about retargeting, page 118.

__open
Source file 430\src\lib\dlib\open.c

Description Low-level function that opens a file.

C-SPY debug action Opens a file on the host computer.

Default implementation None.

See also Briefly about retargeting, page 118.

IAR C/C++ Compiler User Guide

142 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime environment

raise
Source file 430\src\lib\dlib\raise.c

Description Standard C library function that raises a signal.

C-SPY debug action Not applicable.

Default implementation Calls the signal handler for the raised signal, or terminates with call to
__exit(EXIT_FAILURE).

See also Briefly about retargeting, page 118.

__read
Source file 430\src\lib\dlib\read.c

Description Low-level function that reads characters from stdin and from files.

C-SPY debug action Directs stdin to the Terminal I/O window. All other files will read the associated host
file.

Default implementation None.

143

AFE1_AFE2-1:1
Additional information on the runtime environment

Example The code in this example uses memory-mapped I/O to read from a keyboard, whose port
is assumed to be located at 40:
#include <stddef.h>

__no_init volatile unsigned char kbIO @ 40;

size_t __read(int handle,

unsigned char *buf,
size_t bufSize)
{
size_t nChars = 0;

/* Check for stdin

(only necessary if FILE descriptors are enabled) */
if (handle != 0)
{
return -1;
}

for (/*Empty*/; bufSize > 0; --bufSize)

{
unsigned char c = kbIO;
if (c == 0)
break;

*buf++ = c;
++nChars;
}

return nChars;
}

For information about the handles associated with the streams, see Retargeting—
Adapting for your target system, page 122.
For information about the @ operator, see Controlling data and function placement in
memory, page 236.

See also Briefly about retargeting, page 118.

remove
Source file 430\src\lib\dlib\remove.c

Description Standard C library function that removes a file.

IAR C/C++ Compiler User Guide

144 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime environment

C-SPY debug action Writes a message to the Debug Log window and returns -1.

Default implementation Returns 0 to indicate success, but without removing a file.

See also Briefly about retargeting, page 118.

rename
Source file 430\src\lib\dlib\rename.c

Description Standard C library function that renames a file.

C-SPY debug action None.

Default implementation Returns -1 to indicate failure.

See also Briefly about retargeting, page 118.

__ReportAssert
Source file 430\src\lib\dlib\xreportassert.c

Description Low-level function that handles a failed assert.

C-SPY debug action Notifies the C-SPY debugger about the failed assert.

Default implementation Failed asserts are reported by the function __ReportAssert. By default, it prints an
error message and calls abort. If this is not the behavior you require, you can
implement your own version of the function.
The assert macro is defined in the header file assert.h. To turn off assertions, define
the symbol NDEBUG.
In the IDE, the symbol NDEBUG is by default defined in a Release project and not defined
in a Debug project. If you build from the command line, you must explicitly define the
symbol according to your needs. See NDEBUG, page 375.

See also Briefly about retargeting, page 118.

signal
Source file 430\src\lib\dlib\signal.c

145

AFE1_AFE2-1:1
Additional information on the runtime environment

Description Standard C library function that changes signal handlers.

C-SPY debug action Not applicable.

Default implementation As specified by Standard C. You might want to modify this behavior if the environment
supports some kind of asynchronous signals.

See also Briefly about retargeting, page 118.

system
Source file 430\src\lib\dlib\system.c

Description Standard C library function that executes commands.

C-SPY debug action Notifies the C-SPY debugger that system has been called and then returns -1.

Default implementation If you need to use the system function, you must implement it yourself. The system
function available in the library returns 0 if a null pointer is passed to it to indicate that
there is no command processor; otherwise it returns -1 to indicate failure. If this is not
the functionality that you require, you can implement your own version. This does not
require that you rebuild the library.

See also Briefly about retargeting, page 118.

__time32, __time64
Source file 430\src\lib\dlib\time.c
430\src\lib\dlib\time64.c

Description Low-level functions that return the current calendar time.

C-SPY debug action Returns the time on the host computer.

Default implementation Returns -1 to indicate that calendar time is not available.

See also Briefly about retargeting, page 118.

__write
Source file 430\src\lib\dlib\write.c

IAR C/C++ Compiler User Guide

146 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime environment

Description Low-level function that writes to stdout, stderr, or a file.

C-SPY debug action Directs stdout and stderr to the Terminal I/O window. All other files will write to
the associated host file.

Default implementation None.

Example The code in this example uses memory-mapped I/O to write to an LCD display, whose
port is assumed to be located at address 40:
#include <stddef.h>

__no_init volatile unsigned char lcdIO @ 40;

size_t __write(int handle,

const unsigned char *buf,
size_t bufSize)
{
size_t nChars = 0;

/* Check for the command to flush all handles */

if (handle == -1)
{
return 0;
}

/* Check for stdout and stderr

(only necessary if FILE descriptors are enabled.) */
if (handle != 1 && handle != 2)
{
return -1;
}

for (/* Empty */; bufSize > 0; --bufSize)

{
lcdIO = *buf;
++buf;
++nChars;
}

return nChars;
}

For information about the handles associated with the streams, see Retargeting—
Adapting for your target system, page 122.

See also Briefly about retargeting, page 118.

147

AFE1_AFE2-1:1
Additional information on the runtime environment

CONFIGURATION SYMBOLS FOR PRINTF AND SCANF

If the provided formatters do not meet your requirements—Formatters for printf, page
129 and Formatters for scanf, page 130—you can customize the Full formatters. Note
that this means you must rebuild the runtime library.
The default behavior of the printf and scanf formatters are defined by configuration
symbols in the file DLib_Defaults.h.
These configuration symbols determine what capabilities the function printf should
have:
Printf configuration symbols Includes support for
_DLIB_PRINTF_MULTIBYTE Multibyte characters
_DLIB_PRINTF_LONG_LONG Long long (ll qualifier)
_DLIB_PRINTF_SPECIFIER_FLOAT Floating-point numbers
_DLIB_PRINTF_SPECIFIER_A Hexadecimal floating-point numbers
_DLIB_PRINTF_SPECIFIER_N Output count (%n)
_DLIB_PRINTF_QUALIFIERS Qualifiers h, l, L, v, t, and z
_DLIB_PRINTF_FLAGS Flags -, +, #, and 0
_DLIB_PRINTF_WIDTH_AND_PRECISION Width and precision
_DLIB_PRINTF_CHAR_BY_CHAR Output char by char or buffered
Table 16: Descriptions of printf configuration symbols

When you build a library, these configurations determine what capabilities the function
scanf should have:

Scanf configuration symbols Includes support for

_DLIB_SCANF_MULTIBYTE Multibyte characters
_DLIB_SCANF_LONG_LONG Long long (ll qualifier)
_DLIB_SCANF_SPECIFIER_FLOAT Floating-point numbers
_DLIB_SCANF_SPECIFIER_N Output count (%n)
_DLIB_SCANF_QUALIFIERS Qualifiers h, j, l, t, z, and L
_DLIB_SCANF_SCANSET Scanset ([*])
_DLIB_SCANF_WIDTH Width
_DLIB_SCANF_ASSIGNMENT_SUPPRESSING Assignment suppressing ([*])
Table 17: Descriptions of scanf configuration symbols

IAR C/C++ Compiler User Guide

148 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime environment

To customize the formatting capabilities, you must;

1 Define the configuration symbols in the library configuration file according to your
application requirements.
2 Rebuild the library, see Customizing and building your own runtime library, page 124.

CONFIGURATION SYMBOLS FOR FILE INPUT AND OUTPUT

File I/O is only supported by libraries with the Full library configuration, see Runtime
library configurations, page 126, or in a customized library when the configuration
symbol __DLIB_FILE_DESCRIPTOR is defined. If this symbol is not defined, functions
taking a FILE * argument cannot be used.
To customize your library and rebuild it, see Customizing and building your own
runtime library, page 124.

LOCALE
Locale is a part of the C language that allows language- and country-specific settings for
several areas, such as currency symbols, date and time, and multibyte character
encoding.
Depending on which library configuration you are using, you get different level of locale
support. However, the more locale support, the larger your code will get. It is therefore
necessary to consider what level of support your application needs. See Runtime library
configurations, page 126.
The DLIB runtime library can be used in two main modes:
● With locale interface, which makes it possible to switch between different locales
during runtime
● Without locale interface, where one selected locale is hardwired into the
application.

Locale support in prebuilt libraries

The level of locale support in the prebuilt libraries depends on the library configuration.
● All prebuilt libraries support the C locale only
● All libraries with full library configuration have support for the locale interface. For
prebuilt libraries with locale interface, it is by default only supported to switch
multibyte character encoding at runtime.
● Libraries with normal library configuration do not have support for the locale
interface.
If your application requires a different locale support, you must rebuild the library.

149

AFE1_AFE2-1:1
Additional information on the runtime environment

Customizing the locale support and rebuilding the library

If you decide to rebuild the library, you can choose between these locales:
● The C locale
● The POSIX locale
● A wide range of European locales.

Locale configuration symbols

The configuration symbol _DLIB_FULL_LOCALE_SUPPORT, which is defined in the
library configuration file, determines whether a library has support for a locale interface
or not. The locale configuration symbols _LOCALE_USE_LANG_REGION and
_ENCODING_USE_ENCODING define all the supported locales and encodings:

#define _DLIB_FULL_LOCALE_SUPPORT 1
#define _LOCALE_USE_C /* C locale */
#define _LOCALE_USE_EN_US /* American English */
#define _LOCALE_USE_EN_GB /* British English */
#define _LOCALE_USE_SV_SE /* Swedish in Sweden */

See DLib_Defaults.h for a list of supported locale and encoding settings.

If you want to customize the locale support, you simply define the locale configuration
symbols required by your application. For more information, see Customizing and
building your own runtime library, page 124.
Note: If you use multibyte characters in your C or assembler source code, make sure
that you select the correct locale symbol (the local host locale).

Building a library without support for locale interface

The locale interface is not included if the configuration symbol
_DLIB_FULL_LOCALE_SUPPORT is set to 0 (zero). This means that a hardwired locale
is used—by default the Standard C locale—but you can choose one of the supported
locale configuration symbols. The setlocale function is not available and can
therefore not be used for changing locales at runtime.

Building a library with support for locale interface

Support for the locale interface is obtained if the configuration symbol
_DLIB_FULL_LOCALE_SUPPORT is set to 1. By default, the Standard C locale is used,
but you can define as many configuration symbols as required. Because the setlocale
function will be available in your application, it will be possible to switch locales at
runtime.

IAR C/C++ Compiler User Guide

150 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime environment

Changing locales at runtime

The standard library function setlocale is used for selecting the appropriate portion
of the application’s locale when the application is running.
The setlocale function takes two arguments. The first one is a locale category that is
constructed after the pattern LC_CATEGORY. The second argument is a string that
describes the locale. It can either be a string previously returned by setlocale, or it
can be a string constructed after the pattern:
lang_REGION

or
lang_REGION.encoding

The lang part specifies the language code, and the REGION part specifies a region
qualifier, and encoding specifies the multibyte character encoding that should be used.
The lang_REGION part matches the _LOCALE_USE_LANG_REGION preprocessor
symbols that can be specified in the library configuration file.

Example
This example sets the locale configuration symbols to Swedish to be used in Finland and
UTF8 multibyte character encoding:

setlocale (LC_ALL, "sv_FI.Utf8");

STRTOD
The function strtod does not accept hexadecimal floating-point strings in libraries
with the normal library configuration. To make strtod accept hexadecimal
floating-point strings, you must:
1 Enable the configuration symbol _DLIB_STRTOD_HEX_FLOAT in the library
configuration file.
2 Rebuild the library, see Customizing and building your own runtime library, page 124.

HARDWARE MULTIPLIER SUPPORT

Some MSP430 devices contain a hardware multiplier. The compiler supports this unit
by means of dedicated runtime library modules.
To make the compiler take advantage of the hardware multiplier unit, choose
Project>Options>General Options>Target and select a device that contains a
hardware multiplier unit from the Device drop-down menu. Make sure that the option
Hardware multiplier is selected.

151

AFE1_AFE2-1:1
Additional information on the runtime environment

Specify which runtime library object file to use on the XLINK command line.
In addition to the runtime library object file, you must extend the XLINK command line
with an additional linker configuration file. To use the hardware multiplier, use the
command line option -f to extend the XLINK command line with the appropriate
extended command line file:
Linker configuration file Type of hardware multiplier
multiplier.xcl 16 or 16s
multiplier32.xcl 32
Table 18: Additional linker configuration files for the hardware multiplier

Note: Interrupts are disabled during a hardware-multiply operation.

MPU/IPE SUPPORT

Memory Protection Unit (MPU)

Some MSP430 devices with FRAM contain a Memory Protection Unit (MPU) that
allows the FRAM memory to be divided into ranges with different access rights. The
runtime library provides support for automatically initializing the MPU with ranges
based on the content and placement of code and data in your application.
The linker configuration files for devices with an MPU group the segments in FRAM
such that three zones with different access requirements can be defined. The borders
between these zones are marked by the segments MPU_B1 and MPU_B2, respectively.
Persistent data, and the heaps for dynamically allocated data, are placed in the low zone,
with read-write permissions. For devices with IPE support, the middle zone is dedicated
to IPE code and data, with read-write-execute permissions. Constants and code are then
placed in the high zone, with read-execute permissions. For devices without IPE
support, the middle zone is instead given read-only permissions, and holds constants.
To include the MPU initialization routine, and adapt the memory placement to the
alignment requirements of the MPU, select Project>Options>General
Options>MPU/IPE>Support MPU. To actually enable the MPU, you must also select
Project>Options>General Options>MPU/IPE>Enable MPU. Use the other options
on that page to adapt the MPU initialization to your application needs, including setting
specific permissions on the information memory.
From the command line, send one of the following options to the linker to include the
MPU support:
-g?mpu1_4k_init For devices with MPU but no IPE, and 4k memory
-g?mpu1_8k_init For devices with MPU but no IPE, and 8k memory
-g?mpu1_16k_init For devices with MPU but no IPE, and 16k memory
-g?mpu2_init For devices with both MPU and IPE

IAR C/C++ Compiler User Guide

152 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime environment

You must also define the hexadecimal values that will be put in the MPUSAM and
MPUCTL0 registers, respectively, using for example:
-D__iar_430_MPUSAM_value=1573
-D__iar_430_MPUCTL0_value=0001

If the automatic setup for the MPU does not suit your application, you can manually
override the module ?MpuInit with your own implementation, without rebuilding the
runtime library.

Intellectual Property Encapsulation (IPE)

Some MSP430 devices with MPU support also contain the Intellectual Property
Encapsulation functionality. When enabled, this prevents a certain range of memory to
be read by a debugger. Only code located within the IPE range can read the data.
The runtime library provides support for automatically initializing the IPE to protect the
data and code in certain predefined memory segments. If IPE support is included,
special data structures are placed in the IPESIGNATURE memory, that are read by the
boot code to initialize the IPE functionality.
The linker configuration files for devices with IPE functionality define the segments
IPEDATA16_N, IPEDATA16_C and IPECODE16 in FRAM, surrounded by the border
segments IPE_B1 and IPE_B2. Make sure to place writable __no_init data to be
protected in the IPEDATA16_N segment, constant data in IPEDATA16_C, and the code
to read the data in IPECODE16. Additionally, any user-defined segment linked between
the border segments IPE_B1 and IPE_B2 will be protected.
For more information about how to place code and data in specific segments, see
Controlling data and function placement in memory, page 236.
To include the IPE initialization data structures, and enforce the alignment requirements
of the IPE, select Project>Options>General Options>MPU/IPE>Support IPE. To
actually enable the IPE, also select Project>Options>General
Options>MPU/IPE>Enable IPE. Use the other options on that page to further adapt
the IPE initialization to your application needs.
From the command line, send the following option to the linker to include the IPE
support:
-g__iar_430_ipe_signature

You must also define the hexadecimal value that will be put in the MPUIPC0 register,
using for example:
-D__iar_430_MPUIPC0_value=0040

153

AFE1_AFE2-1:1
Managing a multithreaded environment

If the automatic setup for the IPE does not suit your application, you can manually
override the module ?IpeInit with your own implementation, without rebuilding the
runtime library.
Note: Once IPE has been enabled on a device, the IPE area will remain locked until
cleared.
To clear the IPE area when downloading an application, select
Project>Options>Debugger>FET Debugger>Download>Erase main and
Information memory inc. IP PROTECTED area.

Managing a multithreaded environment

In a multithreaded environment, the standard library must treat all library objects
according to whether they are global or local to a thread. If an object is a true global
object, any updates of its state must be guarded by a locking mechanism to make sure
that only one thread can update it at any given time. If an object is local to a thread, the
static variables containing the object state must reside in a variable area local to that
thread. This area is commonly named thread-local storage (TLS).
The low-level implementations of locks and TLS are system-specific, and is not
included in the DLIB runtime environment. If you are using an RTOS, check if it
provides some or all of the required functions. Otherwise, you must provide your own.

MULTITHREAD SUPPORT IN THE DLIB RUNTIME

ENVIRONMENT
The DLIB runtime environment uses two kinds of locks—system locks and file stream
locks. The file stream locks are used as guards when the state of a file stream is updated,
and are only needed in the Full library configuration. The following objects are guarded
with system locks:
● The heap (in other words when malloc, new, free, delete, realloc, or calloc
is used).
● The file system (only available in the Full library configuration), but not the file
streams themselves. The file system is updated when a stream is opened or closed,
in other words when fopen, fclose, fdopen, fflush, or freopen is used.
● The signal system (in other words when signal is used).
● The temporary file system (in other words when tmpnam is used).
● Dynamically initialized function local objects with static storage duration.

IAR C/C++ Compiler User Guide

154 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime environment

These library objects use TLS:

Library objects using TLS When these functions are used

Error functions errno, strerror
Locale functions localeconv, setlocale
Time functions asctime, localtime, gmtime, mktime
Multibyte functions mbrlen, mbrtowc, mbsrtowc, mbtowc, wcrtomb,
wcsrtomb, wctomb
Rand functions rand, srand
Miscellaneous functions atexit, strtok
Table 19: Library objects using TLS

Note: If you are using printf/scanf (or any variants) with formatters, each individual
formatter will be guarded, but the complete printf/scanf invocation will not be
guarded.
If one of the C++ variants is used together with the DLIB runtime environment with
multithread support, the compiler option --guard_calls must be used to make sure
that function-static variables with dynamic initializers are not initialized simultaneously
by several threads.

ENABLING MULTITHREAD SUPPORT

Prebuilt libraries with multithread support are provided in the product installation. There
are no prebuilt runtime libraries with support for multithreading, which means you must
first customize the library by adding the line #define _DLIB_THREAD_SUPPORT 3 in
the library configuration file and rebuild your library. See also Customizing and building
your own runtime library, page 124.
To configure multithread support for use with threaded applications:
1 To enable multithread support:
On the command line, use the linker option --threaded_lib and use one of the
prebuilt libraries with thread support (dl430*t.r43) or your own customized library.
In the IDE, choose Project>Options>General Options>Library
Configuration>Enable thread support in the library. The linker option
--threaded_lib and the matching prebuilt library with thread support will
automatically be used. If one of the C++ variants is used, the IDE will automatically use
the compiler option --guard_calls to make sure that function-static variables with
dynamic initializers are not initialized simultaneously by several threads.

155

AFE1_AFE2-1:1
Managing a multithreaded environment

2 To complement the built-in multithread support in the runtime library, you must also:
● Implement code for the library’s system locks interface, see System locks interface,
page 156.
● If file streams are used, implement code for the library’s file stream locks interface
or redirect the interface to the system locks interface (using the linker option -e),
see File streams locks interface, page 156.
● Implement code that handles thread creation, thread destruction, and TLS access
methods for the library, see TLS handling, page 157.
See also Lock usage, page 157 for information about used file streams locks and system
locks.
You can find the required declaration of functions and definitions of macros in the
DLib_Threads.h file, which is included by yvals.h.

3 Build your project.

Note: If you are using a third-party RTOS, check their guidelines for how to enable
multithread support with IAR Systems tools.

System locks interface

This interface must be fully implemented for system locks to work:
typedef void *__iar_Rmtx; /* Lock info object */

void __iar_system_Mtxinit(__iar_Rmtx *); /* Initialize a system

lock */
void __iar_system_Mtxdst(__iar_Rmtx *);/*Destroy a system lock */
void __iar_system_Mtxlock(__iar_Rmtx *); /* Lock a system lock */
void __iar_system_Mtxunlock(__iar_Rmtx *); /* Unlock a system
lock */

The lock and unlock implementation must survive nested calls.

File streams locks interface

This interface is only needed for the Full library configuration. If file streams are used,
they can either be fully implemented or they can be redirected to the system locks
interface. This interface must be implemented for file streams locks to work:
typedef void *__iar_Rmtx; /* Lock info object */

void __iar_file_Mtxinit(__iar_Rmtx *);/*Initialize a file lock */

void __iar_file_Mtxdst(__iar_Rmtx *); /* Destroy a file lock */
void __iar_file_Mtxlock(__iar_Rmtx *); /* Lock a file lock */
void __iar_file_Mtxunlock(__iar_Rmtx *); /* Unlock a file lock */

IAR C/C++ Compiler User Guide

156 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime environment

The lock and unlock implementation must survive nested calls.

Lock usage
The number of locks that the DLIB runtime environment assumes exist are:
● _FOPEN_MAX—the maximum number of file stream locks. These locks are only
used in the Full library configuration, in other words only if both the macro symbols
_DLIB_FILE_DESCRIPTOR and _FILE_OP_LOCKS are true.
● _MAX_LOCK—the maximum number of system locks.

Note that even if the application uses fewer locks, the runtime environment will initialize
and destroy all the locks above.
For information about the initialization and destruction code, see xsyslock.c.

TLS handling
The DLIB runtime environment supports TLS memory areas for two types of threads:
the main thread (the main function including the system startup and exit code) and
secondary threads.
The main thread’s TLS memory area:
● Is automatically created and initialized by your application’s startup sequence
● Is automatically destructed by the application’s destruct sequence
● Is located in the segment TLS16_I
● Exists also for non-threaded applications.
Each secondary thread’s TLS memory area:
● Must be manually created and initialized
● Must be manually destructed
● Is located in a manually allocated memory area.
If you need the runtime library to support secondary threads, you must override the
function:
void *__iar_dlib_perthread_access(void *symbp);

The parameter is the address to the TLS variable to be accessed—in the main thread’s
TLS area—and it should return the address to the symbol in the current TLS area.

157

AFE1_AFE2-1:1
Managing a multithreaded environment

Two interfaces can be used for creating and destroying secondary threads. You can use
the following interface that allocates a memory area on the heap and initializes it. At
deallocation, it destroys the objects in the area and then frees the memory.
void *__iar_dlib_perthread_allocate(void);
void __iar_dlib_perthread_deallocate(void *);

Alternatively, if the application handles the TLS allocation, you can use this interface
for initializing and destroying the objects in the memory area:
void __iar_dlib_perthread_initialize(void *);
void __iar_dlib_perthread_destroy(void *);

These macros can be helpful when you implement an interface for creating and
destroying secondary threads:

Macro Description
__IAR_DLIB_PERTHREAD_SIZE The size needed for the TLS memory area.
__IAR_DLIB_PERTHREAD_INIT_SIZE The initializer size for the TLS memory area.
You should initialize the rest of the TLS
memory area, up to
__IAR_DLIB_PERTHREAD_SIZE to zero.
__IAR_DLIB_PERTHREAD_SYMBOL_ The offset to the symbol in the TLS memory
OFFSET(symbolptr) area.
Table 20: Macros for implementing TLS allocation

Note that the size needed for TLS variables depends on which resources in the DLIB
runtime environment your application uses.

IAR C/C++ Compiler User Guide

158 for MSP430

AFE1_AFE2-1:1
 The DLIB runtime environment

This is an example of how you can handle threads:

#include <yvals.h>

/* A thread's TLS pointer */

void _DLIB_TLS_MEMORY *TLSp;

/* Are we in a secondary thread? */

int InSecondaryThread = 0;

/* Allocate a thread-local TLS memory

area and store a pointer to it in TLSp. */
void AllocateTLS()
{
TLSp = __iar_dlib_perthread_allocate();
}

/* Deallocate the thread-local TLS memory area. */

void DeallocateTLS()
{
__iar_dlib_perthread_deallocate(TLSp);
}

/* Access an object in the

thread-local TLS memory area. */
void _DLIB_TLS_MEMORY *__iar_dlib_perthread_access(
void _DLIB_TLS_MEMORY *symbp)
{
char _DLIB_TLS_MEMORY *p = 0;
if (InSecondaryThread)
p = (char _DLIB_TLS_MEMORY *) TLSp;
else
p = (char _DLIB_TLS_MEMORY *)
__segment_begin("__DLIB_PERTHREAD");

p += __IAR_DLIB_PERTHREAD_SYMBOL_OFFSET(symbp);
return (void _DLIB_TLS_MEMORY *) p;
}

The TLSp variable is unique for each thread, and must be exchanged by the RTOS or
manually whenever a thread switch occurs.

159

AFE1_AFE2-1:1
Managing a multithreaded environment

TLS IN THE LINKER CONFIGURATION FILE

If threads are used, the main thread’s TLS memory area must be initialized by plain
copying because the initializers are used for each secondary thread’s TLS memory area
as well. This is controlled by the following statement in your linker configuration file:
-QTLS16_I=TLS16_ID

Both the TLS16_I segment and the TLS16_ID segment must be placed in default
memory for RAM and ROM, respectively.
The startup code will copy TLS16_ID to TLS16_I.

IAR C/C++ Compiler User Guide

160 for MSP430

AFE1_AFE2-1:1
 The CLIB runtime
environment
● Using a prebuilt runtime library

● Input and output

● System startup and termination

● Overriding default library modules

● Customizing system initialization

● C-SPY emulated I/O

● Hardware multiplier support

● MPU/IPE support

Note: The CLIB runtime environment does not support any C99 functionality. For
example, complex numbers and variable length arrays are not supported. Neither does
CLIB support C++.
The legacy CLIB runtime environment is provided for backward compatibility
and should not be used for new application projects. Among other things, it
does not support ROPI nor multithreading.

For information about migrating from CLIB to DLIB, see the IAR Embedded
Workbench® Migration Guide.

Using a prebuilt runtime library

The prebuilt runtime libraries are configured for different combinations of these
features:
● Core
● Code model
● Data model

161

AFE1_AFE2-1:1
Input and output

● Size of the double floating-point type.

CHOOSING A RUNTIME LIBRARY

The IDE includes the correct runtime library based on the options you select. See the
IDE Project Management and Building Guide for more information.
Specify which runtime library file to use on the XLINK command line, for instance:
cllibname.r43

The CLIB runtime environment includes the C standard library. The linker will include
only those routines that are required—directly or indirectly—by your application. For
more information about the runtime libraries, see the chapter C/C++ standard library
functions.

RUNTIME LIBRARY FILENAME SYNTAX

The runtime library names are constructed in this way:
{lib}{core}{code_model}{data_model}{size_of_double}.r43

where
● {lib} cl for the CLIB runtime library
● {core} is either 430 or 430X
● {code_model} is empty for MSP430 devices. For MSP430X devices, it is one of s
or l, for the Small and Large code model, respectively
● {data_model} is empty for MSP430 devices. For MSP430X devices, it is one of s,
m, or l, for the Small, Medium, and Large data model, respectively
● {size_of_double} is either f for 32 bits or d for 64 bits.

Input and output

You can customize:
● The functions related to character-based I/O
● The formatters used by printf/sprintf and scanf/sscanf.

CHARACTER-BASED I/O
The functions putchar and getchar are the fundamental C functions for
character-based I/O. For any character-based I/O to be available, you must provide
definitions for these two functions, using whatever facilities the hardware environment
provides.

IAR C/C++ Compiler User Guide

162 for MSP430

AFE1_AFE2-1:1
 The CLIB runtime environment

The creation of new I/O routines is based on these files:

● putchar.c, which serves as the low-level part of functions such as printf
● getchar.c, which serves as the low-level part of functions such as scanf.

The code example below shows how memory-mapped I/O could be used to write to a
memory-mapped I/O device:
__no_init volatile unsigned char devIO @ 8;

int putchar(int outChar)

{
devIO = outChar;
return outChar;
}

The exact address is a design decision. For example, it can depend on the selected
processor variant.
For information about how to include your own modified version of putchar and
getchar in your project build process, see Overriding library modules, page 123.

FORMATTERS USED BY PRINTF AND SPRINTF

The printf and sprintf functions use a common formatter, called
_formatted_write. There are three variants of the formatter:
_large_write
_medium_write
_small_write

By default, the linker automatically uses the most appropriate formatter for your
application.

_large_write
The _large_write formatter supports the C89 printf format directives.

_medium_write
The _medium_write formatter has the same format directives as _large_write,
except that floating-point numbers are not supported. Any attempt to use a %f, %g, %G,
%e, or %E specifier will produce a runtime error:

FLOATS? wrong formatter installed!

_medium_write is considerably smaller than the large version.

163

AFE1_AFE2-1:1
Input and output

_small_write
The _small_write formatter works in the same way as _medium_write, except that
it supports only the %%, %d, %o, %c, %s, and %x specifiers for integer objects, and does
not support field width or precision arguments. The size of _small_write is 10–15%
that of _medium_write.

Specifying the printf formatter in the IDE

1 Choose Project>Options and select the General Options category. Click the Library
Options tab.
2 Choose the appropriate Printf formatter option, which can be either Auto, Small,
Medium, or Large.

Specifying the printf formatter from the command line

To explicitly specify and override the formatter used by default, add one of the following
lines to the linker configuration file:
-e_small_write=_formatted_write
-e_medium_write=_formatted_write
-e_large_write=_formatted_write

Customizing printf
For many embedded applications, sprintf is not required, and even printf with
_small_write provides more facilities than are justified, considering the amount of
memory it consumes. Alternatively, a custom output routine might be required to
support particular formatting needs or non-standard output devices.
For such applications, a much reduced version of the printf function (without
sprintf) is supplied in source form in the file intwri.c. This file can be modified to
meet your requirements, and the compiled module inserted into the library in place of
the original file, see Overriding library modules, page 123.

FORMATTERS USED BY SCANF AND SSCANF

As with the printf and sprintf functions, scanf and sscanf use a common
formatter, called _formatted_read. There are two variants of the formatter:
_large_read
_medium_read

By default, the linker automatically uses the most appropriate formatter for your
application.

IAR C/C++ Compiler User Guide

164 for MSP430

AFE1_AFE2-1:1
 The CLIB runtime environment

_large_read
The _large_read formatter supports the C89 scanf format directives.

_medium_read
The _medium_read formatter has the same format directives as the large version,
except that floating-point numbers are not supported. _medium_read is considerably
smaller than the large version.

Specifying the scanf formatter in the IDE

1 Choose Project>Options and select the General Options category. Click the Library
Options tab.
2 Choose the appropriate Scanf formatter option, which can be either Auto, Medium or
Large.

Specifying the read formatter from the command line

To explicitly specify and override the formatter used by default, add one of the following
lines to the linker configuration file:
-e_medium_read=_formatted_read
-e_large_read=_formatted_read

System startup and termination

This section describes the actions the runtime environment performs during startup and
termination of applications.
The code for handling startup and termination is located in the source files
cstartup.s43 and low_level_init.c located in the 430\src\lib directory.

Note: Normally, you do not need to customize either of the files cstartup.s43 or
cexit.s43.

SYSTEM STARTUP
When an application is initialized, several steps are performed:
● If MPU support is included, the function __iar_430_mpu_init is called to
initialize the MPU.
● The custom function __low_level_init is called if you defined it, giving the
application a chance to perform early initializations.
● Static variables are initialized; this includes clearing zero-initialized memory and
copying the ROM image of the RAM memory of the remaining initialized variables.

165

AFE1_AFE2-1:1
Overriding default library modules

● The main function is called, which starts the application.

Note that the system startup code contains code for more steps than described here. The
other steps are applicable to the DLIB runtime environment.

SYSTEM TERMINATION
An application can terminate normally in two different ways:
● Return from the main function
● Call the exit function.
Because the C standard states that the two methods should be equivalent, the cstartup
code calls the exit function if main returns. The parameter passed to the exit function
is the return value of main. The default exit function is written in assembler.
When the application is built in debug mode, C-SPY stops when it reaches the special
code label ?C_EXIT.
An application can also exit by calling the abort function. The default function just
calls __exit to halt the system, without performing any type of cleanup.

Overriding default library modules

The IAR CLIB Library contains modules which you probably need to override with
your own customized modules, for example for character-based I/O, without rebuilding
the entire library. For information about how to override default library modules, see
Overriding library modules, page 123, in the chapter The DLIB runtime environment.

Customizing system initialization

For information about how to customize system initialization, see System initialization,
page 138.

C-SPY emulated I/O

The low-level I/O interface is used for communication between the application being
debugged and the debugger itself. The interface is simple: C-SPY will place breakpoints
on certain assembler labels in the application. When code located at the special labels is
about to be executed, C-SPY will be notified and can perform an action.

IAR C/C++ Compiler User Guide

166 for MSP430

AFE1_AFE2-1:1
 The CLIB runtime environment

THE DEBUGGER TERMINAL I/O WINDOW

When code at the labels ?C_PUTCHAR and ?C_GETCHAR is executed, data will be sent to
or read from the debugger window.
For the ?C_PUTCHAR routine, one character is taken from the output stream and written.
If everything goes well, the character itself is returned, otherwise -1 is returned.
When the label ?C_GETCHAR is reached, C-SPY returns the next character in the input
field. If no input is given, C-SPY waits until the user types some input and presses the
Return key.
To make the Terminal I/O window available, the application must be linked with the
XLINK option With I/O emulation modules selected. See the IDE Project
Management and Building Guide.

TERMINATION
The debugger stops executing when it reaches the special label ?C_EXIT.

Hardware multiplier support

Some MSP430 devices contain a hardware multiplier. For information about how the
compiler supports this unit, see Hardware multiplier support, page 151.

MPU/IPE support
Some MSP430 devices support Memory Protection Unit (MPU) and Intellectual
Property Encapsulation, see MPU/IPE support, page 152.

167

AFE1_AFE2-1:1
MPU/IPE support

IAR C/C++ Compiler User Guide

168 for MSP430

AFE1_AFE2-1:1
 Assembler language
interface
● Mixing C and assembler

● Calling assembler routines from C

● Calling assembler routines from C++

● Calling convention

● Assembler instructions used for calling functions

● Memory access methods

● Call frame information

Mixing C and assembler

The IAR C/C++ Compiler for MSP430 provides several ways to access low-level
resources:
● Modules written entirely in assembler
● Intrinsic functions (the C alternative)
● Inline assembler.
It might be tempting to use simple inline assembler. However, you should carefully
choose which method to use.

INTRINSIC FUNCTIONS
The compiler provides a few predefined functions that allow direct access to low-level
processor operations without having to use the assembler language. These functions are
known as intrinsic functions. They can be useful in, for example, time-critical routines.
An intrinsic function looks like a normal function call, but it is really a built-in function
that the compiler recognizes. The intrinsic functions compile into inline code, either as
a single instruction, or as a short sequence of instructions.
The advantage of an intrinsic function compared to using inline assembler is that the
compiler has all necessary information to interface the sequence properly with register

169

AFE1_AFE2-1:1
Mixing C and assembler

allocation and variables. The compiler also knows how to optimize functions with such
sequences; something the compiler is unable to do with inline assembler sequences. The
result is that you get the desired sequence properly integrated in your code, and that the
compiler can optimize the result.
For more information about the available intrinsic functions, see the chapter Intrinsic
functions.

MIXING C AND ASSEMBLER MODULES

It is possible to write parts of your application in assembler and mix them with your C
or C++ modules.
This gives several benefits compared to using inline assembler:
● The function call mechanism is well-defined
● The code will be easy to read
● The optimizer can work with the C or C++ functions.
This causes some overhead in the form of function call and return instruction sequences,
and the compiler will regard some registers as scratch registers.
An important advantage is that you will have a well-defined interface between what the
compiler produces and what you write in assembler. When using inline assembler, you
will not have any guarantees that your inline assembler lines do not interfere with the
compiler generated code.
When an application is written partly in assembler language and partly in C or C++, you
are faced with several questions:
● How should the assembler code be written so that it can be called from C?
● Where does the assembler code find its parameters, and how is the return value
passed back to the caller?
● How should assembler code call functions written in C?
● How are global C variables accessed from code written in assembler language?
● Why does not the debugger display the call stack when assembler code is being
debugged?
The first question is discussed in the section Calling assembler routines from C, page
178. The following two are covered in the section Calling convention, page 181.
The answer to the final question is that the call stack can be displayed when you run
assembler code in the debugger. However, the debugger requires information about the
call frame, which must be supplied as annotations in the assembler source file. For more
information, see Call frame information, page 193.

IAR C/C++ Compiler User Guide

170 for MSP430

AFE1_AFE2-1:1
 Assembler language interface

The recommended method for mixing C or C++ and assembler modules is described in
Calling assembler routines from C, page 178, and Calling assembler routines from
C++, page 180, respectively.

INLINE ASSEMBLER
Inline assembler can be used for inserting assembler instructions directly into a C or
C++ function. Typically, this can be useful if you need to:
● Access hardware resources that are not accessible in C (in other words, when there
is no definition for an SFR or there is no suitable intrinsic function available).
● Manually write a time-critical sequence of code that if written in C will not have the
right timing.
● Manually write a speed-critical sequence of code that if written in C will be too
slow.
● Call functions using a non-standard calling convention.
An inline assembler statement is similar to a C function in that it can take input
arguments (input operands), have return values (output operands), and read or write to
C symbols (via the operands). An inline assembler statement can also declare clobbered
resources (that is, values in registers and memory that have been overwritten).

Limitations
Most things you can to do in normal assembler language are also possible with inline
assembler, with the following differences:
● In general, assembler directives will cause errors or have no meaning. However,
data definition directives will work as expected.
● Resources used (registers, memory, etc) that are also used by the C compiler must
be declared as operands or clobbered resources.
● If you do not want to risk that the inline assembler statement to be optimized away
by the compiler, you must declare it volatile.
● Accessing a C symbol or using a constant expression requires the use of operands.
● Dependencies between the expressions for the operands might result in an error.

Risks with inline assembler

Without operands and clobbered resources, inline assembler statements have no
interface with the surrounding C source code. This makes the inline assembler code
fragile, and might also become a maintenance problem if you update the compiler in the

171

AFE1_AFE2-1:1
Mixing C and assembler

future. There are also several limitations to using inline assembler without operands and
clobbered resources:
● The inline assembler statement will be volatile and clobbered memory is not
implied. This means that the compiler will not remove the assembler statement. It
will simply be inserted at the given location in the program flow. The consequences
or side-effects that the insertion might have on the surrounding code are not taken
into consideration. If, for example, registers or memory locations are altered, they
might have to be restored within the sequence of inline assembler instructions for
the rest of the code to work properly.
The following example demonstrates the risks of using the asm keyword without
operands and clobbers:
int Add(int term1, int term2)
{
asm("add.w R13, R12");
return term1;
}

In this example:
● The function Add assumes that values are passed and returned in registers in a way
that they might not always be, for example if the function is inlined.
● The ADD instruction updates the condition flags, which you specify using the cc
clobber operand. Otherwise, the compiler will assume that the condition flags are
not modified.
Inline assembler without using operands or clobbered resources is therefore often best
avoided.

Reference information for inline assembler

The asm and __asm keywords both insert inline assembler instructions. However, when
you compile C source code, the asm keyword is not available when the option
--strict is used. The __asm keyword is always available.

Syntax The syntax of an inline assembler statement is (similar to the one used by GNU gcc):
asm [volatile]( string [assembler-interface])

string can contain one or more valid assembler instructions or data definition
assembler directives, separated by \n.

IAR C/C++ Compiler User Guide

172 for MSP430

AFE1_AFE2-1:1
 Assembler language interface

For example:
void LoopForever(void)
{
asm("label: nop\n"
" jmp label");
}

Note that any labels you define in the inline assembler statement will be local to that
statement. You can use this for loops or conditional code.
If you define a label in an inline assembler statement using two colons (for example:
"label:: nop\n") instead of one, the label will be public, not only in the inline
assembler statement, but in the module as well. This feature is intended for testing only.
assembler-interface is:
: comma-separated list of output operands /* optional */
: comma-separated list of input operands /* optional */
: comma-separated list of clobbered resources /* optional */

Operands An inline assembler statement can have one input and one output comma-separated list
of operands. Each operand consists of an optional symbolic name in brackets, a quoted
constraint, followed by a C expression in parentheses.

Syntax of operands [[ symbolic-name ]] "[modifiers]constraint" (expr)

For example:
int Add(int term1, int term2)
{
int sum;

asm("mov %1,%0\n"
"add %2,%0"
: "=r"(sum)
: "r"(term1), "r"(term2));

return sum;
}

In this example, the assembler instruction uses one output operand, sum, two input
operands, term1 and term2, and no clobbered resources.

173

AFE1_AFE2-1:1
Mixing C and assembler

It is possible to omit any list by leaving it empty. For example:

char matrix[M][N];

void MatrixSetBit(int row)

{
asm("BIS.W #1,0(%0)" : : "r" (&matrix[row][0]) : "memory");
}

Operand constraints
Constraint Description
r Uses a general purpose register or group of registers
R4-R15 A specific general purpose register or group of registers
i Integer constant (not valid as output)
m Operand referring to a memory location
digit The input must be in the same location as the output operand digit.
The first output operand is 0, the second 1, etc. (Not valid as output)
Table 21: Inline assembler operand constraints

Constraint modifiers Constraint modifiers can be used together with a constraint to modify its meaning. This
table lists the supported constraint modifiers:

Modifier Description
= Write-only operand
+ Read-write operand
& Early clobber output operand which is written to before the instruction
has processed all the input operands.
Table 22: Supported constraint modifiers

Referring to operands Assembler instructions refer to operands by prefixing their order number with %. The
first operand has order number 0 and is referred to by %0.
If the operand has a symbolic name, you can refer to it using the syntax
%[operand.name]. Symbolic operand names are in a separate namespace from C/C++
code and can be the same as a C/C++ variable names. Each operand name must however
be unique in each assembler statement.

IAR C/C++ Compiler User Guide

174 for MSP430

AFE1_AFE2-1:1
 Assembler language interface

For example:
int Add(int term1, int term2)
{
int sum;

asm("mov %[Rm], %[Rd]\n"

"add %[Rn], %[Rd]"
: [Rd]"=r"(sum)
: [Rn]"r"(term1), [Rm]"r"(term2));
return sum;
}

Input operands Input operands cannot have any constraint modifiers, but they can have any valid C
expression as long as the type of the expression fits the register.
The C expression will be evaluated just before any of the assembler instructions in the
inline assembler statement and assigned to the constraint, for example a register.

Output operands Output operands must have = as a constraint modifier and the C expression must be an
l-value and specify a writable location. For example, =r for a write-only general purpose
register. The constraint will be assigned to the evaluated C expression (as an l-value)
immediately after the last assembler instruction in the inline assembler statement. Input
operands are assumed to be consumed before output is produced and the compiler may
use the same register for an input and output operand. To prohibit this, prefix the output
constraint with & to make it an early clobber resource, for example =&r. This will ensure
that the output operand will be allocated in a different register than the input operands.

Input/output operands An operand that should be used both for input and output must be listed as an output
operand and have the + modifier. The C expression must be an l-value and specify a
writable location. The location will be read immediately before any assembler
instructions and it will be written to right after the last assembler instruction.
This is an example of using a read-write operand:
int Double(int value)
{
asm("add.w %0,%0" : "+r"(value));
return value;
}

In the example above, the input value for value will be placed in a general purpose
register. After the assembler statement, the result from the ADD instruction will be placed
in the same register.

175

AFE1_AFE2-1:1
Mixing C and assembler

Clobbered resources An inline assembler statement can have a list of clobbered resources.
"resource1", "resource2", ...

Specify clobbered resources to inform the compiler about which resources the inline
assembler statement destroys. Any value that resides in a clobbered resource and that is
needed after the inline assembler statement will be reloaded.
Clobbered resources will not be used as input or output operands.
This is an example of how to use clobbered resources:
int Add(int term1, int term2)
{
int sum;

asm("mov %1,%0\n"
"add %2,%0"
: "=r"(sum)
: "r" (term1), "r" (term2)
: "cc");

return sum;
}

In this example the condition codes will be modified by the ADD instruction. Therefore,
"cc" must be listed in the clobber list.

This table lists valid clobbered resources:

Clobber Description
R4-R15 General purpose register
cc The condition flags (N, Z, V, and C)
memory To be used if the instructions modify any memory. This will avoid
keeping memory values cached in registers across the inline
assembler statement.
Table 23: List of valid clobbers

IAR C/C++ Compiler User Guide

176 for MSP430

AFE1_AFE2-1:1
 Assembler language interface

Operand modifiers An operand modifier is a single letter between the % and the operand number, which is
used for transforming the operand.
In the example below, the modifiers A and B are used for accessing the least and most
significant 16 bits, respectively, of the operands:
unsigned long Mov32(void)
{
unsigned long sum;

asm("mov.w %A1,%A0\n"
"mov.w %B1,%B0"
: "=r"(sum)
: "i"(0x12345678UL));
return sum;
}

This table describes the transformation performed by each valid modifier:

Modifier Description
A The first (lowest) 16 bits of the operand.
B The second 16 bits of the operand.
C The third 16 bits of the operand. (64-bit types only)
D The fourth (highest) 16 bits of the operand. (64-bit types only)
Table 24: Operand modifiers and transformations

AN EXAMPLE OF HOW TO USE CLOBBERED MEMORY

In the example below, the inline assembler statement specifies that R8 and memory will
be written to.
void MemSet(char * memory, char value)
{
asm("mov.w %0, R8\n"
"mov.b %1, 0(R8)"
: /* No output constraints. */
: "r"(memory), "r"(value)
: "memory", "R8");
}

177

AFE1_AFE2-1:1
Calling assembler routines from C

Calling assembler routines from C

An assembler routine that will be called from C must:
● Conform to the calling convention
● Have a PUBLIC entry-point label
● Be declared as external before any call, to allow type checking and optional
promotion of parameters, as in these examples:
extern int foo(void);
or
extern int foo(int i, int j);

One way of fulfilling these requirements is to create skeleton code in C, compile it, and
study the assembler list file.

CREATING SKELETON CODE

The recommended way to create an assembler language routine with the correct
interface is to start with an assembler language source file created by the C compiler.
Note: You must create skeleton code for each function prototype.
The following example shows how to create skeleton code to which you can easily add
the functional body of the routine. The skeleton source code only needs to declare the
variables required and perform simple accesses to them. In this example, the assembler
routine takes an int and a char, and then returns an int:
extern int gInt;
extern char gChar;

int Func(int arg1, char arg2)

{
int locInt = arg1;
gInt = arg1;
gChar = arg2;
return locInt;
}

int main()
{
int locInt = gInt;
gInt = Func(locInt, gChar);
return 0;
}

Note: In this example, we use a low optimization level when compiling the code to show
local and global variable access. If a higher level of optimization is used, the required

IAR C/C++ Compiler User Guide

178 for MSP430

AFE1_AFE2-1:1
 Assembler language interface

references to local variables could be removed during the optimization. The actual
function declaration is not changed by the optimization level.

COMPILING THE SKELETON CODE

In the IDE, specify list options on file level. Select the file in the workspace window.
Then choose Project>Options. In the C/C++ Compiler category, select Override
inherited settings. On the List page, deselect Output list file, and instead select the
Output assembler file option and its suboption Include source. Also, be sure to specify
a low level of optimization.
Use these options to compile the skeleton code:
icc430 skeleton.c -lA . -On -e

The -lA option creates an assembler language output file including C or C++ source
lines as assembler comments. The . (period) specifies that the assembler file should be
named in the same way as the C or C++ module (skeleton), but with the filename
extension s43. The -On option means that no optimization will be used and -e enables
language extensions. In addition, make sure to use relevant compiler options, usually the
same as you use for other C or C++ source files in your project.
The result is the assembler source output file skeleton.s43.
Note: The -lA option creates a list file containing call frame information (CFI)
directives, which can be useful if you intend to study these directives and how they are
used. If you only want to study the calling convention, you can exclude the CFI
directives from the list file.
In the IDE, to exclude the CFI directives from the list file, choose
Project>Options>C/C++ Compiler>List and deselect the suboption Include call
frame information.
On the command line, to exclude the CFI directives from the list file, use the option -lB
instead of -lA.
Note: CFI information must be included in the source code to make the C-SPY Call
Stack window work.

The output file

The output file contains the following important information:
● The calling convention
● The return values
● The global variables
● The function parameters

179

AFE1_AFE2-1:1
Calling assembler routines from C++

● How to create space on the stack (auto variables)

● Call frame information (CFI).
The CFI directives describe the call frame information needed by the Call Stack
window in the debugger. For more information, see Call frame information, page 193.

Calling assembler routines from C++

The C calling convention does not apply to C++ functions. Most importantly, a function
name is not sufficient to identify a C++ function. The scope and the type of the function
are also required to guarantee type-safe linkage, and to resolve overloading.
Another difference is that non-static member functions get an extra, hidden argument,
the this pointer.
However, when using C linkage, the calling convention conforms to the C calling
convention. An assembler routine can therefore be called from C++ when declared in
this manner:
extern "C"
{
int MyRoutine(int);
}

In C++, data structures that only use C features are known as PODs (“plain old data
structures”), they use the same memory layout as in C. However, we do not recommend
that you access non-PODs from assembler routines.
The following example shows how to achieve the equivalent to a non-static member
function, which means that the implicit this pointer must be made explicit. It is also
possible to “wrap” the call to the assembler routine in a member function. Use an inline

IAR C/C++ Compiler User Guide

180 for MSP430

AFE1_AFE2-1:1
 Assembler language interface

member function to remove the overhead of the extra call—this assumes that function
inlining is enabled:
class MyClass;

extern "C"
{
void DoIt(MyClass *ptr, int arg);
}

class MyClass
{
public:
inline void DoIt(int arg)
{
::DoIt(this, arg);
}
};

Note: Support for C++ names from assembler code is extremely limited. This means
that:
● Assembler list files resulting from compiling C++ files cannot, in general, be passed
through the assembler.
● It is not possible to refer to or define C++ functions that do not have C linkage in
assembler.

Calling convention
A calling convention is the way a function in a program calls another function. The
compiler handles this automatically, but, if a function is written in assembler language,
you must know where and how its parameters can be found, how to return to the program
location from where it was called, and how to return the resulting value.
It is also important to know which registers an assembler-level routine must preserve. If
the program preserves too many registers, the program might be ineffective. If it
preserves too few registers, the result would be an incorrect program.
The compiler provides two calling conventions—Version1 and Version2. This section
describes the calling conventions used by the compiler. These items are examined:
● Choosing a calling convention
● Function declarations
● C and C++ linkage
● Preserved versus scratch registers

181

AFE1_AFE2-1:1
Calling convention

● Function entrance
● Function exit
● Return address handling
At the end of the section, some examples are shown to describe the calling convention
in practice.

CHOOSING A CALLING CONVENTION

The compiler supports three calling conventions:
● The Version1 calling convention is used by version 1.x, 2.x, and 3.x of the compiler
● The Version2 calling convention was introduced with version 4.x of the compiler. It
is more efficient than the Version1 calling convention.
● The ROM calling convention is a restricted calling convention intended for ROM
library functions. See The ROM calling convention, page 183.
You can explicitly specify the calling convention when you declare and define functions.
However, normally this is not needed, unless the function is written in assembler.
For old routines written in assembler and that use the Version1 calling convention, the
function attribute __cc_version1 should be used, for example:
extern __cc_version1 void doit(int arg);

New routines written in assembler should be declared using the function attribute
__cc_version2. This ensures that they will be called using the Version2 calling
convention if new calling conventions are introduced in future compilers.

Hints for a quick introduction to the calling conventions

Both calling conventions are complex and if you intend to use any of them for your
assembler routines, you should create a list file and see how the compiler assigns the
different parameters to the available registers. For an example, see Creating skeleton
code, page 178.
You should also specify a value to the runtime model attribute __rt_version using the
RTMODEL assembler directive:

RTMODEL "__rt_version", "value"

The parameter value should have the same value as the one used internally by the
compiler. For information about what value to use, see the generated list file. If the
calling convention changes in future compiler versions, the runtime model value used
internally by the compiler will also change. Using this method gives a module
consistency check, because the linker produces errors for mismatches between the
values.

IAR C/C++ Compiler User Guide

182 for MSP430

AFE1_AFE2-1:1
 Assembler language interface

For more information about checking module consistency, see Checking module
consistency, page 111.

The ROM calling convention

In addition to the two full calling conventions, the compiler supports a restricted calling
convention intended for ROM library functions. This has been designed to allow the
ROM library functions to be more compatible with different toolchains and build
settings. It is associated with the function type attribute __cc_rom.
There is no need for an application to use this calling convention other than for calling
functions in a ROM library.
The ROM calling convention differs from the Version2 calling convention in these ways:
● All ROM functions must have C linkage.
● On 430X devices, calls to ROM functions behave as if the large code model was
used, that is, the CALLA instruction is always used, and the function address is 32 or
20 bits depending on the data model settings.
● The register R11 is not preserved by the ROM functions.
● For the preserved registers. R4-R10, the full 20 bits are always preserved.
● The ROM functions can use the most significant four bits of any 20-bit register, so
any interrupt handlers in the application must preserve those. For more information,
see --save_reg20, page 297.
Furthermore, the ROM calling convention places restrictions on how parameters and
return values are passed to and from the ROM functions. These restrictions are checked
by the compiler:
● All parameters and return values must be passed in registers. There must be no
parameters or return values on the stack.
● It is not allowed to pass a register pair as the second parameter after a single-register
parameter.
● Only scalar parameters and return values are allowed.
● Function pointers are not allowed as parameters or return values.
● Enum values are not allowed as parameters or return values.
● Doubles are not allowed as parameters or return values.
● Data pointers must point to __data20 memory.
The type restrictions also apply recursively to members of structs or arrays that are
pointed to by data pointers.

183

AFE1_AFE2-1:1
Calling convention

FUNCTION DECLARATIONS
In C, a function must be declared in order for the compiler to know how to call it. A
declaration could look as follows:
int MyFunction(int first, char * second);

This means that the function takes two parameters: an integer and a pointer to a
character. The function returns a value, an integer.
In the general case, this is the only knowledge that the compiler has about a function.
Therefore, it must be able to deduce the calling convention from this information.

USING C LINKAGE IN C++ SOURCE CODE

In C++, a function can have either C or C++ linkage. To call assembler routines from
C++, it is easiest if you make the C++ function have C linkage.
This is an example of a declaration of a function with C linkage:
extern "C"
{
int F(int);
}

It is often practical to share header files between C and C++. This is an example of a
declaration that declares a function with C linkage in both C and C++:
#ifdef __cplusplus
extern "C"
{
#endif

int F(int);

#ifdef __cplusplus
}
#endif

PRESERVED VERSUS SCRATCH REGISTERS

The general MSP430 CPU registers are divided into three separate sets, which are
described in this section.

Scratch registers
Any function is permitted to destroy the contents of a scratch register. If a function needs
the register value after a call to another function, it must store it during the call, for
example on the stack.

IAR C/C++ Compiler User Guide

184 for MSP430

AFE1_AFE2-1:1
 Assembler language interface

Any of the registers R12 to R15 are considered scratch registers and can be used by the
function.
When the registers R11:R10:R9:R8 are used for passing a 64-bit scalar parameter, they
are also considered to be scratch registers.

Preserved registers
Preserved registers, on the other hand, are preserved across function calls. The called
function can use the register for other purposes, but must save the value before using the
register and restore it at the exit of the function.
The registers R4 to R11 are preserved registers.
If the registers R11:R10:R9:R8 are used for passing a 64-bit scalar parameter, they do
not have to be preserved.
Note: When compiling for the MSP430X architecture in the Small data model, only the
lower 16 bits of the registers are preserved, unless the __save_reg20 attribute is
specified. Because the code generated by the compiler in the Small data model does not
use the upper four bits of registers, it is only necessary to save and restore these bits if
they are used by any assembler routines.
Note: When compiling using the options --lock_r4 or --lock_r5, the R4 and R5
registers are not used.

FUNCTION ENTRANCE
Parameters can be passed to a function using one of these basic methods:
● In registers
● On the stack
It is much more efficient to use registers than to take a detour via memory, so the calling
convention is designed to use registers as much as possible. Only a limited number of
registers can be used for passing parameters; when no more registers are available, the
remaining parameters are passed on the stack. The parameters are also passed on the
stack in these cases:
● Structure types: struct, union, and classes
● Unnamed parameters to variable length (variadic) functions; in other words,
functions declared as foo(param1, ...), for example printf.
Note: Interrupt functions cannot take any parameters.

185

AFE1_AFE2-1:1
Calling convention

Hidden parameters
In addition to the parameters visible in a function declaration and definition, there can
be hidden parameters:
● If the function returns a structure, the memory location where to store the structure
is passed in the register R12 as a hidden parameter.
● If the function is a non-static C++ member function, then the this pointer is passed
as the first parameter (but placed after the return structure pointer, if there is one).
The reason for the requirement that the member function must be non-static is that
static member methods do not have a this pointer.

Register parameters
These registers are available for passing parameters:
Parameters Passed in registers, Version1 Passed in registers, Version2
8-bit values R12, R14 R12 to R15
16-bit values R12, R14 R12 to R15
20-bit values* R12, R14 R12 to R15
32-bit values (R13:R12), (R15:R14) (R13:R12), (R15:R14)
64-bit values (R15:R14:R13:R12), (R15:R14:R13:R12),
(R11:R10:R9:R8) (R11:R10:R9:R8)
Table 25: Registers used for passing parameters

* On MSP430X devices, if the Small data model is combined with the Large code
model, function pointers are passed as 32-bit values.
The assignment of registers to parameters is a straightforward process.
For Version1, the first parameter is assigned to R12 or R13:R12, depending on the size
of the parameter. The second parameter is passed in R14 or R15:R14. Should there be
no more available registers, the parameter is passed on the stack.
For Version2, each parameter is assigned to the first register that has not already been
assigned a parameter, starting from R12.

Stack parameters and layout

Stack parameters are stored in the main memory, starting at the location pointed to by
the stack pointer. Below the stack pointer (toward low memory) there is free space that
the called function can use. The first stack parameter is stored at the location pointed to
by the stack pointer. The next one is stored at the next even location on the stack. It is
the responsibility of the caller to remove the parameters from the stack by restoring the
stack pointer.

IAR C/C++ Compiler User Guide

186 for MSP430

AFE1_AFE2-1:1
 Assembler language interface

This figure illustrates how parameters are stored on the stack:

FUNCTION EXIT
A function can return a value to the function or program that called it, or it can have the
return type void.
The return value of a function, if any, can be scalar (such as integers and pointers),
floating-point, or a structure.
Note: An interrupt function must have the return type void.

Registers used for returning values

These registers are available for returning values:
Return values Passed in registers
8-bit values R12
16-bit values R12
*
20-bit values R12
32-bit values (R13:R12)
64-bit values (R15:R14:R13:R12)
Table 26: Registers used for returning values

* On MSP430X devices, if the Small data model is combined with the Large code
model, function pointers are returned as 32-bit values.

Stack layout at function exit

It is the responsibility of the caller to clean the stack after the called function returns.

187

AFE1_AFE2-1:1
Calling convention

RESTRICTIONS FOR SPECIAL FUNCTION TYPES

For information about how the __interrupt, __raw, and __save_reg20 keywords
affect the calling convention, see Interrupt functions, page 73.

EXAMPLES
The following section shows a series of declaration examples and the corresponding
calling conventions. The complexity of the examples increases toward the end.

Example 1
Assume this function declaration:
int add1(int);

This function takes one parameter in the register R12, and the return value is passed back
to its caller in the register R12.
This assembler routine is compatible with the declaration; it will return a value that is
one number higher than the value of its parameter:
add.w #1,R12
ret

Example 2
This example shows how structures are passed on the stack. Assume these declarations:
struct MyStruct
{
short a;
short b;
short c;
short d;
short e;
};

int MyFunction(struct MyStruct x, int y);

The calling function must reserve 10 bytes on the top of the stack and copy the contents
of the struct to that location. The integer parameter y is passed in the register R12. The
return value is passed back to its caller in the register R12.

IAR C/C++ Compiler User Guide

188 for MSP430

AFE1_AFE2-1:1
 Assembler language interface

Example 3
The function below will return a structure of type struct MyStruct.
struct MyStruct
{
int mA[20];
};

struct MyStruct MyFunction(int x);

It is the responsibility of the calling function to allocate a memory location for the return
value—typically on the stack—and pass a pointer to it as a hidden first parameter. The
pointer to the location where the return value should be stored is passed in R12. The
caller assumes that this register remains untouched. The parameter x is passed in R13.
Assume that the function instead was declared to return a pointer to the structure:
struct MyStruct *MyFunction(int x);

In this case, the return value is a pointer, so there is no hidden parameter. The parameter
x is passed in R12 and the return value is also returned in R12.

Assembler instructions used for calling functions

This section presents the assembler instructions that can be used for calling and
returning from functions on the MSP430 microcontroller.
Functions can be called in different ways—directly or via a function pointer. In this
section we will discuss how these types of calls will be performed for each core and code
model.

NORMAL (NON-ROPI) CODE

If the --ropi option is not specified, the following instruction sequences are used for
calling and returning from functions.

MSP430 and MSP430X using the Small code model

For the MSP430 core, and for the MSP430X core when the Small code model is used,
functions are called with the CALL instruction, and returned from with the RET
instruction.
The return address is stored on the stack and uses 2 bytes of memory.

189

AFE1_AFE2-1:1
Assembler instructions used for calling functions

MSP430X using the Large code model

For the MSP430X core when the Large code model is used, functions are called with the
CALLA instruction, and returned from with the RETA instruction.

The return address is stored on the stack and uses 4 bytes of memory.

POSITION-INDEPENDENT CODE AND READ-ONLY DATA

When the --ropi option is specified, the following instruction sequences are used for
calling and returning from functions.

MSP430 and MSP430X using the Small code model

For the MSP430 core, and for the MSP430X core when the Small code model is used,
functions are called with:
push.w PC
add.w #(func)-($-4), PC

The return address is stored on the stack and uses 2 bytes of memory. It must be adjusted
before returning from the function:
add.w #0x4, 0(SP)
ret

MSP430X using the Large code model

For the MSP430X core when the Large code model is used, functions are called with:
pushm.a #0x1, PC
adda #(func)-($-4-?CPU30_OFFSET), PC

The return address is stored on the stack and uses 4 bytes of memory. It must be adjusted
before returning from the function:
addx.a #0x4, 0(SP)
reta

Note: The symbol ?CPU30_OFFSET is given different values in the device-specific

linker configuration files, to compensate for hardware defect CPU30.

INTERRUPT FUNCTIONS
Interrupt functions always return using the RETI instructions. This restores the status
registers and returns to the location where the interrupt occurred.

IAR C/C++ Compiler User Guide

190 for MSP430

AFE1_AFE2-1:1
 Assembler language interface

MODULE CONSISTENCY
When calling an assembler module from C modules, it is important to match the calling
convention.
Because the calling convention differs slightly between the two architectures, you can
define the runtime attribute __core in all your assembler routines, to avoid
inconsistency. Use one of the following lines:
RTMODEL "__core","430"
RTMODEL "__core","430X"

Also, for MSP430X devices, define the runtime attribute __code_model. Use one of:
RTMODEL "__code_model","small"
RTMODEL "__code_model","large"

Using these module consistency checks, the linker will produce an error if there is a
mismatch between the values.
For more information about checking module consistency, see Checking module
consistency, page 111.

Memory access methods

This section describes the different memory types presented in the chapter Data storage.
In addition to presenting the assembler code used for accessing data, this section will
explain the reason behind the different memory types.
You should be familiar with the MSP430 instruction set, in particular the different
addressing modes used by the instructions that can access memory.
For each of the access methods described in the following sections, there are three
examples:
● Accessing a global variable
● Accessing a global array using an unknown index
● Accessing a structure using a pointer.

191

AFE1_AFE2-1:1
Memory access methods

These three examples can be illustrated by this C program:

char myVar;
char MyArr[10];

struct MyStruct
{
long mA;
char mB;
};

char Foo(int i, struct MyStruct *p)

{
return myVar + MyArr[i] + p->mB;
}

THE DATA16 MEMORY ACCESS METHOD

The data16 memory consists of the low 64 Kbytes of memory. In hexadecimal notation,
this is the address range 0x0000-0xFFFF.
A pointer to data16 memory is 16 bits and occupies two bytes when stored in memory.
Direct accesses to data16 memory are performed using normal (non-extended)
instructions. This means a smaller footprint for the application, and faster execution at
run-time.

Examples
These examples access data16 memory in different ways:
mov.b &myVar,R14

mov.b MyArr(R12),R14

mov.b 0x4(R13),R14

THE DATA20 MEMORY ACCESS METHOD

Using this memory type, you can place the data objects anywhere in the entire memory
range 0x00000–0xFFFFF. This requires the extended instructions of the MSP430X
architecture, which are more expensive. Note that a pointer to data20 memory will
occupy four bytes of memory, which is twice the amount needed for data16 memory.

IAR C/C++ Compiler User Guide

192 for MSP430

AFE1_AFE2-1:1
 Assembler language interface

Examples
These examples access data20 memory in different ways:
movx.b &myVar,R14

movx.b MyArr(R12),R14

mov.b 0x4(R13),R14

Call frame information

When you debug an application using C-SPY, you can view the call stack, that is, the
chain of functions that called the current function. To make this possible, the compiler
supplies debug information that describes the layout of the call frame, in particular
information about where the return address is stored.
If you want the call stack to be available when debugging a routine written in assembler
language, you must supply equivalent debug information in your assembler source using
the assembler directive CFI. This directive is described in detail in the IAR Assembler
User Guide for MSP430.

CFI DIRECTIVES
The CFI directives provide C-SPY with information about the state of the calling
function(s). Most important of this is the return address, and the value of the stack
pointer at the entry of the function or assembler routine. Given this information, C-SPY
can reconstruct the state for the calling function, and thereby unwind the stack.
A full description about the calling convention might require extensive call frame
information. In many cases, a more limited approach will suffice.
When describing the call frame information, the following three components must be
present:
● A names block describing the available resources to be tracked
● A common block corresponding to the calling convention
● A data block describing the changes that are performed on the call frame. This
typically includes information about when the stack pointer is changed, and when
permanent registers are stored or restored on the stack.
This table lists all the resources defined in the names block used by the compiler:
Resource Description
CFA The call frames of the stack
Table 27: Call frame information resources defined in a names block

193

AFE1_AFE2-1:1
Call frame information

Resource Description
R4–R15 Normal registers
R4L–R15L Lower 16 bits, when compiling for the MSP430X architecture
R4H–R15H Higher 4 bits, when compiling for the MSP430X architecture
SP The stack pointer
SR The processor state register
PC The program counter
Table 27: Call frame information resources defined in a names block (Continued)

CREATING ASSEMBLER SOURCE WITH CFI SUPPORT

1 Start with suitable C source code, for example:
int F(int);
int cfiExample(int i)
{
return i + F(i);
}

2 Compile the C source code, and make sure to create a list file that contains call frame
information—the CFI directives.
On the command line, use the option -lA.

In the IDE, choose Project>Options>C/C++ Compiler>List and make sure the

suboption Include call frame information is selected.

IAR C/C++ Compiler User Guide

194 for MSP430

AFE1_AFE2-1:1
 Assembler language interface

For the source code in this example, the list file looks like this:
NAME `Cfi`

RTMODEL "__core", "430"

RTMODEL "__double_size", "32"
RTMODEL "__pic", "no"
RTMODEL "__reg_r4", "free"
RTMODEL "__reg_r5", "free"
RTMODEL "__rt_version", "3"

RSEG CSTACK:DATA:SORT:NOROOT(0)

EXTERN ?longjmp_r4
EXTERN ?longjmp_r5
EXTERN ?setjmp_r4
EXTERN ?setjmp_r5

PUBWEAK ?setjmp_save_r4
PUBWEAK ?setjmp_save_r5
PUBLIC cfiExample
FUNCTION cfiExample,021203H
ARGFRAME CSTACK, 0, STACK
LOCFRAME CSTACK, 4, STACK

CFI Names cfiNames0

CFI StackFrame CFA SP DATA
CFI Resource PC:16, SP:16, SR:16, R4:16, R5:16, R6:16,
R7:16, R8:16
CFI Resource R9:16, R10:16, R11:16, R12:16, R13:16,
R14:16, R15:16
CFI EndNames cfiNames0

CFI Common cfiCommon0 Using cfiNames0

CFI CodeAlign 2
CFI DataAlign 2
CFI ReturnAddress PC CODE
CFI CFA SP+2
CFI PC Frame(CFA, -2)
CFI SR Undefined
CFI R4 SameValue
CFI R5 SameValue
CFI R6 SameValue
CFI R7 SameValue
CFI R8 SameValue
CFI R9 SameValue
CFI R10 SameValue
CFI R11 SameValue

195

AFE1_AFE2-1:1
Call frame information

CFI R12 Undefined

CFI R13 Undefined
CFI R14 Undefined
CFI R15 Undefined
CFI EndCommon cfiCommon0

EXTERN F
FUNCTION F,0202H

RSEG CODE:CODE:REORDER:NOROOT(1)
cfiExample:
CFI Block cfiBlock0 Using cfiCommon0
CFI Function cfiExample
FUNCALL cfiExample, F
LOCFRAME CSTACK, 4, STACK
PUSH.W R10
CFI R10 Frame(CFA, -4)
CFI CFA SP+4
MOV.W R12, R10
MOV.W R10, R12
CALL #F
ADD.W R12, R10
MOV.W R10, R12
POP.W R10
CFI R10 SameValue
CFI CFA SP+2
RET
CFI EndBlock cfiBlock0

RSEG CODE:CODE:REORDER:NOROOT(1)
?setjmp_save_r4:
REQUIRE ?setjmp_r4
REQUIRE ?longjmp_r4

RSEG CODE:CODE:REORDER:NOROOT(1)
?setjmp_save_r5:
REQUIRE ?setjmp_r5
REQUIRE ?longjmp_r5

END

Note: The header file cfi.m43 contains the macros XCFI_NAMES and XCFI_COMMON,
which declare a typical names block and a typical common block. These two macros
declare several resources, both concrete and virtual.

IAR C/C++ Compiler User Guide

196 for MSP430

AFE1_AFE2-1:1
 Using C
● C language overview

● Extensions overview

● IAR C language extensions

C language overview
The IAR C/C++ Compiler for MSP430 supports the ISO/IEC 9899:1999 standard
(including up to technical corrigendum No.3), also known as C99. In this guide, this
standard is referred to as Standard C and is the default standard used in the compiler.
This standard is stricter than C89.
In addition, the compiler also supports the ISO 9899:1990 standard (including all
technical corrigenda and addenda), also known as C94, C90, C89, and ANSI C. In this
guide, this standard is referred to as C89. Use the --c89 compiler option to enable this
standard.
The C99 standard is derived from C89, but adds features like these:
● The inline keyword advises the compiler that the function defined immediately
after the keyword should be inlined
● Declarations and statements can be mixed within the same scope
● A declaration in the initialization expression of a for loop
● The bool data type
● The long long data type
● The complex floating-point type
● C++ style comments
● Compound literals
● Incomplete arrays at the end of structs
● Hexadecimal floating-point constants
● Designated initializers in structures and arrays
● The preprocessor operator _Pragma()
● Variadic macros, which are the preprocessor macro equivalents of printf style
functions
● VLA (variable length arrays) must be explicitly enabled with the compiler option
--vla

197

AFE1_AFE2-1:1
Extensions overview

● Inline assembler using the asm or the __asm keyword, see Inline assembler, page
171.
Note: Even though it is a C99 feature, the IAR C/C++ Compiler for MSP430 does not
support UCNs (universal character names).
Note: CLIB does not support any C99 functionality. For example, complex numbers and
variable length arrays are not supported.

Extensions overview
The compiler offers the features of Standard C and a wide set of extensions, ranging
from features specifically tailored for efficient programming in the embedded industry
to the relaxation of some minor standards issues.
This is an overview of the available extensions:
● IAR C language extensions
For information about available language extensions, see IAR C language extensions,
page 199. For more information about the extended keywords, see the chapter
Extended keywords. For information about C++, the two levels of support for the
language, and C++ language extensions, see the chapter Using C++.
● Pragma directives
The #pragma directive is defined by Standard C and is a mechanism for using
vendor-specific extensions in a controlled way to make sure that the source code is
still portable.
The compiler provides a set of predefined pragma directives, which can be used for
controlling the behavior of the compiler, for example, how it allocates memory,
whether it allows extended keywords, and whether it outputs warning messages.
Most pragma directives are preprocessed, which means that macros are substituted
in a pragma directive. The pragma directives are always enabled in the compiler. For
several of them there is also a corresponding C/C++ language extension. For
information about available pragma directives, see the chapter Pragma directives.
● Preprocessor extensions
The preprocessor of the compiler adheres to Standard C. The compiler also makes
several preprocessor-related extensions available to you. For more information, see
the chapter The preprocessor.
● Intrinsic functions
The intrinsic functions provide direct access to low-level processor operations and
can be useful in, for example, time-critical routines. The intrinsic functions compile
into inline code, either as a single instruction or as a short sequence of instructions.
For more information about using intrinsic functions, see Mixing C and assembler,

IAR C/C++ Compiler User Guide

198 for MSP430

AFE1_AFE2-1:1
 Using C

page 169. For information about available functions, see the chapter Intrinsic
functions.
● Library functions
The DLIB runtime environment provides the C and C++ library definitions in the
C/C++ standard library that apply to embedded systems. For more information, see
DLIB runtime environment—implementation details, page 379.
Note: Any use of these extensions, except for the pragma directives, makes your source
code inconsistent with Standard C.

ENABLING LANGUAGE EXTENSIONS

You can choose different levels of language conformance by means of project options:
Command line IDE* Description
--strict Strict All IAR C language extensions are disabled—
errors are issued for anything that is not part
of Standard C.
None Standard All extensions to Standard C are enabled, but no
extensions for embedded systems programming.
For information about extensions, see IAR C
language extensions, page 199.
-e Standard with IAR All IAR C language extensions are enabled.
extensions
Table 28: Language extensions

* In the IDE, choose Project>Options>C/C++ Compiler>Language 1>Language

conformance and select the appropriate option. Note that language extensions are
enabled by default.

IAR C language extensions

The compiler provides a wide set of C language extensions. To help you to find the
extensions required by your application, they are grouped like this in this section:
● Extensions for embedded systems programming—extensions specifically tailored
for efficient embedded programming for the specific microcontroller you are using,
typically to meet memory restrictions
● Relaxations to Standard C—that is, the relaxation of some minor Standard C issues
and also some useful but minor syntax extensions, see Relaxations to Standard C,
page 202.

199

AFE1_AFE2-1:1
IAR C language extensions

EXTENSIONS FOR EMBEDDED SYSTEMS PROGRAMMING

The following language extensions are available both in the C and the C++
programming languages and they are well suited for embedded systems programming:
● Memory attributes, type attributes, and object attributes
For information about the related concepts, the general syntax rules, and for
reference information, see the chapter Extended keywords.
● Placement at an absolute address or in a named segment
The @ operator or the directive #pragma location can be used for placing global
and static variables at absolute addresses, or placing a variable or function in a named
segment. For more information about using these features, see Controlling data and
function placement in memory, page 236, and location, page 344.
● Alignment control
Each data type has its own alignment; for more information, see Alignment, page
303. If you want to change the alignment, the #pragma pack, and the #pragma
data_alignment directives are available. If you want to check the alignment of an
object, use the __ALIGNOF__() operator.
The __ALIGNOF__ operator is used for accessing the alignment of an object. It takes
one of two forms:
● __ALIGNOF__ (type)
● __ALIGNOF__ (expression)
In the second form, the expression is not evaluated.
● Anonymous structs and unions
C++ includes a feature called anonymous unions. The compiler allows a similar
feature for both structs and unions in the C programming language. For more
information, see Anonymous structs and unions, page 235.
● Bitfields and non-standard types
In Standard C, a bitfield must be of the type int or unsigned int. Using IAR C
language extensions, any integer type or enumeration can be used. The advantage is
that the struct will sometimes be smaller. For more information, see Bitfields, page
306.
● static_assert()
The construction static_assert(const-expression,"message"); can be
used in C/C++. The construction will be evaluated at compile time and if
const-expression is false, a message will be issued including the message
string.

IAR C/C++ Compiler User Guide

200 for MSP430

AFE1_AFE2-1:1
 Using C

● Parameters in variadic macros

Variadic macros are the preprocessor macro equivalents of printf style functions.
The preprocessor accepts variadic macros with no arguments, which means if no
parameter matches the ... parameter, the comma is then deleted in the ",
##__VA_ARGS__" macro definition. According to Standard C, the ... parameter
must be matched with at least one argument.

Dedicated segment operators

The compiler supports getting the start address, end address, and size for a segment with
these built-in segment operators:

__segment_begin Returns the address of the first byte of the named segment.
__segment_end Returns the address of the first byte after the named segment.
__segment_size Returns the size of the named segment in bytes.

The operators can be used on named segments defined in the linker configuration file.
These operators behave syntactically as if declared like:
void * __segment_begin(char const * segment)
void * __segment_end(char const * segment)
size_t __segment_size(char const * segment)

When you use the @ operator or the #pragma location directive to place a data object
or a function in a user-defined segment in the linker configuration file, the segment
operators can be used for getting the start and end address of the memory range where
the segments were placed.
The named segment must be a string literal and it must have been declared earlier with
the #pragma segment directive. If the segment was declared with a memory attribute
memattr, the type of the __segment_begin operator is a pointer to memattr void.
Otherwise, the type is a default pointer to void. Note that you must enable language
extensions to use these operators.
Note: These segment operators always return the linked address of a segment. When
ROPI is used, you must add the code distance to get the actual address, see
__code_distance, page 358.

Example
In this example, the type of the __segment_begin operator is void __data16 *.
#pragma segment="MYSEGMENT" __data16
...
segment_start_address = __segment_begin("MYSEGMENT");

201

AFE1_AFE2-1:1
IAR C language extensions

See also segment, page 350, and location, page 344.

RELAXATIONS TO STANDARD C
This section lists and briefly describes the relaxation of some Standard C issues and also
some useful but minor syntax extensions:
● Arrays of incomplete types
An array can have an incomplete struct, union, or enum type as its element type.
The types must be completed before the array is used (if it is), or by the end of the
compilation unit (if it is not).
● Forward declaration of enum types
The extensions allow you to first declare the name of an enum and later resolve it by
specifying the brace-enclosed list.
● Accepting missing semicolon at the end of a struct or union specifier
A warning—instead of an error—is issued if the semicolon at the end of a struct
or union specifier is missing.
● Null and void
In operations on pointers, a pointer to void is always implicitly converted to another
type if necessary, and a null pointer constant is always implicitly converted to a null
pointer of the right type if necessary. In Standard C, some operators allow this kind
of behavior, while others do not allow it.
● Casting pointers to integers in static initializers
In an initializer, a pointer constant value can be cast to an integral type if the integral
type is large enough to contain it. For more information about casting pointers, see
Casting, page 310.
● Taking the address of a register variable
In Standard C, it is illegal to take the address of a variable specified as a register
variable. The compiler allows this, but a warning is issued.
● long float means double
The type long float is accepted as a synonym for double.
● Repeated typedef declarations
Redeclarations of typedef that occur in the same scope are allowed, but a warning
is issued.
● Mixing pointer types
Assignment and pointer difference is allowed between pointers to types that are
interchangeable but not identical; for example, unsigned char * and char *. This
includes pointers to integral types of the same size. A warning is issued.

IAR C/C++ Compiler User Guide

202 for MSP430

AFE1_AFE2-1:1
 Using C

Assignment of a string constant to a pointer to any kind of character is allowed, and

no warning is issued.
● Non-top level const
Assignment of pointers is allowed in cases where the destination type has added type
qualifiers that are not at the top level (for example, int ** to int const **).
Comparing and taking the difference of such pointers is also allowed.
● Non-lvalue arrays
A non-lvalue array expression is converted to a pointer to the first element of the
array when it is used.
● Comments at the end of preprocessor directives
This extension, which makes it legal to place text after preprocessor directives, is
enabled unless the strict Standard C mode is used. The purpose of this language
extension is to support compilation of legacy code; we do not recommend that you
write new code in this fashion.
● An extra comma at the end of enum lists
Placing an extra comma is allowed at the end of an enum list. In strict Standard C
mode, a warning is issued.
● A label preceding a }
In Standard C, a label must be followed by at least one statement. Therefore, it is
illegal to place the label at the end of a block. The compiler allows this, but issues a
warning.
Note that this also applies to the labels of switch statements.
● Empty declarations
An empty declaration (a semicolon by itself) is allowed, but a remark is issued
(provided that remarks are enabled).
● Single-value initialization
Standard C requires that all initializer expressions of static arrays, structs, and unions
are enclosed in braces.
Single-value initializers are allowed to appear without braces, but a warning is
issued. The compiler accepts this expression:
struct str
{
int a;
} x = 10;

203

AFE1_AFE2-1:1
IAR C language extensions

● Declarations in other scopes

External and static declarations in other scopes are visible. In the following example,
the variable y can be used at the end of the function, even though it should only be
visible in the body of the if statement. A warning is issued.
int test(int x)
{
if (x)
{
extern int y;
y = 1;
}

return y;
}
● Expanding function names into strings with the function as context
Use any of the symbols __func__ or __FUNCTION__ inside a function body to
make the symbol expand into a string that contains the name of the current function.
Use the symbol __PRETTY_FUNCTION__ to also include the parameter types and
return type. The result might, for example, look like this if you use the
__PRETTY_FUNCTION__ symbol:
"void func(char)"
These symbols are useful for assertions and other trace utilities and they require that
language extensions are enabled, see -e, page 278.
● Static functions in function and block scopes
Static functions may be declared in function and block scopes. Their declarations are
moved to the file scope.
● Numbers scanned according to the syntax for numbers
Numbers are scanned according to the syntax for numbers rather than the
pp-number syntax. Thus, 0x123e+1 is scanned as three tokens instead of one valid
token. (If the --strict option is used, the pp-number syntax is used instead.)

IAR C/C++ Compiler User Guide

204 for MSP430

AFE1_AFE2-1:1
 Using C++
● Overview—EC++ and EEC++

● Enabling support for C++

● EC++ feature descriptions

● EEC++ feature description

● C++ language extensions

Overview—EC++ and EEC++

IAR Systems supports the C++ language. You can choose between the industry-standard
Embedded C++ and Extended Embedded C++. Using C++ describes what you need to
consider when using the C++ language.
Embedded C++ is a proper subset of the C++ programming language which is intended
for embedded systems programming. It was defined by an industry consortium, the
Embedded C++ Technical Committee. Performance and portability are particularly
important in embedded systems development, which was considered when defining the
language. EC++ offers the same object-oriented benefits as C++, but without some
features that can increase code size and execution time in ways that are hard to predict.

EMBEDDED C++
These C++ features are supported:
● Classes, which are user-defined types that incorporate both data structure and
behavior; the essential feature of inheritance allows data structure and behavior to
be shared among classes
● Polymorphism, which means that an operation can behave differently on different
classes, is provided by virtual functions
● Overloading of operators and function names, which allows several operators or
functions with the same name, provided that their argument lists are sufficiently
different
● Type-safe memory management using the operators new and delete
● Inline functions, which are indicated as particularly suitable for inline expansion.

205

AFE1_AFE2-1:1
Overview—EC++ and EEC++

C++ features that are excluded are those that introduce overhead in execution time or
code size that are beyond the control of the programmer. Also excluded are features
added very late before Standard C++ was defined. Embedded C++ thus offers a subset
of C++ which is efficient and fully supported by existing development tools.
Embedded C++ lacks these features of C++:
● Templates
● Multiple and virtual inheritance
● Exception handling
● Runtime type information
● New cast syntax (the operators dynamic_cast, static_cast,
reinterpret_cast, and const_cast)
● Namespaces
● The mutable attribute.
The exclusion of these language features makes the runtime library significantly more
efficient. The Embedded C++ library furthermore differs from the full C++ library in
that:
● The standard template library (STL) is excluded
● Streams, strings, and complex numbers are supported without the use of templates
● Library features which relate to exception handling and runtime type information
(the headers except, stdexcept, and typeinfo) are excluded.
Note: The library is not in the std namespace, because Embedded C++ does not
support namespaces.

EXTENDED EMBEDDED C++

IAR Systems’ Extended EC++ is a slightly larger subset of C++ which adds these
features to the standard EC++:
● Full template support
● Multiple and virtual inheritance
● Namespace support
● The mutable attribute
● The cast operators static_cast, const_cast, and reinterpret_cast.
All these added features conform to the C++ standard.
To support Extended EC++, this product includes a version of the standard template
library (STL), in other words, the C++ standard chapters utilities, containers, iterators,
algorithms, and some numerics. This STL is tailored for use with the Extended EC++

IAR C/C++ Compiler User Guide

206 for MSP430

AFE1_AFE2-1:1
 Using C++

language, which means no exceptions and no support for runtime type information
(rtti). Moreover, the library is not in the std namespace.
Note: A module compiled with Extended EC++ enabled is fully link-compatible with a
module compiled without Extended EC++ enabled.

Enabling support for C++

In the compiler, the default language is C.
To compile files written in Embedded C++, use the --ec++ compiler option. See
--ec++, page 278.
To take advantage of Extended Embedded C++ features in your source code, use the
--eec++ compiler option. See --eec++, page 279.

For EC++, and EEC++, you must also use the IAR DLIB runtime library.
To enable EC++ or EEC++ in the IDE, choose Project>Options>C/C++
Compiler>Language 1 and select the appropriate standard.

EC++ feature descriptions

When you write C++ source code for the IAR C/C++ Compiler for MSP430, you must
be aware of some benefits and some possible quirks when mixing C++ features—such
as classes, and class members—with IAR language extensions, such as IAR-specific
attributes.

USING IAR ATTRIBUTES WITH CLASSES

Static data members of C++ classes are treated the same way global variables are, and
can have any applicable IAR type, memory, and object attribute.
Member functions are in general treated the same way free functions are, and can have
any applicable IAR type, memory, and object attributes. Virtual member functions can
only have attributes that are compatible with default function pointers, and constructors
and destructors cannot have any such attributes.
The location operator @ and the #pragma location directive can be used on static data
members and with all member functions.

207

AFE1_AFE2-1:1
EC++ feature descriptions

Example of using attributes with classes

class MyClass
{
public:
// Locate a static variable in __data16 memory at address 60
static __data16 __no_init int mI @ 60;

// A static task function

static __task void F();

// A task function
__task void G();

// A virtual task function

virtual __task void H();

// Locate a virtual function into SPECIAL

virtual void M() const volatile @ "SPECIAL";
};

The this pointer

The this pointer used for referring to a class object or calling a member function of a
class object will by default have the data memory attribute for the default data pointer
type. This means that such a class object can only be defined to reside in memory from
which pointers can be implicitly converted to a default data pointer. This restriction
might also apply to objects residing on a stack, for example temporary objects and auto
objects.

Class memory
To compensate for this limitation, a class can be associated with a class memory type.
The class memory type changes:
● the this pointer type in all member functions, constructors, and destructors into a
pointer to class memory
● the default memory for static storage duration variables—that is, not auto
variables—of the class type, into the specified class memory
● the pointer type used for pointing to objects of the class type, into a pointer to class
memory.

IAR C/C++ Compiler User Guide

208 for MSP430

AFE1_AFE2-1:1
 Using C++

Example
class __data20 C
{
public:
void MyF(); // Has a this pointer of type C __data20 *
void MyF() const; // Has a this pointer of type
// C __data20 const *
C(); // Has a this pointer pointing into data20
// memory
C(C const &); // Takes a parameter of type C __data20
// const & (also true of generated copy
// constructor)
int mI;
};

C Ca; // Resides in data20 memory instead of the

// default memory
C __data16 Cb; // Resides in data16 memory, the 'this'
// pointer still points into data20 memory
void MyH()
{
C cd; // Resides on the stack
}

C *Cp1; // Creates a pointer to data20 memory

C __data16 *Cp2; // Creates a pointer to data16 memory

Whenever a class type associated with a class memory type, like C, must be declared,
the class memory type must be mentioned as well:
class __data20 C;

Also note that class types associated with different class memories are not compatible
types.
A built-in operator returns the class memory type associated with a class,
__memory_of(class). For instance, __memory_of(C) returns __data20.

When inheriting, the rule is that it must be possible to convert implicitly a pointer to a
subclass into a pointer to its base class. This means that a subclass can have a more
restrictive class memory than its base class, but not a less restrictive class memory.

209

AFE1_AFE2-1:1
EC++ feature descriptions

class __data20 D : public C

{ // OK, same class memory
public:
void MyG();
int mJ;
};

class __data16 E : public C

{ // OK, data16 memory is inside data20
public:
void MyG() // Has a this pointer pointing into data16 memory
{
MyF(); // Gets a this pointer into data20 memory
}
int mJ;
};

class F : public C
{ // OK, will be associated with same class memory as C
public:
void MyG();
int mJ;
};

Note that the following is not allowed because data20 is not inside data16memory:
class __data20 G:public C
{
};

A new expression on the class will allocate memory in the heap associated with the class
memory. A delete expression will naturally deallocate the memory back to the same
heap. To override the default new and delete operator for a class, declare
void *operator new(size_t);
void operator delete(void *);

as member functions, just like in ordinary C++.

For more information about memory types, see Memory types (MSP430X only), page
60.

FUNCTION TYPES
A function type with extern "C" linkage is compatible with a function that has C++
linkage.

IAR C/C++ Compiler User Guide

210 for MSP430

AFE1_AFE2-1:1
 Using C++

Example
extern "C"
{
typedef void (*FpC)(void); // A C function typedef
}

typedef void (*FpCpp)(void); // A C++ function typedef

FpC F1;
FpCpp F2;
void MyF(FpC);

void MyG()
{
MyF(F1); // Always works
MyF(F2); // FpCpp is compatible with FpC
}

NEW AND DELETE OPERATORS

There are operators for new and delete for each memory that can have a heap, that is,
data16 and data20 memory.
#include <stddef.h>

// Assumes that there is a heap in

// both __data16 and __data20 memory
void __data20 *operator new __data20(__data20_size_t);
void __data16 *operator new __data16(__data16_size_t);
void operator delete(void __data20 *);
void operator delete(void __data16 *);

// And correspondingly for array new and delete operators

void __data20 *operator new[] __data20(__data20_size_t);
void __data16 *operator new[] __data16(__data16_size_t);
void operator delete[](void __data20 *);
void operator delete[](void __data16 *);

Use this syntax if you want to override both global and class-specific operator new
and operator delete for any data memory.
Note that there is a special syntax to name the operator new functions for each
memory, while the naming for the operator delete functions relies on normal
overloading.

211

AFE1_AFE2-1:1
EC++ feature descriptions

New and delete expressions

A new expression calls the operator new function for the memory of the type given. If
a class, struct, or union type with a class memory is used, the class memory will
determine the operator new function called. For example,
void MyF()
{
// Calls operator new __data16(__data16_size_t)
int __data16 *p = new __data16 int;

// Calls operator new __data16(__data16_size_t)

int __data16 *q = new int __data16;

// Calls operator new[] __data16(__data16_size_t)

int __data16 *r = new __data16 int[10];

// Calls operator new __data20(__data20_size_t)

class __data20 S
{
};
S *s = new S;

// Calls operator delete(void __data16 *)

delete p;

// Calls operator delete(void __data20 *)

delete s;

int __data20 *t = new __data16 int;

delete t; // Error: Causes a corrupt heap
}

Note that the pointer used in a delete expression must have the correct type, that is, the
same type as that returned by the new expression. If you use a pointer to the wrong
memory, the result might be a corrupt heap.

USING STATIC CLASS OBJECTS IN INTERRUPTS

If interrupt functions use static class objects that need to be constructed (using
constructors) or destroyed (using destructors), your application will not work properly
if the interrupt occurs before the objects are constructed, or, during or after the objects
are destroyed.
To avoid this, make sure that these interrupts are not enabled until the static objects have
been constructed, and are disabled when returning from main or calling exit. For
information about system startup, see System startup and termination, page 135.

IAR C/C++ Compiler User Guide

212 for MSP430

AFE1_AFE2-1:1
 Using C++

Function local static class objects are constructed the first time execution passes through
their declaration, and are destroyed when returning from main or when calling exit.

USING NEW HANDLERS

To handle memory exhaustion, you can use the set_new_handler function.

New handlers in Embedded C++

If you do not call set_new_handler, or call it with a NULL new handler, and
operator new fails to allocate enough memory, it will call abort. The nothrow
variant of the new operator will instead return NULL.
If you call set_new_handler with a non-NULL new handler, the provided new
handler will be called by operator new if operator new fails to allocate memory. The
new handler must then make more memory available and return, or abort execution in
some manner. The nothrow variant of operator new will never return NULL in the
presence of a new handler.

TEMPLATES
Extended EC++ supports templates according to the C++ standard, but not the export
keyword. The implementation uses a two-phase lookup which means that the keyword
typename must be inserted wherever needed. Furthermore, at each use of a template,
the definitions of all possible templates must be visible. This means that the definitions
of all templates must be in include files or in the actual source file.

DEBUG SUPPORT IN C-SPY

C-SPY® has built-in display support for the STL containers. The logical structure of
containers is presented in the watch views in a comprehensive way that is easy to
understand and follow.
Note: To be able to watch STL containers with many elements in a comprehensive way,
the STL container expansion option—available by choosing
Tools>Options>Debugger—is set to display only a small number of items at first.
For more information, see the C-SPY® Debugging Guide for MSP430.

213

AFE1_AFE2-1:1
EEC++ feature description

EEC++ feature description

This section describes features that distinguish Extended EC++ from EC++.

TEMPLATES
The compiler supports templates with the syntax and semantics as defined by Standard
C++. However, note that the STL (standard template library) delivered with the product
is tailored for Extended EC++, see Extended Embedded C++, page 206.

Templates and data memory attributes

For data memory attributes to work as expected in templates, two elements of the
standard C++ template handling were changed—class template partial specialization
matching and function template parameter deduction.
In Extended Embedded C++, the class template partial specialization matching
algorithm works like this:
When a pointer or reference type is matched against a pointer or reference to a template
parameter type, the template parameter type will be the type pointed to, stripped of any
data memory attributes, if the resulting pointer or reference type is the same.

Example
// We assume that __data20 is the memory type of the default
// pointer.
template<typename> class Z {};
template<typename T> class Z<T *> {};

Z<int __data16 *> Zn; // T = int __data16

Z<int __data20 *> Zf; // T = int

In Extended Embedded C++, the function template parameter deduction algorithm

works like this:
When function template matching is performed and an argument is used for the
deduction; if that argument is a pointer to a memory that can be implicitly converted to
a default pointer, do the parameter deduction as if it was a default pointer.
When an argument is matched against a reference, do the deduction as if the argument
and the parameter were both pointers.

IAR C/C++ Compiler User Guide

214 for MSP430

AFE1_AFE2-1:1
 Using C++

Example
// We assume that __data20 is the memory type of the default
// pointer.
template<typename T> void fun(T *);

void MyF()
{
fun((int __data16 *) 0); // T = int. The result is different
// than the analogous situation with
// class template specializations.
fun((int *) 0); // T = int
fun((int __data20 *) 0); // T = int
}

For templates that are matched using this modified algorithm, it is impossible to get
automatic generation of special code for pointers to “small” memory types. For “large”
and “other” memory types (memory that cannot be pointed to by a default pointer) it is
possible. To make it possible to write templates that are fully memory-aware—in the
rare cases where this is useful—use the #pragma basic_template_matching
directive in front of the template function declaration. That template function will then
match without the modifications described above.

Example
// We assume that __data20 is the memory type of the default
// pointer.
#pragma basic_template_matching
template<typename T> void fun(T *);

void MyF()
{
fun((int __data16 *) 0); // T = int __data16
}

Non-type template parameters

It is allowed to have a reference to a memory type as a template parameter, even if
pointers to that memory type are not allowed.

215

AFE1_AFE2-1:1
EEC++ feature description

Example
#include <intrinsics.h>

__no_init int __regvar x @ __R4;

template<__regvar int &y>

void foo()
{
y = 17;
}

void bar()
{
foo<x>();
}

Note: This example must be compiled with the --regvar_r4 compiler option.

Example
#include <vector>

vector<int> D; // D placed in default memory,

// using the default heap,
// uses default pointers
vector<int __data16> __data16 X; // X placed in data16 memory,
// heap allocation from
// data16, uses pointers to
// data16 memory
vector<int __data20> __data16 Y; // Y placed in data16 memory,
// heap allocation from
// data20, uses pointers to
// data20 memory

The standard template library

The containers in the STL, like vector and map, are memory attribute aware. This
means that a container can be declared to reside in a specific memory type which has the
following consequences:
● The container itself will reside in the chosen memory
● Allocations of elements in the container will use a heap for the chosen memory
● All references inside it use pointers to the chosen memory.

IAR C/C++ Compiler User Guide

216 for MSP430

AFE1_AFE2-1:1
 Using C++

Example
#include <vector>

vector<int> D; // D placed in default memory,

// using the default heap,
// uses default pointers
vector<int __data16> __data16 X; // X placed in data16 memory,
// heap allocation from
// data16, uses pointers to
// data16 memory
vector<int __data20> __data16 Y; // Y placed in data16 memory,
// heap allocation from
// data20, uses pointers to
// data20 memory

Note that this is illegal:

vector<int __data16> __data20 Z;

Note also that map<key, T>, multimap<key, T>, hash_map<key, T>, and
hash_multimap<key, T> all use the memory of T. This means that the value_type
of these collections will be pair<key, const T> mem where mem is the memory type
of T. Supplying a key with a memory type is not useful.

Example
Note that two containers that only differ by the data memory attribute they use cannot
be assigned to each other. Instead, the templated assign member method must be used.
#include <vector>

vector<int __data16> X;
vector<int __data20> Y;

void MyF()
{
// The templated assign member method will work
X.assign(Y.begin(), Y.end());
Y.assign(X.begin(), X.end());
}

VARIANTS OF CAST OPERATORS

In Extended EC++ these additional variants of C++ cast operators can be used:
const_cast<to>(from)
static_cast<to>(from)
reinterpret_cast<to>(from)

217

AFE1_AFE2-1:1
C++ language extensions

MUTABLE
The mutable attribute is supported in Extended EC++. A mutable symbol can be
changed even though the whole class object is const.

NAMESPACE
The namespace feature is only supported in Extended EC++. This means that you can
use namespaces to partition your code. Note, however, that the library itself is not placed
in the std namespace.

THE STD NAMESPACE

The std namespace is not used in either standard EC++ or in Extended EC++. If you
have code that refers to symbols in the std namespace, simply define std as nothing;
for example:
#define std

You must make sure that identifiers in your application do not interfere with identifiers
in the runtime library.

C++ language extensions

When you use the compiler in any C++ mode and enable IAR language extensions, the
following C++ language extensions are available in the compiler:
● In a friend declaration of a class, the class keyword can be omitted, for example:
class B;
class A
{
friend B; //Possible when using IAR language
//extensions
friend class B; //According to the standard
};
● Constants of a scalar type can be defined within classes, for example:
class A
{
const int mSize = 10; //Possible when using IAR language
//extensions
int mArr[mSize];
};
According to the standard, initialized static data members should be used instead.

IAR C/C++ Compiler User Guide

218 for MSP430

AFE1_AFE2-1:1
 Using C++

● In the declaration of a class member, a qualified name can be used, for example:
struct A
{
int A::F(); // Possible when using IAR language extensions
int G(); // According to the standard
};
● It is permitted to use an implicit type conversion between a pointer to a function
with C linkage (extern "C") and a pointer to a function with C++ linkage
(extern "C++"), for example:
extern "C" void F(); // Function with C linkage
void (*PF)() // PF points to a function with C++ linkage
= &F; // Implicit conversion of function pointer.
According to the standard, the pointer must be explicitly converted.
● If the second or third operands in a construction that contains the ? operator are
string literals or wide string literals (which in C++ are constants), the operands can
be implicitly converted to char * or wchar_t *, for example:
bool X;

char *P1 = X ? "abc" : "def"; //Possible when using IAR

//language extensions
char const *P2 = X ? "abc" : "def";//According to the standard
● Default arguments can be specified for function parameters not only in the top-level
function declaration, which is according to the standard, but also in typedef
declarations, in pointer-to-function function declarations, and in pointer-to-member
function declarations.
● In a function that contains a non-static local variable and a class that contains a
non-evaluated expression (for example a sizeof expression), the expression can
reference the non-static local variable. However, a warning is issued.
● An anonymous union can be introduced into a containing class by a typedef name.
It is not necessary to first declare the union. For example:
typedef union
{
int i,j;
} U; // U identifies a reusable anonymous union.

class A
{
public:
U; // OK -- references to A::i and A::j are allowed.
};
In addition, this extension also permits anonymous classes and anonymous structs,
as long as they have no C++ features (for example, no static data members or member

219

AFE1_AFE2-1:1
C++ language extensions

functions, and no non-public members) and have no nested types other than other
anonymous classes, structs, or unions. For example:
struct A
{
struct
{
int i,j;
}; // OK -- references to A::i and A::j are allowed.
};
● The friend class syntax allows nonclass types as well as class types expressed
through a typedef without an elaborated type name. For example:
typedef struct S ST;

class C
{
public:
friend S; // Okay (requires S to be in scope)
friend ST; // Okay (same as "friend S;")
// friend S const; // Error, cv-qualifiers cannot
// appear directly
};
● It is allowed to specify an array with no size or size 0 as the last member of a struct.
For example:
typedef struct
{
int i;
char ir[0]; // Zero-length array
};

typedef struct
{
int i;
char ir[]; // Zero-length array
};

Note: If you use any of these constructions without first enabling language extensions,
errors are issued.

IAR C/C++ Compiler User Guide

220 for MSP430

AFE1_AFE2-1:1
 Application-related
considerations
● Stack considerations

● Heap considerations

● Interaction between the tools and your application

● Checksum calculation for verifying image integrity

Stack considerations
To make your application use stack memory efficiently, there are some considerations
to be made.

STACK SIZE CONSIDERATIONS

The required stack size depends heavily on the application’s behavior. If the given stack
size is too large, RAM will be wasted. If the given stack size is too small, one of two
things can happen, depending on where in memory you located your stack:
● Variable storage will be overwritten, leading to undefined behavior
● The stack will fall outside of the memory area, leading to an abnormal termination
of your application.
Both alternatives are likely to result in application failure. Because the second
alternative is easier to detect, you should consider placing your stack so that it grows
toward the end of the RAM memory.
For more information about the stack size, see Setting up stack memory, page 105, and
Saving stack space and RAM memory, page 246.

Heap considerations
The heap contains dynamic data allocated by use of the C function malloc (or a
corresponding function) or the C++ operator new.
If your application uses dynamic memory allocation, you should be familiar with:
● Linker segments used for the heap

221

AFE1_AFE2-1:1
Heap considerations

● Allocating the heap size, see Setting up heap memory, page 106.

HEAP SEGMENTS IN DLIB

When using the DLIB runtime environment, you can allocate data in the default memory
using the standard memory allocation functions malloc, free etc. However, in the
Medium or Large data model, using an MSP430X device, you can also allocate data in
a non-default memory by using the appropriate memory attribute as a prefix to the
standard functions malloc, free, calloc, and realloc, for example:
__data16_malloc

If you use any of the standard functions without a prefix, the function will be mapped to
the default memory type data16.
Each heap will reside in a segment with the name _HEAP prefixed by a memory attribute,
for example DATA16_HEAP.
For information about available heaps, see Dynamic memory on the heap, page 69.

HEAP SEGMENTS IN CLIB

The memory allocated to the heap is placed in the segment HEAP, which is only included
in the application if dynamic memory allocation is actually used.
In the CLIB runtime environment one heap is available. It is placed in default memory;
data16 in the Small and Medium data model (the DATA16_HEAP segment), and data20
in the Large data model (the DATA20_HEAP segment).

HEAP SIZE AND STANDARD I/O

If you excluded FILE descriptors from the DLIB runtime environment, as in the Normal
configuration, there are no input and output buffers at all. Otherwise, as in the Full
configuration, be aware that the size of the input and output buffers is set to 512 bytes
in the stdio library header file. If the heap is too small, I/O will not be buffered, which
is considerably slower than when I/O is buffered. If you execute the application using
the simulator driver of the IAR C-SPY® Debugger, you are not likely to notice the speed
penalty, but it is quite noticeable when the application runs on an MSP430
microcontroller. If you use the standard I/O library, you should set the heap size to a
value which accommodates the needs of the standard I/O buffer.

IAR C/C++ Compiler User Guide

222 for MSP430

AFE1_AFE2-1:1
 Application-related considerations

Interaction between the tools and your application

The linking process and the application can interact symbolically in four ways:
● Creating a symbol by using the linker command line option -D. The linker will
create a public absolute constant symbol that the application can use as a label, as a
size, as setup for a debugger, etc.
● Using the compiler operators __segment_begin, __segment_end, or
__segment_size, or the assembler operators SFB, SFE, or SIZEOF on a named
segment. These operators provide access to the start address, end address, and size
of a contiguous sequence of segments with the same name
● The command line option -s informs the linker about the start label of the
application. It is used by the linker as a root symbol and to inform the debugger
where to start execution.
The following lines illustrate how to use -D to create a symbol. If you need to use this
mechanism, add these options to your command line like this:
-Dmy_symbol=A
-DMY_HEAP_SIZE=400

In this example, the function GetElementArray() allocates an array. The size of the
array is controlled by the linker. Add -DNrOfElements=100 to the linker configuration
file:
#include <stdlib.h>

/* Use symbol defined by an XLINK option to dynamically allocate

an array of elements with specified size. The value takes the
form of a label.
*/
extern int NrOfElements;

typedef char Elements;

Elements *GetElementArray()
{
return malloc(sizeof(Elements) * (size_t) &NrOfElements);
}

Here, MyHeap() returns a pointer to a cleared memory area. The size and placement of
the memory area is controlled by the linker. Add the following lines to the linker
configuration file, and adapt the range to your device:
-DHeapSize=40
-Z(DATA)MYHEAP+HeapSize=4000-FFFF

223

AFE1_AFE2-1:1
Checksum calculation for verifying image integrity

/* Use a symbol defined by an XLINK option, a symbol that in the

* configuration file was made available to the application.
*/
extern char HeapSize;

/* Declare the section that contains the heap. */

#pragma segment = "MYHEAP"

char *MyHeap()
{
/* First get start of statically allocated section, */
char *p = __segment_begin("MYHEAP");

/* ...then we zero it, using the imported size. */

for (int i = 0; i < (int) &HeapSize; ++i)
{
p[i] = 0;
}
return p;
}

Checksum calculation for verifying image integrity

This section contains information about checksum calculation:
● Briefly about checksum calculation, page 224
● Calculating and verifying a checksum, page 226
● Troubleshooting checksum calculation, page 231

BRIEFLY ABOUT CHECKSUM CALCULATION

You can use a checksum to verify that the image is the same at runtime as when the
image’s original checksum was generated. In other words, to verify that the image has
not been corrupted.
This works as follows:
● You need an initial checksum.
You can either use the linker to generate an initial checksum or you might have a
third-party checksum available.
● You must generate a second checksum during runtime.
You can either add specific code to your application source code for calculating a
checksum during runtime or you can use some dedicated hardware on your device
for calculating a checksum during runtime.

IAR C/C++ Compiler User Guide

224 for MSP430

AFE1_AFE2-1:1
 Application-related considerations

● You must add specific code to your application source code for comparing the two
checksums and take an appropriate action if they differ.
If the two checksums have been calculated in the same way, and if there are no errors
in the image, the checksums should be identical. If not, you should first suspect that
the two checksums were not generated in the same way.
No matter which solutions you use for generating the two checksum, you must make
sure that both checksums are calculated in the exact same way. If you use the linker for
the initial checksum and use a software-based calculation during runtime, you have full
control of the generation for both checksums. However, if you are using a third-party
checksum for the initial checksum or some hardware support for the checksum
calculation during runtime, there might be additional requirements that you must
consider.
For the two checksums, there are some choices that you must always consider and there
are some choices to make only if there are additional requirements. Still, all of the details
must be the same for both checksums.
Always consider:
● Checksum range
The memory range (or ranges) that you want to verify by means of checksums.
Typically, you might want to calculate a checksum for all ROM memory. However,
you might want to calculate a checksum only for specific ranges. Remember that:
● It is OK to have several ranges for one checksum.
● Typically, the checksum must be calculated from the lowest to the highest
address for every memory range.
● Each memory range must be verified in the same order as defined, for example,
0x100–0x1FF,0x400–0x4FF is not the same as 0x400–0x4FF,0x100–0x1FF.
● If several checksums are used, you should place them in sections with unique
names and use unique symbol names.
● A checksum should never be calculated on a memory range that contains a
checksum or a software breakpoint.
● Algorithm and size of checksum
You should consider which algorithm is most suitable in your case. There are two
basic choices, Sum—a simple arithmetic algorithm—or CRC—which is the most
commonly used algorithm. For CRC there are different sizes to choose for the
checksum, 2 or 4 bytes where the predefined polynomials are wide enough to suit the
size, for more error detecting power. The predefined polynomials work well for most,
but possibly not for all data sets. If not, you can specify your own polynomial. If you
just want a decent error detecting mechanism, use the predefined CRC algorithm for
your checksum size, typically CRC16 or CRC32.

225

AFE1_AFE2-1:1
Checksum calculation for verifying image integrity

Note: For an n-bit polynomial, the n:th bit is always considered to be set. For a 16-bit
polynomial—for example, CRC16—this means that 0x11021 is the same as
0x1021.
For more information about selecting an appropriate polynomial for data sets with
non-uniform distribution, see for example section 3.5.3 in Tannenbaum, A.S.,
Computer Networks, Prentice Hall 1981, ISBN: 0131646990.
● Fill
Every byte in the checksum range must have a well-defined value before the
checksum can be calculated. Typically, bytes with unknown values are pad bytes that
have been added for alignment. This means that you must specify which fill pattern
to be used during calculation, typically 0xFF or 0x00.
● Initial value
The checksum must always have an explicit initial value.
In addition to these mandatory details, there might be other details to consider.
Typically, this might happen when you have a third-party checksum, you want the
checksum be compliant with the Rocksoft™ checksum model, or when you use
hardware support for generating a checksum during runtime. The linker also provides
support for controlling alignment, complement, bit order, and checksum unit size.

CALCULATING AND VERIFYING A CHECKSUM

In this example procedure, a checksum is calculated for ROM memory from 0x8002 up
to 0x8FFF and the 2-byte calculated checksum is placed at 0x8000.
1 The CHECKSUM segment will only be included in your application if the segment
appears to be needed. If the checksum is not needed by the application itself, use the
linker option -g__checksum to force the segment to be included.
2 When configuring the linker to calculate a checksum, there are some basic choices to
make:
● Checksum algorithm
Choose which checksum algorithm you want to use. In this example, the CRC16
algorithm is used.
● Memory range
Using the IDE, the checksum will by default be calculated for all placement
directives (specified in the linker configuration file) for ROM-based memory. From
the command line, you can specify any ranges.
● Fill pattern
Specify a fill pattern—typically 0xFF or 0x00—for bytes with unknown values. The
fill pattern will be used in all checksum ranges.

IAR C/C++ Compiler User Guide

226 for MSP430

AFE1_AFE2-1:1
 Application-related considerations

For more information, see Briefly about checksum calculation, page 224.
To run the linker from the IDE, choose Project>Options>Linker>Checksum and
make your settings, for example:

In the simplest case, you can ignore (or leave with default settings) these options:
Complement, Bit order, and Checksum unit size.
To make the linker create a checksum from the command line, use the -J linker option,
for example like this:
-J2,crc16,,__checksum,CHECKSUM,1=0x8002–0x8FFF

The checksum will be created when you build your project and will be placed in the
automatically generated segment CHECKSUM. If you are using your own linker
configuration file or if you explicitly want to control the placement of the CHECKSUM
segment, you must update your linker configuration file with placement information
accordingly. In that case, make sure to place the segment so that it is not part of the
application’s checksum calculation.
3 You can specify several ranges instead of only one range.
If you are using the IDE, perform these steps:
● Choose Project>Options>Linker>Checksum and make sure to deselect Fill
unused code memory.
● Choose Project>Options>Linker>Extra Options and specify the ranges, for
example like this:
-h(CODE)0-3FF,8002-8FFF
-J2,crc16,,,1=0-3FF,8002-8FFF

227

AFE1_AFE2-1:1
Checksum calculation for verifying image integrity

If you are using the command line, use the -J option and specify the ranges. for example
like this:
-h(CODE)0-3FF,8002-8FFF
-J2,crc16,,,1=0-3FF,8002-8FFF

IAR C/C++ Compiler User Guide

228 for MSP430

AFE1_AFE2-1:1
 Application-related considerations

4 Add a function for checksum calculation to your source code. Make sure that the
function uses the same algorithm and settings as for the checksum calculated by the
linker. For example, a slow variant of the crc16 algorithm but with small memory
footprint (in contrast to the fast variant that uses more memory):
unsigned short SmallCrc16(uint16_t
sum,
unsigned char *p,
unsigned int len)
{
while (len--)
{
int i;
unsigned char byte = *(p++);

for (i = 0; i < 8; ++i)

{
unsigned long oSum = sum;
sum <<= 1;
if (byte & 0x80)
sum |= 1;
if (oSum & 0x8000)
sum ^= 0x1021;
byte <<= 1;
}
}
return sum;
}

You can find the source code for this checksum algorithm in the 430\src\linker
directory of your product installation.
5 Make sure that your application also contains a call to the function that calculates the
checksum, compares the two checksums, and takes appropriate action if the checksum
values do not match.

229

AFE1_AFE2-1:1
Checksum calculation for verifying image integrity

This code gives an example of how the checksum can be calculated for your application
and to be compared with the linker generated checksum:
/* The calculated checksum */

/* Linker generated symbols */

extern unsigned short const __checksum;
extern int __checksum_begin;
extern int __checksum_end;

void TestChecksum()
{
unsigned short calc = 0;
unsigned char zeros[2] = {0, 0};

/* Run the checksum algorithm */

calc = SmallCrc16(0,
(unsigned char *) &__checksum_begin,
((unsigned char *) &__checksum_end -
((unsigned char *) &__checksum_begin)+1));

/* Fill the end of the byte sequence with zeros. */

calc = SmallCrc16(calc, zeros, 2);

/* Test the checksum */

if (calc != __checksum)
{
printf("Incorrect checksum!\n");
abort(); /* Failure */
}

/* Checksum is correct */
}

Note: Make sure to define the symbols __checksum_begin and __checksum_end in

your linker configuration file.
6 Build your application project and download it.
During the build, the linker creates a checksum and places it in the specified symbol
__checksum in the segment CHECKSUM.

7 Choose Download and Debug to start the C-SPY debugger.

During execution, the checksum calculated by the linker and the checksum calculated
by your application should be identical.

IAR C/C++ Compiler User Guide

230 for MSP430

AFE1_AFE2-1:1
 Application-related considerations

TROUBLESHOOTING CHECKSUM CALCULATION

If the two checksums do not match, there are several possible causes. These are some
troubleshooting hints:
● If possible, start with a small example when trying to get the checksums to match.
● Verify that the exact same memory range or ranges are used in both checksum
calculations.
To help you do this, The linker produces useful information in the map file about the
exact addresses that were used and the order in which they were accessed.
● Make sure that all checksum symbols are excluded from all checksum calculations.
In the map file, notice the checksum symbol and its size, and for information about
its placement, check the module map or the entry list. Compare that placement with
the checksum range.
● Verify that the checksum calculations use the same polynomial.
● Verify that the bits in the bytes are processed in the same order in both checksum
calculations, from the least to the most significant bit or the other way around. You
control this with the Bit order option (or from the command line, the -m parameter
of the --checksum option).
● If you are using the small variant of CRC, check whether you need to feed
additional bytes into the algorithm.
The number of zeros to add at the end of the byte sequence must match the size of
the checksum, in other words, one zero for a 1-byte checksum, two zeros for a 2-byte
checksum, and four zeros for a 4-byte checksum.
● Any breakpoints in flash memory change the content of the flash. This means that
the checksum which is calculated by your application will no longer match the
initial checksum calculated by the linker. To make the two checksums match again,
you must disable all your breakpoints in flash and any breakpoints set in flash by
C-SPY internally. The stack plugin and the debugger option Run to both require
C-SPY to set breakpoints. Read more about possible breakpoint consumers in the
C-SPY® Debugging Guide for MSP430.

231

AFE1_AFE2-1:1
Checksum calculation for verifying image integrity

IAR C/C++ Compiler User Guide

232 for MSP430

AFE1_AFE2-1:1
 Efficient coding for
embedded applications
● Selecting data types

● Controlling data and function placement in memory

● Controlling compiler optimizations

● Facilitating good code generation

Selecting data types

For efficient treatment of data, you should consider the data types used and the most
efficient placement of the variables.

USING EFFICIENT DATA TYPES

The data types you use should be considered carefully, because this can have a large
impact on code size and code speed.
● Use small data types.
● Try to avoid 64-bit data types, such as double and long long.
● Bitfields with sizes other than 1 bit should be avoided because they will result in
inefficient code compared to bit operations.
● Using floating-point types is very inefficient, both in terms of code size and
execution speed. If possible, consider using integer operations instead.
For information about representation of supported data types, pointers, and structures
types, see the chapter Data representation.

FLOATING-POINT TYPES
Using floating-point types on a microprocessor without a math coprocessor is
inefficient, both in terms of code size and execution speed. Therefore, you should
consider replacing code that uses floating-point operations with code that uses integers,
because these are more efficient.
The compiler supports two floating-point formats—32 and 64 bits. The 32-bit
floating-point type float is more efficient in terms of code size and execution speed.
The 64-bit format double supports higher precision and larger numbers.

233

AFE1_AFE2-1:1
Selecting data types

In the compiler, the floating-point type float always uses the 32-bit format. The format
used by the double floating-point type depends on the setting of the --double
compiler option.
Unless the application requires the extra precision that 64-bit floating-point numbers
give, we recommend using 32-bit floating-point numbers instead. Also, consider
replacing code using floating-point operations with code using integers because these
are more efficient.
By default, a floating-point constant in the source code is treated as being of the type
double. This can cause innocent-looking expressions to be evaluated in double
precision. In the example below a is converted from a float to a double, the double
constant 1.0 is added and the result is converted back to a float:
double Test(float a)
{
return a + 1.0;
}

To treat a floating-point constant as a float rather than as a double, add the suffix f
to it, for example:
double Test(float a)
{
return a + 1.0f;
}

For more information about floating-point types, see Basic data types—floating-point
types, page 307.

ALIGNMENT OF ELEMENTS IN A STRUCTURE

The MSP430 microcontroller requires that when accessing data in memory, the data
must be aligned. Each element in a structure must be aligned according to its specified
type requirements. This means that the compiler might need to insert pad bytes to keep
the alignment correct.
There are situations when this can be a problem:
● There are external demands, for example, network communication protocols are
usually specified in terms of data types with no padding in between
● You need to save data memory.
For information about alignment requirements, see Alignment, page 303.
Use the #pragma pack directive for a tighter layout of the structure. The drawback is
that each access to an unaligned element in the structure will use more code.

IAR C/C++ Compiler User Guide

234 for MSP430

AFE1_AFE2-1:1
 Efficient coding for embedded applications

Alternatively, write your own customized functions for packing and unpacking
structures. This is a more portable way, which will not produce any more code apart
from your functions. The drawback is the need for two views on the structure data—
packed and unpacked.
For more information about the #pragma pack directive, see pack, page 347.

ANONYMOUS STRUCTS AND UNIONS

When a structure or union is declared without a name, it becomes anonymous. The effect
is that its members will only be seen in the surrounding scope.
Anonymous structures are part of the C++ language; however, they are not part of the C
standard. In the IAR C/C++ Compiler for MSP430 they can be used in C if language
extensions are enabled.
In the IDE, language extensions are enabled by default.

Use the -e compiler option to enable language extensions. See -e, page 278, for
additional information.

Example
In this example, the members in the anonymous union can be accessed, in function F,
without explicitly specifying the union name:
struct S
{
char mTag;
union
{
long mL;
float mF;
};
} St;

void F(void)
{
St.mL = 5;
}

235

AFE1_AFE2-1:1
Controlling data and function placement in memory

The member names must be unique in the surrounding scope. Having an anonymous
struct or union at file scope, as a global, external, or static variable is also allowed.
This could for instance be used for declaring I/O registers, as in this example:
__no_init volatile
union
{
unsigned char IOPORT;
struct
{
unsigned char way: 1;
unsigned char out: 1;
};
} @ 8;

/* The variables are used here. */

void Test(void)
{
IOPORT = 0;
way = 1;
out = 1;
}

This declares an I/O register byte IOPORT at address 8. The I/O register has 2 bits
declared, way and out. Note that both the inner structure and the outer union are
anonymous.
Anonymous structures and unions are implemented in terms of objects named after the
first field, with a prefix _A_ to place the name in the implementation part of the
namespace. In this example, the anonymous union will be implemented through an
object named _A_IOPORT.

Controlling data and function placement in memory

The compiler provides different mechanisms for controlling placement of functions and
data objects in memory. To use memory efficiently, you should be familiar with these
mechanisms and know which one is best suited for different situations. You can use:
● Data models (MSP430X only)
By selecting a data model, you can control the default memory placement of
variables and constants. For more information, see Data models, page 66.

IAR C/C++ Compiler User Guide

236 for MSP430

AFE1_AFE2-1:1
 Efficient coding for embedded applications

● Memory attributes (MSP430X only)

Using IAR-specific keywords or pragma directives, you can override the default
placement of variables and constants. For more information, see Using data memory
attributes, page 61.
● The @ operator and the #pragma location directive for absolute placement.
Using the @ operator or the #pragma location directive, you can place individual
global and static variables at absolute addresses. For more information, see Data
placement at an absolute location, page 237.
● The @ operator and the #pragma location directive for segment placement.
Using the @ operator or the #pragma location directive, you can place individual
functions, variables, and constants in named segments. The placement of these
segments can then be controlled by linker directives. For more information, see Data
and function placement in segments, page 239.
● Using the --segment option, you can set the default segment for functions,
variables, and constants in a particular module. For more information, see
--segment, page 297.

DATA PLACEMENT AT AN ABSOLUTE LOCATION

The @ operator, alternatively the #pragma location directive, can be used for placing
global and static variables at absolute addresses. The variables must be declared using
one of these combinations of keywords:
● __no_init
● __no_init and const (without initializers)
● const (with initializers)

To place a variable at an absolute address, the argument to the @ operator and the
#pragma location directive should be a literal number, representing the actual
address. The absolute location must fulfill the alignment requirement for the variable
that should be located.
Note: All declarations of variables placed at an absolute address are tentative
definitions. Tentatively defined variables are only kept in the output from the compiler
if they are needed in the module being compiled. Such variables will be defined in all
modules in which they are used, which will work as long as they are defined in the same
way. The recommendation is to place all such declarations in header files that are
included in all modules that use the variables.

237

AFE1_AFE2-1:1
Controlling data and function placement in memory

Examples
In this example, a __no_init declared variable is placed at an absolute address. This
is useful for interfacing between multiple processes, applications, etc:
__no_init volatile char alpha @ 0x200;/* OK */

The next example contains two const declared objects. The first one is not initialized,
and the second one is initialized to a specific value. (The first case is useful for
configuration parameters, because they are accessible from an external interface.) Both
objects are placed in ROM. Note that in the second case, the compiler is not obliged to
actually read from the variable, because the value is known.
#pragma location=0x202
__no_init const int beta; /* OK */

const int gamma @ 0x204 = 3; /* OK */

In the first case, the value is not initialized by the compiler—the value must be set by
other means. The typical use is for configurations where the values are loaded to ROM
separately, or for special function registers that are read-only.
This shows incorrect usage:
int delta @ 0x206; /* Error, neither */
/* "__no_init" nor "const".*/
__no_init int epsilon @ 0x207; /* Error, misaligned. */

C++ considerations
In C++, module scoped const variables are static (module local), whereas in C they are
global. This means that each module that declares a certain const variable will contain
a separate variable with this name. If you link an application with several such modules
all containing (via a header file), for instance, the declaration:
volatile const __no_init int x @ 0x100; /* Bad in C++ */

the linker will report that more than one variable is located at address 0x100.
To avoid this problem and make the process the same in C and C++, you should declare
these variables extern, for example:
/* The extern keyword makes x public. */
extern volatile const __no_init int x @ 0x100;

Note: C++ static member variables can be placed at an absolute address just like any
other static variable.

IAR C/C++ Compiler User Guide

238 for MSP430

AFE1_AFE2-1:1
 Efficient coding for embedded applications

DATA AND FUNCTION PLACEMENT IN SEGMENTS

The following methods can be used for placing data or functions in named segments
other than default:
● The @ operator, alternatively the #pragma location directive, can be used for
placing individual variables or individual functions in named segments. The named
segment can either be a predefined segment, or a user-defined segment.
● The --segment option can be used for placing variables and functions, which are
parts of the whole compilation unit, in named segments.
C++ static member variables can be placed in named segments just like any other static
variable.
If you use your own segments, in addition to the predefined segments, the segments
must also be defined in the linker configuration file using the -Z or the -P segment
control directives.
Note: Take care when explicitly placing a variable or function in a predefined segment
other than the one used by default. This is useful in some situations, but incorrect
placement can result in anything from error messages during compilation and linking to
a malfunctioning application. Carefully consider the circumstances—there might be
strict requirements on the declaration and use of the function or variable.
The location of the segments can be controlled from the linker configuration file.
For more information about segments, see the chapter Segment reference.

Examples of placing variables in named segments

In the following examples, a data object is placed in a user-defined segment. If no
memory attribute is specified, the variable will, like any other variable, be treated as if
it is located in the default memory. Note that you must as always ensure that the segment
is placed in the appropriate memory area when linking.
__no_init int alpha @ "MY_NOINIT"; /* OK */

#pragma location="MY_CONSTANTS"
const int beta = 42; /* OK */

const int gamma @ "MY_CONSTANTS" = 17; /* OK */

int theta @ "MY_ZEROS"; /* OK */
int phi @ "MY_INITED" = 4711; /* OK */

The compiler will warn that segments that contain zero-initialized and initialized data
must be handled manually. To do this, you must use the linker option -Q to separate the
initializers into one separate segment and the symbols to be initialized to a different

239

AFE1_AFE2-1:1
Controlling compiler optimizations

segment. You must then write source code that copies the initializer segment to the
initialized segment, and zero-initialized symbols must be cleared before they are used.
As described elsewhere, for MSP430X you can use memory attributes to select a
memory for the variable. Note that you must as always ensure that the segment is placed
in the appropriate memory area when linking.
__data16 __no_init int alpha @ "MY_DATA16_NOINIT";/* Placed in
data16*/

Examples of placing functions in named segments

void f(void) @ "MY_FUNCTIONS";

void g(void) @ "MY_FUNCTIONS"

{
}

#pragma location="MY_FUNCTIONS"
void h(void);

Controlling compiler optimizations

The compiler performs many transformations on your application to generate the best
possible code. Examples of such transformations are storing values in registers instead
of memory, removing superfluous code, reordering computations in a more efficient
order, and replacing arithmetic operations by cheaper operations.
The linker should also be considered an integral part of the compilation system, because
some optimizations are performed by the linker. For instance, all unused functions and
variables are removed and not included in the final output.

SCOPE FOR PERFORMED OPTIMIZATIONS

You can decide whether optimizations should be performed on your whole application
or on individual files. By default, the same types of optimizations are used for an entire
project, but you should consider using different optimization settings for individual files.
For example, put code that must execute quickly into a separate file and compile it for
minimal execution time, and the rest of the code for minimal code size. This will give a
small program, which is still fast enough where it matters.
You can also exclude individual functions from the performed optimizations. The
#pragma optimize directive allows you to either lower the optimization level, or
specify another type of optimization to be performed. See optimize, page 346, for
information about the pragma directive.

IAR C/C++ Compiler User Guide

240 for MSP430

AFE1_AFE2-1:1
 Efficient coding for embedded applications

MULTI-FILE COMPILATION UNITS

In addition to applying different optimizations to different source files or even functions,
you can also decide what a compilation unit consists of—one or several source code
files.
By default, a compilation unit consists of one source file, but you can also use multi-file
compilation to make several source files in a compilation unit. The advantage is that
interprocedural optimizations such as inlining, cross call, and cross jump have more
source code to work on. Ideally, the whole application should be compiled as one
compilation unit. However, for large applications this is not practical because of
resource restrictions on the host computer. For more information, see --mfc, page 284.
Note: Only one object file is generated, and therefore all symbols will be part of that
object file.
If the whole application is compiled as one compilation unit, it is useful to make the
compiler also discard unused public functions and variables before the interprocedural
optimizations are performed. Doing this limits the scope of the optimizations to
functions and variables that are actually used. For more information, see
--discard_unused_publics, page 276.

241

AFE1_AFE2-1:1
Controlling compiler optimizations

OPTIMIZATION LEVELS
The compiler supports different levels of optimizations. This table lists optimizations
that are typically performed on each level:
Optimization level Description
None (Best debug support) Variables live through their entire scope
Dead code elimination
Redundant label elimination
Redundant branch elimination
Low Same as above but variables only live for as long as they are
needed, not necessarily through their entire scope
Medium Same as above, and:
Live-dead analysis and optimization
Code hoisting
Register content analysis and optimization
Common subexpression elimination
High (Balanced) Same as above, and:
Peephole optimization
Cross jumping
Loop unrolling
Function inlining
Type-based alias analysis
Table 29: Compiler optimization levels

Note: Some of the performed optimizations can be individually enabled or disabled. For
more information, see Fine-tuning enabled transformations, page 243.
A high level of optimization might result in increased compile time, and will also most
likely make debugging more difficult, because it is less clear how the generated code
relates to the source code. For example, at the low, medium, and high optimization
levels, variables do not live through their entire scope, which means processor registers
used for storing variables can be reused immediately after they were last used. Due to
this, the C-SPY Watch window might not be able to display the value of the variable
throughout its scope, or even occasionally display an incorrect value. At any time, if you
experience difficulties when debugging your code, try lowering the optimization level.

SPEED VERSUS SIZE

At the high optimization level, the compiler balances between size and speed
optimizations. However, it is possible to fine-tune the optimizations explicitly for either
size or speed. They only differ in what thresholds that are used—speed will trade size
for speed, whereas size will trade speed for size.

IAR C/C++ Compiler User Guide

242 for MSP430

AFE1_AFE2-1:1
 Efficient coding for embedded applications

If you use the optimization level High speed, the --no_size_constraints compiler
option relaxes the normal restrictions for code size expansion and enables more
aggressive optimizations.
You can choose an optimization goal for each module, or even individual functions,
using command line options and pragma directives (see -O, page 291 and optimize, page
346). For a small embedded application, this makes it possible to achieve acceptable
speed performance while minimizing the code size: Typically, only a few places in the
application need to be fast, such as the most frequently executed inner loops, or the
interrupt handlers.
Rather than compiling the whole application with High (Balanced) optimization, you
can use High (Size) in general, but override this to get High (Speed) optimization only
for those functions where the application needs to be fast.
Note: Because of the unpredictable way in which different optimizations interact, where
one optimization can enable other optimizations, sometimes a function becomes smaller
when compiled with High (Speed) optimization than if High (Size) is used. Also, using
multi-file compilation (see --mfc, page 284) can enable many optimizations to improve
both speed and size performance. It is recommended that you experiment with different
optimization settings so that you can pick the best ones for your project.

FINE-TUNING ENABLED TRANSFORMATIONS

At each optimization level you can disable some of the transformations individually. To
disable a transformation, use either the appropriate option, for instance the command
line option --no_inline, alternatively its equivalent in the IDE Function inlining, or
the #pragma optimize directive. These transformations can be disabled individually:
● Common subexpression elimination
● Loop unrolling
● Function inlining
● Code motion
● Type-based alias analysis

Common subexpression elimination

Redundant re-evaluation of common subexpressions is by default eliminated at
optimization levels Medium and High. This optimization normally reduces both code
size and execution time. However, the resulting code might be difficult to debug.
Note: This option has no effect at optimization levels None and Low.
For more information about the command line option, see --no_cse, page 286.

243

AFE1_AFE2-1:1
Controlling compiler optimizations

Loop unrolling
Loop unrolling means that the code body of a loop, whose number of iterations can be
determined at compile time, is duplicated. Loop unrolling reduces the loop overhead by
amortizing it over several iterations.
This optimization is most efficient for smaller loops, where the loop overhead can be a
substantial part of the total loop body.
Loop unrolling, which can be performed at optimization level High, normally reduces
execution time, but increases code size. The resulting code might also be difficult to
debug.
The compiler heuristically decides which loops to unroll. Only relatively small loops
where the loop overhead reduction is noticeable will be unrolled. Different heuristics are
used when optimizing for speed, size, or when balancing between size and speed.
Note: This option has no effect at optimization levels None, Low, and Medium.
To disable loop unrolling, use the command line option --no_unroll, see --no_unroll,
page 290.

Function inlining
Function inlining means that a function, whose definition is known at compile time, is
integrated into the body of its caller to eliminate the overhead of the call. This
optimization normally reduces execution time, but might increase the code size.
For more information, see Inlining functions, page 81.
To disable function inlining, use the command line option --no_inline, see
--no_inline, page 287.

Code motion
Evaluation of loop-invariant expressions and common subexpressions are moved to
avoid redundant re-evaluation. This optimization, which is performed at optimization
level Medium and above, normally reduces code size and execution time. The resulting
code might however be difficult to debug.
Note: This option has no effect at optimization levels below Medium.
For more information about the command line option, see --no_code_motion, page 286.

Type-based alias analysis

When two or more pointers reference the same memory location, these pointers are said
to be aliases for each other. The existence of aliases makes optimization more difficult

IAR C/C++ Compiler User Guide

244 for MSP430

AFE1_AFE2-1:1
 Efficient coding for embedded applications

because it is not necessarily known at compile time whether a particular value is being
changed.
Type-based alias analysis optimization assumes that all accesses to an object are
performed using its declared type or as a char type. This assumption lets the compiler
detect whether pointers can reference the same memory location or not.
Type-based alias analysis is performed at optimization level High. For application code
conforming to standard C or C++ application code, this optimization can reduce code
size and execution time. However, non-standard C or C++ code might result in the
compiler producing code that leads to unexpected behavior. Therefore, it is possible to
turn this optimization off.
Note: This option has no effect at optimization levels None, Low, and Medium.
For more information about the command line option, see --no_tbaa, page 289.

Example
short F(short *p1, long *p2)
{
*p2 = 0;
*p1 = 1;
return *p2;
}

With type-based alias analysis, it is assumed that a write access to the short pointed to
by p1 cannot affect the long value that p2 points to. Therefore, it is known at compile
time that this function returns 0. However, in non-standard-conforming C or C++ code
these pointers could overlap each other by being part of the same union. If you use
explicit casts, you can also force pointers of different pointer types to point to the same
memory location.

Facilitating good code generation

This section contains hints on how to help the compiler generate good code:
● Writing optimization-friendly source code, page 246
● Saving stack space and RAM memory, page 246
● Function prototypes, page 247
● Integer types and bit negation, page 248
● Protecting simultaneously accessed variables, page 248
● Accessing special function registers, page 249
● Non-initialized variables, page 251

245

AFE1_AFE2-1:1
Facilitating good code generation

● Efficient switch statements, page 252

WRITING OPTIMIZATION-FRIENDLY SOURCE CODE

The following is a list of programming techniques that will, when followed, enable the
compiler to better optimize the application.
● Local variables—auto variables and parameters—are preferred over static or global
variables. The reason is that the optimizer must assume, for example, that called
functions can modify non-local variables. When the life spans for local variables
end, the previously occupied memory can then be reused. Globally declared
variables will occupy data memory during the whole program execution.
● Avoid taking the address of local variables using the & operator. This is inefficient
for two main reasons. First, the variable must be placed in memory, and therefore
cannot be placed in a processor register. This results in larger and slower code.
Second, the optimizer can no longer assume that the local variable is unaffected
over function calls.
● Module-local variables—variables that are declared static—are preferred over
global variables (non-static). Also, avoid taking the address of frequently accessed
static variables.
● The compiler is capable of inlining functions, see Function inlining, page 244. To
maximize the effect of the inlining transformation, it is good practice to place the
definitions of small functions called from more than one module in the header file
rather than in the implementation file. Alternatively, you can use multi-file
compilation. For more information, see Multi-file compilation units, page 241.
● Avoid using inline assembler. Instead, try writing the code in C/C++, use intrinsic
functions, or write a separate module in assembler language. For more information,
see Mixing C and assembler, page 169.

SAVING STACK SPACE AND RAM MEMORY

The following is a list of programming techniques that save memory and stack space:
● If stack space is limited, avoid long call chains and recursive functions.
● Avoid using large non-scalar types, such as structures, as parameters or return type.
To save stack space, you should instead pass them as pointers or, in C++, as
references.
● Use the --reduce_stack_usage option. This will eliminate holes in the stack but
results in somewhat larger code. See --reduce_stack_usage, page 294.

IAR C/C++ Compiler User Guide

246 for MSP430

AFE1_AFE2-1:1
 Efficient coding for embedded applications

FUNCTION PROTOTYPES
It is possible to declare and define functions using one of two different styles:
● Prototyped
● Kernighan & Ritchie C (K&R C)
Both styles are valid C, however it is strongly recommended to use the prototyped style,
and provide a prototype declaration for each public function in a header that is included
both in the compilation unit defining the function and in all compilation units using it.
The compiler will not perform type checking on parameters passed to functions declared
using K&R style. Using prototype declarations will also result in more efficient code in
some cases, as there is no need for type promotion for these functions.
To make the compiler require that all function definitions use the prototyped style, and
that all public functions have been declared before being defined, use the
Project>Options>C/C++ Compiler>Language 1>Require prototypes compiler
option (--require_prototypes).

Prototyped style
In prototyped function declarations, the type for each parameter must be specified.
int Test(char, int); /* Declaration */

int Test(char ch, int i) /* Definition */

{
return i + ch;
}

Kernighan & Ritchie style

In K&R style—pre-Standard C—it is not possible to declare a function prototyped.
Instead, an empty parameter list is used in the function declaration. Also, the definition
looks different.
For example:
int Test(); /* Declaration */

int Test(ch, i) /* Definition */

char ch;
int i;
{
return i + ch;
}

247

AFE1_AFE2-1:1
Facilitating good code generation

INTEGER TYPES AND BIT NEGATION

In some situations, the rules for integer types and their conversion lead to possibly
confusing behavior. Things to look out for are assignments or conditionals (test
expressions) involving types with different size, and logical operations, especially bit
negation. Here, types also includes types of constants.
In some cases there might be warnings—for example, for constant conditional or
pointless comparison—in others just a different result than what is expected. Under
certain circumstances the compiler might warn only at higher optimizations, for
example, if the compiler relies on optimizations to identify some instances of constant
conditionals. In this example, an 8-bit character, a 16-bit integer, and two’s complement
is assumed:
void F1(unsigned char c1)
{
if (c1 == ~0x80)
;
}

Here, the test is always false. On the right hand side, 0x80 is 0x0080, and ~0x0080
becomes 0xFF7F. On the left hand side, c1 is an 8-bit unsigned character in the range
0–255, which can never be equal to 0xFF7F. Furthermore, it cannot be negative, which
means that the integral promoted value can never have the topmost 8 bits set.

PROTECTING SIMULTANEOUSLY ACCESSED VARIABLES

Variables that are accessed asynchronously, for example, by interrupt routines or by
code executing in separate threads, must be properly marked and have adequate
protection. The only exception to this is a variable that is always read-only.
To mark a variable properly, use the volatile keyword. This informs the compiler,
among other things, that the variable can be changed from other threads. The compiler
will then avoid optimizing on the variable—for example, keeping track of the variable
in registers—will not delay writes to it, and be careful accessing the variable only the
number of times given in the source code.
For sequences of accesses to variables that you do not want to be interrupted, use the
__monitor keyword. This must be done for both write and read sequences, otherwise
you might end up reading a partially updated variable. Accessing a small-sized
volatile variable can be an atomic operation, but you should not rely on it unless you
continuously study the compiler output. It is safer to use the __monitor keyword to
ensure that the sequence is an atomic operation. For more information, see __monitor,
page 324.
For more information about the volatile type qualifier and the rules for accessing
volatile objects, see Declaring objects volatile, page 313.

IAR C/C++ Compiler User Guide

248 for MSP430

AFE1_AFE2-1:1
 Efficient coding for embedded applications

Protecting the eeprom write mechanism

A typical example of when it can be necessary to use the __monitor keyword is when
protecting the eeprom write mechanism, which can be used from two threads (for
example, main code and interrupts). Servicing an interrupt during an EEPROM write
sequence can in many cases corrupt the written data.

ACCESSING SPECIAL FUNCTION REGISTERS

Specific header files for all MSP430 devices are included in the IAR product
installation. There are two types of header files, named iodevice.h and
mspdevice.h, respectively. They define the processor-specific special function
registers (SFRs).
You can also use the header files as templates when you create new header files for other
MSP430 devices.

iodevice.h files
The header files named iodevice.h support C and C++. They define SFRs using
structs and unions, and provide access to individual bits through bitfields.

249

AFE1_AFE2-1:1
Facilitating good code generation

The following example is from io430x14x.h:

/* Watchdog Timer Control */
__no_init volatile union
{
unsigned short WDTCTL;
struct
{
unsigned short WDTIS0 : 1;
unsigned short WDTIS1 : 1;
unsigned short WDTSSEL : 1;
unsigned short WDTCNTCL : 1;
unsigned short WDTTMSEL : 1;
unsigned short WDTNMI : 1;
unsigned short WDTNMIES : 1;
unsigned short WDTHOLD : 1;
unsigned short : 8;
} WDTCTL_bit;
} @ 0x0120;

enum {
WDTIS0 = 0x0001,
WDTIS1 = 0x0002,
WDTSSEL = 0x0004,
WDTCNTCL = 0x0008,
WDTTMSEL = 0x0010,
WDTNMI = 0x0020,
WDTNMIES = 0x0040,
WDTHOLD = 0x0080
};

#define WDTPW (0x5A00)

By including the appropriate header file in your source code, you make it possible to
access either the object or any individual bit (or bitfields) from C code as follows:
/* Object access */
WDTCTL = 0x1234;

/* Bitfield accesses */
WDTCTL_bit.WDTSSEL = 1;

If more than one bit must be written to a memory-mapped peripheral unit at the same
time, for instance to stop the watchdog timer, the defined bit constants can be used
instead, for example:
WDTCTL = WDTPW | WDTHOLD; /* Stop watchdog timer */

For information about the @ operator, see Placing located data, page 104.

IAR C/C++ Compiler User Guide

250 for MSP430

AFE1_AFE2-1:1
 Efficient coding for embedded applications

mspdevice.h files
The header files named mspdevice.h support C, C++, and assembler. They define
SFRs using primitive types, and provide access to individual bits through preprocessor
defines.
The following example is from msp430x14x.h:
/* Watchdog Timer Control */
__no_init volatile unsigned short WDTCTL @ 0x0120u;

/* The bit names have been prefixed with "WDT" */

#define WDTIS0 (0x0001u)
#define WDTIS1 (0x0002u)
#define WDTSSEL (0x0004u)
#define WDTCNTCL (0x0008u)
#define WDTTMSEL (0x0010u)
#define WDTNMI (0x0020u)
#define WDTNMIES (0x0040u)
#define WDTHOLD (0x0080u)

#define WDTPW (0x5A00u)

By including the appropriate header file in your source code, you can access the object
as follows:
/* Object access */
WDTCTL = 0x1234;

/* Bitfield accesses */
WDTCTL |= WDTSSEL;

/* Multiple bits access */

WDTCTL = (WDTPW | WDTHOLD); /* Stop watchdog timer */

NON-INITIALIZED VARIABLES
Normally, the runtime environment will initialize all global and static variables when the
application is started.
The compiler supports the declaration of variables that will not be initialized, using the
__no_init type modifier. They can be specified either as a keyword or using the
#pragma object_attribute directive. The compiler places such variables in a
separate segment, according to the specified memory keyword. See the chapter Linking
overview for more information.
For __no_init, the const keyword implies that an object is read-only, rather than that
the object is stored in read-only memory. It is not possible to give a __no_init object
an initial value.

251

AFE1_AFE2-1:1
Facilitating good code generation

Variables declared using the __no_init keyword could, for example, be large input
buffers or mapped to special RAM that keeps its content even when the application is
turned off.
For more information, see __no_init, page 326.
Note: To use this keyword, language extensions must be enabled, see -e, page 278. For
more information, see object_attribute, page 345.

EFFICIENT SWITCH STATEMENTS

The compiler provides a way to generate very efficient code for switch statements when
it is known that the value in the expression is even and within a specific limit. This can
for example be used for writing efficient interrupt service routines that use the Interrupt
Vector Generators Timer A, Timer B, the I2C module, and the ADC12 module. For more
information, see Interrupt Vector Generator interrupt functions, page 74.

IAR C/C++ Compiler User Guide

252 for MSP430

AFE1_AFE2-1:1
Part 2. Reference
information
This part of the IAR C/C++ Compiler User Guide for MSP430 contains these
chapters:

● External interface details

● Compiler options

● Data representation

● Extended keywords

● Pragma directives

● Intrinsic functions

● The preprocessor

● C/C++ standard library functions

● Segment reference

● The stack usage control file

● Implementation-defined behavior for Standard C

● Implementation-defined behavior for C89

253
254
 External interface details
● Invocation syntax

● Include file search procedure

● Compiler output

● Diagnostics

Invocation syntax
You can use the compiler either from the IDE or from the command line. See the IDE
Project Management and Building Guide for information about using the compiler from
the IDE.

COMPILER INVOCATION SYNTAX

The invocation syntax for the compiler is:
icc430 [options] [sourcefile] [options]

For example, when compiling the source file prog.c, use this command to generate an
object file with debug information:
icc430 prog.c --debug

The source file can be a C or C++ file, typically with the filename extension c or cpp,
respectively. If no filename extension is specified, the file to be compiled must have the
extension c.
Generally, the order of options on the command line, both relative to each other and to
the source filename, is not significant. There is, however, one exception: when you use
the -I option, the directories are searched in the same order as they are specified on the
command line.
If you run the compiler from the command line without any arguments, the compiler
version number and all available options including brief descriptions are directed to
stdout and displayed on the screen.

255

AFE1_AFE2-1:1
Include file search procedure

PASSING OPTIONS
There are three different ways of passing options to the compiler:
● Directly from the command line
Specify the options on the command line after the icc430 command, either before
or after the source filename, see Invocation syntax, page 255.
● Via environment variables
The compiler automatically appends the value of the environment variables to every
command line, see Environment variables, page 256.
● Via a text file, using the -f option, see -f, page 280.
For general guidelines for the option syntax, an options summary, and a detailed
description of each option, see the chapter Compiler options.

ENVIRONMENT VARIABLES
These environment variables can be used with the compiler:
Environment variable Description
C_INCLUDE Specifies directories to search for include files, for example:
C_INCLUDE=c:\my_programs\embedded workbench
.n\430\inc;c:\headers
QCC430 Specifies command line options, for example: QCC430=-lA
asm.lst
Table 30: Compiler environment variables

Include file search procedure

This is a detailed description of the compiler’s #include file search procedure:
● The string found between the "" and <> in the #include directive is used verbatim
as a source file name.
● If the name of the #include file is an absolute path specified in angle brackets or
double quotes, that file is opened.
● If the compiler encounters the name of an #include file in angle brackets, such as:
#include <stdio.h>
it searches these directories for the file to include:
1 The directories specified with the -I option, in the order that they were
specified, see -I, page 282.
2 The directories specified using the C_INCLUDE environment variable, if any, see
Environment variables, page 256.

IAR C/C++ Compiler User Guide

256 for MSP430

AFE1_AFE2-1:1
 External interface details

3 The automatically set up library system include directories. See --clib, page 270,
--dlib, page 276, and --dlib_config, page 277.
● If the compiler encounters the name of an #include file in double quotes, for
example:
#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 compiler starts searching the directory of the file
that was last included, iterating upwards for each included file, searching the source file
directory last. For example:
src.c in directory dir\src
#include "src.h"
...
src.h in directory dir\include
#include "config.h"
...

When dir\exe is the current directory, use this command for compilation:
icc430 ..\src\src.c -I..\include -I..\debugconfig

Then the following directories are searched in the order listed below for the file
config.h, which in this example is located in the dir\debugconfig directory:

dir\include Current file is src.h.

dir\src File including current file (src.c).
dir\include As specified with the first -I option.
dir\debugconfig As specified with the second -I option.

Use angle brackets for standard header files, like stdio.h, and double quotes for files
that are part of your application.
Note: Both \ and / can be used as directory delimiters.
For more information, see Overview of the preprocessor, page 369.

257

AFE1_AFE2-1:1
Compiler output

Compiler output
The compiler can produce the following output:
● A linkable object file
The object files produced by the compiler use a proprietary format called UBROF,
which stands for Universal Binary Relocatable Object Format. By default, the object
file has the filename extension r43.
● Optional list files
Various kinds of list files can be specified using the compiler option -l, see -l, page
282. By default, these files will have the filename extension lst.
● Optional preprocessor output files
A preprocessor output file is produced when you use the --preprocess option. The
file will have the filename extension i, by default.
● Diagnostic messages
Diagnostic messages are directed to the standard error stream and displayed on the
screen, and printed in an optional list file. For more information about diagnostic
messages, see Diagnostics, page 259.
● Error return codes
These codes provide status information to the operating system which can be tested
in a batch file, see Error return codes, page 258.
● Size information
Information about the generated amount of bytes for functions and data for each
memory is directed to the standard output stream and displayed on the screen. Some
of the bytes might be reported as shared.
Shared objects are functions or data objects that are shared between modules. If any
of these occur in more than one module, only one copy is retained. For example, in
some cases inline functions are not inlined, which means that they are marked as
shared, because only one instance of each function will be included in the final
application. This mechanism is sometimes also used for compiler-generated code or
data not directly associated with a particular function or variable, and when only one
instance is required in the final application.

ERROR RETURN CODES

The compiler returns status information to the operating system that can be tested in a
batch file.

IAR C/C++ Compiler User Guide

258 for MSP430

AFE1_AFE2-1:1
 External interface details

These command line error codes are supported:

Code Description
0 Compilation successful, but there might have been warnings.
1 Warnings were produced and the option --warnings_affect_exit_code
was used.
2 Errors occurred.
3 Fatal errors occurred, making the compiler abort.
4 Internal errors occurred, making the compiler abort.
Table 31: Error return codes

Diagnostics
This section describes the format of the diagnostic messages and explains how
diagnostic messages are divided into different levels of severity.

MESSAGE FORMAT
All diagnostic messages are issued as complete, self-explanatory messages. A typical
diagnostic message from the compiler is produced in the form:
level[tag]: message filename linenumber

with these elements:

level The level of seriousness of the issue

tag A unique tag that identifies the diagnostic message
message An explanation, possibly several lines long
filename The name of the source file in which the issue was encountered
linenumber The line number at which the compiler detected the issue

Diagnostic messages are displayed on the screen, as well as printed in the optional list
file.
Use the option --diagnostics_tables to list all possible compiler diagnostic
messages.

259

AFE1_AFE2-1:1
Diagnostics

SEVERITY LEVELS
The diagnostic messages are divided into different levels of severity:

Remark
A diagnostic message that is produced when the compiler 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 296.

Warning
A diagnostic message that is produced when the compiler finds a potential programming
error or omission which is of concern, but which does not prevent completion of the
compilation. Warnings can be disabled by use of the command line option
--no_warnings, see --no_warnings, page 290.

Error
A diagnostic message that is produced when the compiler finds a construct which clearly
violates the C or C++ language rules, such that code cannot be produced. An error will
produce a non-zero exit code.

Fatal error
A diagnostic message produced when the compiler finds a condition that not only
prevents code generation, but also makes further processing of the source code pointless.
After the message is issued, compilation terminates. A fatal error will produce a
non-zero exit code.

SETTING THE SEVERITY LEVEL

The diagnostic messages can be suppressed or the severity level can be changed for all
diagnostics messages, except for fatal errors and some of the regular errors.
For information about the compiler options that are available for setting severity levels,
see the chapter Compiler options.
the chapter Pragma directives.

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 compiler. It is produced using this form:
Internal error: message

IAR C/C++ Compiler User Guide

260 for MSP430

AFE1_AFE2-1:1
 External interface details

where message is an explanatory message. If internal errors occur, they should be

reported to your software distributor or IAR Systems Technical Support. Include enough
information to reproduce the problem, typically:
● The product name
● The version number of the compiler, which can be seen in the header of the list files
generated by the compiler
● Your license number
● The exact internal error message text
● The source file of the application that generated the internal error
● A list of the options that were used when the internal error occurred.

261

AFE1_AFE2-1:1
Diagnostics

IAR C/C++ Compiler User Guide

262 for MSP430

AFE1_AFE2-1:1
 Compiler options
● Options syntax

● Summary of compiler options

● Descriptions of compiler options

Options syntax
Compiler options are parameters you can specify to change the default behavior of the
compiler. You can specify options from the command line—which is described in more
detail in this section—and from within the IDE.
See the online help system for information about the compiler options available in the
IDE and how to set them.

TYPES OF OPTIONS
There are two types of names for command line options, short names and long names.
Some options have both.
● A short option name consists of one character, and it can have parameters. You
specify it with a single dash, for example -e
● A long option name consists of one or several words joined by underscores, and it
can have parameters. You specify it with double dashes, for example
--char_is_signed.

For information about the different methods for passing options, see Passing options,
page 256.

RULES FOR SPECIFYING PARAMETERS

There are some general syntax rules for specifying option parameters. First, the rules
depending on whether the parameter is optional or mandatory, and whether the option
has a short or a long name, are described. Then, the rules for specifying filenames and
directories are listed. Finally, the remaining rules are listed.

Rules for optional parameters

For options with a short name and an optional parameter, any parameter should be
specified without a preceding space, for example:
-O or -Oh

263

AFE1_AFE2-1:1
Options syntax

For options with a long name and an optional parameter, any parameter should be
specified with a preceding equal sign (=), like this:
--example_option=value

Rules for mandatory parameters

For options with a short name and a mandatory parameter, the parameter can be
specified either with or without a preceding space, for example:
-I..\src or -I ..\src\

For options with a long name and a mandatory parameter, the parameter can be specified
either with a preceding equal sign (=) or with a preceding space, for example:
--diagnostics_tables=MyDiagnostics.lst

or
--diagnostics_tables MyDiagnostics.lst

Rules for options with both optional and mandatory parameters

For options taking both optional and mandatory parameters, the rules for specifying the
parameters are:
● For short options, optional parameters are specified without a preceding space
● For long options, optional parameters are specified with a preceding equal sign (=)
● For short and long options, mandatory parameters are specified with a preceding
space.
For example, a short option with an optional parameter followed by a mandatory
parameter:
-lA MyList.lst

For example, a long option with an optional parameter followed by a mandatory

parameter:
--preprocess=n PreprocOutput.lst

Rules for specifying a filename or directory as parameters

These rules apply for options taking a filename or directory as parameters:
● Options that take a filename as a parameter can optionally take a file path. The path
can be relative or absolute. For example, to generate a listing to the file List.lst
in the directory ..\listings\:
icc430 prog.c -l ..\listings\List.lst

IAR C/C++ Compiler User Guide

264 for MSP430

AFE1_AFE2-1:1
 Compiler options

● For options that take a filename as the destination for output, the parameter can be
specified as a path without a specified filename. The compiler stores the output in
that directory, in a file with an extension according to the option. The filename will
be the same as the name of the compiled source file, unless a different name was
specified with the option -o, in which case that name is used. For example:
icc430 prog.c -l ..\listings\
The produced list file will have the default name ..\listings\prog.lst
● The current directory is specified with a period (.). For example:
icc430 prog.c -l .
● / can be used instead of \ as the directory delimiter.
● By specifying -, input files and output files can be redirected to the standard input
and output stream, respectively. For example:
icc430 prog.c -l -

Additional rules
These rules also apply:
● 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 will create a list file called -r:
icc430 prog.c -l ---r
● For options that accept multiple arguments of the same type, the arguments can be
provided as a comma-separated list (without a space), for example:
--diag_warning=Be0001,Be0002
Alternatively, the option can be repeated for each argument, for example:
--diag_warning=Be0001
--diag_warning=Be0002

Summary of compiler options

This table summarizes the compiler command line options:
Command line option Description
--c89 Specifies the C89 dialect
--char_is_signed Treats char as signed
--char_is_unsigned Treats char as unsigned
--clib Uses the system include files for the CLIB library
--code_model Specifies the code model
Table 32: Compiler options summary

265

AFE1_AFE2-1:1
Summary of compiler options

Command line option Description

--core Specifies a CPU core
-D Defines preprocessor symbols
--data_model Specifies the data model
--debug Generates debug information
--dependencies Lists file dependencies
--diag_error Treats these as errors
--diag_remark Treats these as remarks
--diag_suppress Suppresses these diagnostics
--diag_warning Treats these as warnings
--diagnostics_tables Lists all diagnostic messages
--discard_unused_publics Discards unused public symbols
--dlib Uses the system include files for the DLIB library
--dlib_config Uses the system include files for the DLIB library
and determines which configuration of the library
to use
--double Forces the compiler to use 32-bit or 64-bit
doubles
-e Enables language extensions
--ec++ Specifies Embedded C++
--eec++ Specifies Extended Embedded C++
--enable_multibytes Enables support for multibyte characters in source
files
--enable_restrict Enables the Standard C keyword restrict
--error_limit Specifies the allowed number of errors before
compilation stops
-f Extends the command line
--guard_calls Enables guards for function static variable
initialization
--header_context Lists all referred source files and header files
--hw_workaround Enables workarounds for various hardware issues
-I Specifies include file path
-l Creates a list file
--library_module Creates a library module
Table 32: Compiler options summary (Continued)

IAR C/C++ Compiler User Guide

266 for MSP430

AFE1_AFE2-1:1
 Compiler options

Command line option Description

--lock_r4 Excludes register R4 from use
--lock_r5 Excludes register R5 from use
--macro_positions_in Obtains positions inside macros in diagnostic
_diagnostics messages
--mfc Enables multi-file compilation
--migration_preprocessor Extends the preprocessor
_extensions
--misrac Enables error messages specific to MISRA-C:1998.
This option is a synonym of --misrac1998 and
is only available for backwards compatibility.
--misrac1998 Enables error messages specific to MISRA-C:1998.
See the IAR Embedded Workbench® MISRA C:1998
Reference Guide.
--misrac2004 Enables error messages specific to MISRA-C:2004.
See the IAR Embedded Workbench® MISRA C:2004
Reference Guide.
--misrac_verbose IAR Embedded Workbench® MISRA C:1998
Reference Guide or the IAR Embedded Workbench®
MISRA C:2004 Reference Guide.
--module_name Sets the object module name
--multiplier Enables support for the hardware multiplier
--no_call_frame_info Disables output of call frame information
--no_code_motion Disables code motion optimization
--no_cse Disables common subexpression elimination
--no_inline Disables function inlining
--no_path_in_file_macros Removes the path from the return value of the
symbols __FILE__ and __BASE_FILE__
--no_rw_dynamic_init Issues an error message instead of rewriting
initializations.
--no_size_constraints Relaxes the normal restrictions for code size
expansion when optimizing for speed.
--no_static_destruction Disables destruction of C++ static variables at
program exit
--no_system_include Disables the automatic search for system include
files
Table 32: Compiler options summary (Continued)

267

AFE1_AFE2-1:1
Summary of compiler options

Command line option Description

--no_tbaa Disables type-based alias analysis
--no_typedefs_in_diagnostics Disables the use of typedef names in diagnostics
--no_ubrof_messages Excludes messages from UBROF files
--no_unroll Disables loop unrolling
--no_warnings Disables all warnings
--no_wrap_diagnostics Disables wrapping of diagnostic messages
-O Sets the optimization level
-o Sets the object filename. Alias for --output.
--omit_types Excludes type information
--only_stdout Uses standard output only
--output Sets the object filename
--pending_instantiations Sets the maximum number of instantiations of a
given C++ template.
--predef_macros Lists the predefined symbols.
--preinclude Includes an include file before reading the source
file
--preprocess Generates preprocessor output
--public_equ Defines a global named assembler label
-r Generates debug information. Alias for --debug.
--reduce_stack_usage Reduces stack usage
--regvar_r4 Reserves register R4 for use by global register
variables
--regvar_r5 Reserves register R5 for use by global register
variables
--relaxed_fp Relaxes the rules for optimizing floating-point
expressions
--remarks Enables remarks
--require_prototypes Verifies that functions are declared before they are
defined
--ropi Generates position-independent code and
read-only data.
--save_reg20 Declares all interrupt functions __save_reg20
by default
--segment Changes a segment name
Table 32: Compiler options summary (Continued)

IAR C/C++ Compiler User Guide

268 for MSP430

AFE1_AFE2-1:1
 Compiler options

Command line option Description

--silent Sets silent operation
--strict Checks for strict compliance with Standard
C/C++
--system_include_dir Specifies the path for system include files
--use_c++_inline Uses C++ inline semantics in C99
--version Sends compiler output to the console and then
exits.
--vla Enables C99 VLA support
--warn_about_c_style_casts Makes the compiler warn when C-style casts are
used in C++ source code
--warnings_affect_exit_code Warnings affect exit code
--warnings_are_errors Warnings are treated as errors
Table 32: Compiler options summary (Continued)

Descriptions of compiler options

The following section gives detailed reference information about each compiler option.
If you use the options page Extra Options to specify specific command line options,
the IDE does not perform an instant check for consistency problems like conflicting
options, duplication of options, or use of irrelevant options.

--c89
Syntax --c89

Description Use this option to enable the C89 C dialect instead of Standard C.
Note: This option is mandatory when the MISRA C checking is enabled.

See also C language overview, page 197.

Project>Options>C/C++ Compiler>Language 1>C dialect>C89

269

AFE1_AFE2-1:1
Descriptions of compiler options

--char_is_signed
Syntax --char_is_signed

Description By default, the compiler interprets the plain char type as unsigned. Use this option to
make the compiler interpret the plain char type as signed instead. This can be useful
when you, for example, want to maintain compatibility with another compiler.
Note: The runtime library is compiled without the --char_is_signed option and
cannot be used with code that is compiled with this option.
Project>Options>C/C++ Compiler>Language 2>Plain ‘char’ is

--char_is_unsigned
Syntax --char_is_unsigned

Description Use this option to make the compiler interpret the plain char type as unsigned. This is
the default interpretation of the plain char type.
Project>Options>C/C++ Compiler>Language 2>Plain ‘char’ is

--clib
Syntax --clib

Description Use this option to use the system header files for the CLIB library; the compiler will
automatically locate the files and use them when compiling.

See also --dlib, page 276 and --dlib_config, page 277.

To set related options, choose:
Project>Options>General Options>Library Configuration

--code_model
Syntax --code_model={small|large}

Parameters
small Uses the Small code model

IAR C/C++ Compiler User Guide

270 for MSP430

AFE1_AFE2-1:1
 Compiler options

large (default) Uses the Large code model

Description Use this option to select the code model, which controls which instruction sequences are
used for function calls and returns. If you do not select a code model, the compiler uses
the default code model. Note that all modules of your application must use the same
code model.
Note: This option is only available if --core is set to 430X.

See also Code models (MSP430X only), page 71

Project>Options>General Options>Target>Code model

--core
Syntax --core={430|430X}

Parameters
430 (default) For devices based on the MSP430 architecture
430X For devices based on the MSP430X architecture

Description Use this option to select the processor core for which the code will be generated. If you
do not use the option to specify a core, Note that all modules of your application must
use the same core.
Project>Options>General Options>Target>Device

-D
Syntax -D symbol[=value]

Parameters
symbol The name of the preprocessor symbol
value The value of the preprocessor symbol

Description Use this option to define a preprocessor symbol. If no value is specified, 1 is used. This
option can be used one or more times on the command line.

271

AFE1_AFE2-1:1
Descriptions of compiler options

The option -D has the same effect as a #define statement at the top of the source file:
-Dsymbol

is equivalent to:
#define symbol 1

To get the equivalence of:

#define FOO

specify the = sign but nothing after, for example:

-DFOO=

Project>Options>C/C++ Compiler>Preprocessor>Defined symbols

--data_model
Syntax --data_model={small|medium|large}

Parameters
small (default) Uses the Small data model.
medium Uses the Medium data model.
large Uses the Large data model.

Description Use this option to select the data model, which controls the default placement of data
objects. If you do not select a data model, the compiler uses the default data model. Note
that all modules of your application must use the same data model.
Note: This option is only available if --core is set to 430X.

See also Data models, page 66 and __DATA_MODEL__, page 371.

Project>Options>General Options>Target>Data model

--debug, -r
Syntax --debug
-r

IAR C/C++ Compiler User Guide

272 for MSP430

AFE1_AFE2-1:1
 Compiler options

Description Use the --debug or -r option to make the compiler include information in the object
modules required by the IAR C-SPY® Debugger and other symbolic debuggers.
Note: Including debug information will make the object files larger than otherwise.
Project>Options>C/C++ Compiler>Output>Generate debug information

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

Parameters
i (default) Lists only the names of files
m Lists in makefile style (multiple rules)
n Lists in makefile style (one rule)
s Suppresses system files
+ Gives the same output as -o, but with the filename extension d

See also Rules for specifying a filename or directory as parameters, page 264.

Description Use this option to make the compiler list the names of all source and header files opened
for input into a file with the default filename extension i.

Example If --dependencies or --dependencies=i is used, the name of each opened input

file, including the full path, if available, is output on a separate line. For example:
c:\iar\product\include\stdio.h
d:\myproject\include\foo.h

If --dependencies=m is used, the output is in makefile style. For each input file, one
line containing a makefile dependency rule is produced. Each line consists of the name
of the object file, a colon, a space, and the name of an input file. For example:
foo.r43: c:\iar\product\include\stdio.h
foo.r43: d:\myproject\include\foo.h

An example of using --dependencies with a popular make utility, such as gmake

(GNU make):
1 Set up the rule for compiling files to be something like:
%.r43 : %.c
$(ICC) $(ICCFLAGS) $< --dependencies=m $*.d

273

AFE1_AFE2-1:1
Descriptions of compiler options

That is, in addition to producing an object file, the command also produces a
dependency file in makefile style—in this example, using the extension .d.
2 Include all the dependency files in the makefile using, for example:
-include $(sources:.c=.d)

Because of the dash (-) 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
tag The number of a diagnostic message, for example, the
message number Pe117

Description Use this option to reclassify certain diagnostic messages as errors. An error indicates a
violation of the C or C++ language rules, of such severity that object code will not be
generated. The exit code will be non-zero. This option may be used more than once on
the command line.
Project>Options>C/C++ Compiler>Diagnostics>Treat these as errors

--diag_remark
Syntax --diag_remark=tag[,tag,...]

Parameters
tag The number of a diagnostic message, for example, the
message number Pe177

Description Use this option to reclassify certain diagnostic messages as remarks. A remark is the
least severe type of diagnostic message and indicates a source code construction that
may cause strange behavior in the generated code. This option may be used more than
once on the command line.
Note: By default, remarks are not displayed—use the --remarks option to display
them.

IAR C/C++ Compiler User Guide

274 for MSP430

AFE1_AFE2-1:1
 Compiler options

Project>Options>C/C++ Compiler>Diagnostics>Treat these as remarks

--diag_suppress
Syntax --diag_suppress=tag[,tag,...]

Parameters
tag The number of a diagnostic message, for example, the
message number Pe117

Description Use this option to suppress certain diagnostic messages. These messages will not be
displayed. This option may be used more than once on the command line.
Project>Options>C/C++ Compiler>Diagnostics>Suppress these diagnostics

--diag_warning
Syntax --diag_warning=tag[,tag,...]

Parameters
tag The number of a diagnostic message, for example, the
message number Pe826

Description Use this option to reclassify certain diagnostic messages as warnings. A warning
indicates an error or omission that is of concern, but which will not cause the compiler
to stop before compilation is completed. This option may be used more than once on the
command line.
Project>Options>C/C++ Compiler>Diagnostics>Treat these as warnings

--diagnostics_tables
Syntax --diagnostics_tables {filename|directory}

Parameters See Rules for specifying a filename or directory as parameters, page 264.

275

AFE1_AFE2-1:1
Descriptions of compiler options

Description Use this option to list all possible diagnostic messages to a named file. This can be
convenient, for example, if you have used a pragma directive to suppress or change the
severity level of any diagnostic messages, but forgot to document why.
Typically, this option cannot be given together with other options.
To set this option, use Project>Options>C/C++ Compiler>Extra Options.

--discard_unused_publics
Syntax --discard_unused_publics

Description Use this option to discard unused public functions and variables when compiling with
the --mfc compiler option.
Note: Do not use this option only on parts of the application, as necessary symbols
might be removed from the generated output. Use the object attribute __root to keep
symbols that are used from outside the compilation unit, for example, interrupt handlers.
If the symbol does not have the __root attribute and is defined in the library, the library
definition will be used instead.

See also --mfc, page 284 and Multi-file compilation units, page 241.
Project>Options>C/C++ Compiler>Discard unused publics

--dlib
Syntax --dlib

Description Use this option to use the system header files for the DLIB library—the compiler will
automatically locate the files and use them when compiling.
Note: The DLIB library is used by default: To use the CLIB library, use the --clib
option instead.

See also --dlib_config, page 277, --no_system_include, page 288, --system_include_dir, page
299, and --clib, page 270.
To set related options, choose:
Project>Options>General Options>Library Configuration

IAR C/C++ Compiler User Guide

276 for MSP430

AFE1_AFE2-1:1
 Compiler options

--dlib_config
Syntax --dlib_config filename.h|config

Parameters
filename A DLIB configuration header file, see Rules for specifying a
filename or directory as parameters, page 264.
config The default configuration file for the specified configuration
will be used. Choose between:
none, no configuration will be used

normal, the normal library configuration will be used

full, the full library configuration will be used.

Description Use this option to specify which library configuration to use, either by specifying an
explicit file or by specifying a library configuration—in which case the default file for
that library configuration will be used. Make sure that you specify a configuration that
corresponds to the library you are using. If you do not specify this option, the default
library configuration file will be used.
All prebuilt runtime libraries are delivered with corresponding configuration files. You
can find the library object files in the directory 430\lib. For examples and information
about prebuilt runtime libraries, see Prebuilt runtime libraries, page 127.
If you build your own customized runtime library, you should also create a
corresponding customized library configuration file, which must be specified to the
compiler. For more information, see Customizing and building your own runtime
library, page 124.
Note: This option only applies to the IAR DLIB runtime environment.
To set related options, choose:
Project>Options>General Options>Library Configuration

--double
Syntax --double={32|64}

Parameters
32 (default) 32-bit doubles are used
64 64-bit doubles are used

277

AFE1_AFE2-1:1
Descriptions of compiler options

Description Use this option to select the precision used by the compiler for representing the
floating-point types double and long double. The compiler can use either 32-bit or
64-bit precision. By default, the compiler uses 32-bit precision.

See also Basic data types—floating-point types, page 307.

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

-e
Syntax -e

Description In the command line version of the compiler, language extensions are disabled by
default. If you use language extensions such as extended keywords and anonymous
structs and unions in your source code, you must use this option to enable them.
Note: The -e option and the --strict option cannot be used at the same time.

See also Enabling language extensions, page 199.

Project>Options>C/C++ Compiler>Language 1>Standard with IAR extensions
Note: By default, this option is selected in the IDE.

--ec++
Syntax --ec++

Description In the compiler, the default language is C. If you use Embedded C++, you must use this
option to set the language the compiler uses to Embedded C++.
Project>Options>C/C++ Compiler>Language 1>C++
and
Project>Options>C/C++ Compiler>Language 1>C++ dialect>Embedded C++

IAR C/C++ Compiler User Guide

278 for MSP430

AFE1_AFE2-1:1
 Compiler options

--eec++
Syntax --eec++

Description In the compiler, the default language is C. If you take advantage of Extended Embedded
C++ features like namespaces or the standard template library in your source code, you
must use this option to set the language the compiler uses to Extended Embedded C++.

See also Extended Embedded C++, page 206.

Project>Options>C/C++ Compiler>Language 1>C++
and
Project>Options>C/C++ Compiler>Language 1>C++ dialect>Extended
Embedded C++

--enable_multibytes
Syntax --enable_multibytes

Description By default, multibyte characters cannot be used in C or C++ source code. Use this option
to make multibyte characters in the source code be interpreted according to the host
computer’s default setting for multibyte support.
Multibyte characters are allowed in C and C++ style comments, in string literals, and in
character constants. They are transferred untouched to the generated code.
Project>Options>C/C++ Compiler>Language 2>Enable multibyte support

--enable_restrict
Syntax --enable_restrict

Description Enables the Standard C keyword restrict. This option can be useful for improving
analysis precision during optimization.
To set this option, use Project>Options>C/C++ Compiler>Extra options

279

AFE1_AFE2-1:1
Descriptions of compiler options

--error_limit
Syntax --error_limit=n

Parameters
n The number of errors before the compiler stops the
compilation. n must be a positive integer. 0 indicates no
limit.

Description Use the --error_limit option to specify the number of errors allowed before the
compiler stops the compilation. By default, 100 errors are allowed.
This option is not available in the IDE.

-f
Syntax -f filename

Parameters See Rules for specifying a filename or directory as parameters, page 264.

Description Use this option to make the compiler read command line options from the named file,
with the default filename extension xcl.
In the command file, you format the items exactly as if they were on the command line
itself, except that you may use multiple lines, because the newline character acts just as
a space or tab character.
Both C and C++ style comments are allowed in the file. Double quotes behave in the
same way as in the Microsoft Windows command line environment.
To set this option, use Project>Options>C/C++ Compiler>Extra Options.

--guard_calls
Syntax --guard_calls

Description Use this option to enable guards for function static variable initialization. This option
should be used in a threaded C++ environment.

See also Managing a multithreaded environment, page 154.

IAR C/C++ Compiler User Guide

280 for MSP430

AFE1_AFE2-1:1
 Compiler options

Project>Options>C/C++ Compiler>Language 2>Guard Calls

--header_context
Syntax --header_context

Description Occasionally, to find the cause of a problem it is necessary to know which header file
that was included from which source line. 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.
This option is not available in the IDE.

--hw_workaround
Syntax --hw_workaround=[CPU6|nop_after_lpm|CPU40]

Parameters
CPU6 Workaround for hardware issue CPU6
nop_after_lpm Workaround for hardware issues CPU18, CPU19, CPU24,
CPU25, CPU27, and CPU29
CPU40 Workaround for hardware issue CPU40

Description Use this option to enable compiler workarounds for various hardware issues. Specify the
option multiple times if you need to enable more than one workaround.

See also For more information about the workarounds available for the different hardware issues,
see the release notes.
When you select a device in the IAR Embedded Workbench IDE, the relevant hardware
workarounds are enabled automatically.
Note: The workaround for hardware issue CPU6 is not enabled automatically. To set
this option for CPU6, use Project>Options>C/C++ Compiler>Extra Options.

281

AFE1_AFE2-1:1
Descriptions of compiler options

-I
Syntax -I path

Parameters
path The search path for #include files

Description Use this option to specify the search paths for #include files. This option can be used
more than once on the command line.

See also Include file search procedure, page 256.

Project>Options>C/C++ Compiler>Preprocessor>Additional include directories

-l
Syntax -l[a|A|b|B|c|C|D][N][H] {filename|directory}

Parameters
a (default) Assembler list file
A Assembler list file with C or C++ source as comments
b Basic assembler list file. This file has the same contents as a
list file produced with -la, except that no extra
compiler-generated information (runtime model attributes,
call frame information, frame size information) is included *
B Basic assembler list file. This file has the same contents as a
list file produced with -lA, except that no extra compiler
generated information (runtime model attributes, call frame
information, frame size information) is included *
c C or C++ list file
C (default) C or C++ list file with assembler source as comments
D C or C++ list file with assembler source as comments, but
without instruction offsets and hexadecimal byte values
N No diagnostics in file
H Include source lines from header files in output. Without this
option, only source lines from the primary source file are
included

IAR C/C++ Compiler User Guide

282 for MSP430

AFE1_AFE2-1:1
 Compiler options

* This makes the list file less useful as input to the assembler, but more useful for reading
by a human.
See also Rules for specifying a filename or directory as parameters, page 264.

Description Use this option to generate an assembler or C/C++ listing to a file.

Note: This option can be used one or more times on the command line.
To set related options, choose:
Project>Options>C/C++ Compiler>List

--library_module
Syntax --library_module

Description Use this option to make the compiler generate a library module rather than a program
module. A program module is always included during linking. A library module will
only be included if it is referenced in your program.
Project>Options>C/C++ Compiler>Output>Module type>Library Module

--lock_r4
Syntax --lock_R4

Description Use this option to exclude the register R4 from use by the compiler. This makes the
module linkable with both modules that use R4 as __regvar and modules that do not
define their R4 usage. Use this option if the R4 registers is used by another tool, for
example a ROM-monitor debugger.
Project>Options>C/C++ Compiler>Code>R4 utilization>Not used

--lock_r5
Syntax --lock_R5

Description Use this option to exclude the register R5 from use by the compiler. This makes the
module linkable with both modules that use R5 as __regvar and modules that do not
define their R5 usage. Use this option if the R5 registers is used by another tool, for
example a ROM-monitor debugger.

283

AFE1_AFE2-1:1
Descriptions of compiler options

Project>Options>C/C++ Compiler>Code>R5 utilization>Not used

--macro_positions_in_diagnostics
Syntax --macro_positions_in_diagnostics

Description Use this option to obtain position references inside macros in diagnostic messages. This
is useful for detecting incorrect source code constructs in macros.
To set this option, use Project>Options>C/C++ Compiler>Extra Options.

--mfc
Syntax --mfc

Description Use this option to enable multi-file compilation. This means that the compiler compiles
one or several source files specified on the command line as one unit, which enhances
interprocedural optimizations.
Note: The compiler will generate one object file per input source code file, where the
first object file contains all relevant data and the other ones are empty. If you want only
the first file to be produced, use the -o compiler option and specify a certain output file.

Example icc430 myfile1.c myfile2.c myfile3.c --mfc

See also --discard_unused_publics, page 276, --output, -o, page 292, and Multi-file compilation
units, page 241.
Project>Options>C/C++ Compiler>Multi-file compilation

--migration_preprocessor_extensions
Syntax --migration_preprocessor_extensions

Description If you need to migrate code from an earlier IAR Systems C or C++ compiler, you might
want to use this option. Use this option to use the following in preprocessor expressions:
● Floating-point expressions
● Basic type names and sizeof

IAR C/C++ Compiler User Guide

284 for MSP430

AFE1_AFE2-1:1
 Compiler options

● All symbol names (including typedefs and variables).

Note: If you use this option, not only will the compiler accept code that does not
conform to Standard C, but it will also reject some code that does conform to the
standard.
Important! Do not depend on these extensions in newly written code, because support
for them might be removed in future compiler versions.
Project>Options>C/C++ Compiler>Language 1>Enable IAR migration
preprocessor extensions

--module_name
Syntax --module_name=name

Parameters
name An explicit object module name

Description Normally, the internal name of the object module is the name of the source file, without
a directory name or extension. Use this option to specify an object module name
explicitly.
This option is useful when several modules have the same filename, because the
resulting duplicate module name would normally cause a linker error; for example,
when the source file is a temporary file generated by a preprocessor.
Project>Options>C/C++ Compiler>Output>Object module name

--multiplier
Syntax --multiplier[=[16|16s|32]]

Parameters
No parameter The 16-bit hardware multiplier
16 The 16-bit hardware multiplier (same as no parameter)
16s The extended 16-bit hardware multiplier used by some 2xx devices
32 The 32-bit hardware multiplier

Description Use this option to generate code that accesses the hardware multiplier. This will also
disable interrupts during hardware multiplier accesses.

285

AFE1_AFE2-1:1
Descriptions of compiler options

Note: You should also redirect library function calls to variants that use the hardware
multiplier, see Hardware multiplier support, page 151.
To set related options, choose:
Project>Options>General Options>Target>Device
and
Project>Options>General Options>Target>Hardware multiplier

--no_call_frame_info
Syntax --no_call_frame_info

Description Normally, the compiler always generates call frame information in the output, to enable
the debugger to display the call stack even in code from modules with no debug
information. Use this option to disable the generation of call frame information.

See also Call frame information, page 193.

To set this option, use Project>Options>C/C++ Compiler>Extra Options.

--no_code_motion
Syntax --no_code_motion

Description Use this option to disable code motion optimizations.

Note: This option has no effect at optimization levels below Medium.

See also Code motion, page 244.

Project>Options>C/C++ Compiler>Optimizations>Enable
transformations>Code motion

--no_cse
Syntax --no_cse

Description Use this option to disable common subexpression elimination.

Note: This option has no effect at optimization levels below Medium.

IAR C/C++ Compiler User Guide

286 for MSP430

AFE1_AFE2-1:1
 Compiler options

See also Common subexpression elimination, page 243.

Project>Options>C/C++ Compiler>Optimizations>Enable
transformations>Common subexpression elimination

--no_inline
Syntax --no_inline

Description Use this option to disable function inlining.

See also Inlining functions, page 81.

Project>Options>C/C++ Compiler>Optimizations>Enable
transformations>Function inlining

--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__.

See also Description of predefined preprocessor symbols, page 370.

This option is not available in the IDE.

--no_rw_dynamic_init
Syntax --no_rw_dynamic_init

Description When the option --ropi is used, the actual addresses of constant variables are not
known until at runtime. Therefore, pointers to constant data cannot be initialized
statically. The compiler rewrites such static initializations to be dynamic where it is
possible. Use the --no_rw_dynamic_init option to make the compiler give an error
instead of rewriting the initializations.
This option has no effect if --ropi is not used.

See also --ropi, page 296 and Position-independent code and read-only data, page 80.

287

AFE1_AFE2-1:1
Descriptions of compiler options

Project>Options>C/C++ Compiler>Code>No dynamic read/write initialization

--no_size_constraints
Syntax --no_size_constraints

Description Use this option to relax the normal restrictions for code size expansion when optimizing
for high speed.
Note: This option has no effect unless used with -Ohs.

See also Speed versus size, page 242.

Project>Options>C/C++ Compiler>Optimizations>Enable transformations>No
size constraints

--no_static_destruction
Syntax --no_static_destruction

Description Normally, the compiler emits code to destroy C++ static variables that require
destruction at program exit. Sometimes, such destruction is not needed.
Use this option to suppress the emission of such code.

See also System termination, page 137.

To set this option, use Project>Options>C/C++ Compiler>Extra Options.

--no_system_include
Syntax --no_system_include

Description By default, the compiler 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 compiler option.

See also --dlib, page 276, --dlib_config, page 277, and --system_include_dir, page 299.
Project>Options>C/C++ Compiler>Preprocessor>Ignore standard include
directories

IAR C/C++ Compiler User Guide

288 for MSP430

AFE1_AFE2-1:1
 Compiler options

--no_tbaa
Syntax --no_tbaa

Description Use this option to disable type-based alias analysis.

Note: This option has no effect at optimization levels below High.

See also Type-based alias analysis, page 244.

Project>Options>C/C++ Compiler>Optimizations>Enable
transformations>Type-based alias analysis

--no_typedefs_in_diagnostics
Syntax --no_typedefs_in_diagnostics

Description Use this option to disable the use of typedef names in diagnostics. Normally, when a
type is mentioned in a message from the compiler, most commonly in a diagnostic
message of some kind, the typedef names that were used in the original declaration are
used whenever they make the resulting text shorter.

Example typedef int (*MyPtr)(char const *);

MyPtr p = "My text string";

will give an error message like this:

Error[Pe144]: a value of type "char *" cannot be used to
initialize an entity of type "MyPtr"

If the --no_typedefs_in_diagnostics option is used, the error message will be like

this:
Error[Pe144]: a value of type "char *" cannot be used to
initialize an entity of type "int (*)(char const *)"

To set this option, use Project>Options>C/C++ Compiler>Extra Options.

289

AFE1_AFE2-1:1
Descriptions of compiler options

--no_ubrof_messages
Syntax --no_ubrof_messages

Description Use this option to minimize the size of your application object file by excluding
messages from the UBROF files. The file size can decrease by up to 60%. Note that the
XLINK diagnostic messages will, however, be less useful when you use this option.
To set this option, use Project>Options>C/C++ Compiler>Extra Options.

--no_unroll
Syntax --no_unroll

Description Use this option to disable loop unrolling.

Note: This option has no effect at optimization levels below High.

See also Loop unrolling, page 244.

Project>Options>C/C++ Compiler>Optimizations>Enable
transformations>Loop unrolling

--no_warnings
Syntax --no_warnings

Description By default, the compiler issues warning messages. Use this option to disable all warning
messages.
This option is not available in the IDE.

--no_wrap_diagnostics
Syntax --no_wrap_diagnostics

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

IAR C/C++ Compiler User Guide

290 for MSP430

AFE1_AFE2-1:1
 Compiler options

-O
Syntax -O[n|l|m|h|hs|hz]

Parameters
n None* (Best debug support)
l (default) Low*
m Medium
h High, balanced
hs High, favoring speed
hz High, favoring size

*All optimizations performed at level Low will be performed also at None. The only
difference is that at level None, all non-static variables will live during their entire scope.

Description Use this option to set the optimization level to be used by the compiler when optimizing
the code. If no optimization option is specified, the optimization level Low is used by
default. If only -O is used without any parameter, the optimization level High balanced
is used.
A low level of optimization makes it relatively easy to follow the program flow in the
debugger, and, conversely, a high level of optimization makes it relatively hard.

See also Controlling compiler optimizations, page 240.

Project>Options>C/C++ Compiler>Optimizations

--omit_types
Syntax --omit_types

Description By default, the compiler includes type information about variables and functions in the
object output. Use this option if you do not want the compiler to include this type
information in the output, which is useful when you build a library that should not
contain type information. The object file will then only contain type information that is
a part of a symbol’s name. This means that the linker cannot check symbol references
for type correctness.
To set this option, use Project>Options>C/C++ Compiler>Extra Options.

291

AFE1_AFE2-1:1
Descriptions of compiler options

--only_stdout
Syntax --only_stdout

Description Use this option to make the compiler use the standard output stream (stdout), and
messages that are normally directed to the error output stream (stderr).
This option is not available in the IDE.

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

Parameters See Rules for specifying a filename or directory as parameters, page 264.

Description By default, the object code output produced by the compiler is located in a file with the
same name as the source file, but with the extension r43. Use this option to explicitly
specify a different output filename for the object code output.
This option is not available in the IDE.

--pending_instantiations
Syntax --pending_instantiations number

Parameters
number An integer that specifies the limit, where 64 is default. If 0
is used, there is no limit.

Description Use this option to specify the maximum number of instantiations of a given C++
template that is allowed to be in process of being instantiated at a given time. This is
used for detecting recursive instantiations.
Project>Options>C/C++ Compiler>Extra Options

IAR C/C++ Compiler User Guide

292 for MSP430

AFE1_AFE2-1:1
 Compiler options

--predef_macros
Syntax --predef_macros {filename|directory}

Parameters See Rules for specifying a filename or directory as parameters, page 264.

Description Use this option to list all symbols defined by the compiler or on the command line.
(Symbols defined in the source code are not listed.) When using this option, make sure
to also use the same options as for the rest of your project.
If a filename is specified, the compiler stores the output in that file. If a directory is
specified, the compiler stores the output in that directory, in a file with the predef
filename extension.
Note: This option requires that you specify a source file on the command line.
This option is not available in the IDE.

--preinclude
Syntax --preinclude includefile

Parameters See Rules for specifying a filename or directory as parameters, page 264.

Description Use this option to make the compiler read 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.
Project>Options>C/C++ Compiler>Preprocessor>Preinclude file

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

Parameters
c Preserve comments
n Preprocess only
l Generate #line directives

See also Rules for specifying a filename or directory as parameters, page 264.

293

AFE1_AFE2-1:1
Descriptions of compiler options

Description Use this option to generate preprocessed output to a named file.

Project>Options>C/C++ Compiler>Preprocessor>Preprocessor output to file

--public_equ
Syntax --public_equ symbol[=value]

Parameters
symbol The name of the assembler symbol to be defined
value An optional value of the defined assembler symbol

Description This option is equivalent to defining a label in assembler language using the EQU
directive and exporting it using the PUBLIC directive. This option can be used more than
once on the command line.
This option is not available in the IDE.

--reduce_stack_usage
Syntax --reduce_stack_usage

Description Use this option to make the compiler minimize the use of stack space at the cost of
somewhat larger and slower code.
Project>Options>C/C++ Compiler>Code>Reduce stack usage

--regvar_r4
Syntax --regvar_r4

Description Use this option to reserve the register R4 for use by global register variables, declared
with the __regvar attribute. This can give more efficient code if used on frequently
used variables.

See also --lock_r4, page 283 and __regvar, page 328.

Project>Options>C/C++ Compiler>Code>R4 utilization>__regvar variables

IAR C/C++ Compiler User Guide

294 for MSP430

AFE1_AFE2-1:1
 Compiler options

--regvar_r5
Syntax --regvar_r5

Description Use this option to reserve the register R5 for use by global register variables, declared
with the __regvar attribute. This can give more efficient code if used on frequently
used variables.

See also --lock_r5, page 283 and __regvar, page 328.

Project>Options>C/C++ Compiler>Code>R5 utilization>__regvar variables

--relaxed_fp
Syntax --relaxed_fp

Description Use this option to allow the compiler to relax the language rules and perform more
aggressive optimization of floating-point expressions. This option improves
performance for floating-point expressions that fulfill these conditions:
● The expression consists of both single and double-precision values
● The double-precision values can be converted to single precision without loss of
accuracy
● The result of the expression is converted to single precision.
Note: Performing the calculation in single precision instead of double precision might
cause a loss of accuracy.

Example float F(float a, float b)

{
return a + b * 3.0;
}

The C standard states that 3.0 in this example has the type double and therefore the
whole expression should be evaluated in double precision. However, when the
--relaxed_fp option is used, 3.0 will be converted to float and the whole expression
can be evaluated in float precision.
To set related options, choose:
Project>Options>C/C++ Compiler>Language 2>Floating-point semantics

295

AFE1_AFE2-1:1
Descriptions of compiler options

--remarks
Syntax --remarks

Description The least severe diagnostic messages are called remarks. A remark indicates a source
code construct that may cause strange behavior in the generated code. By default, the
compiler does not generate remarks. Use this option to make the compiler generate
remarks.

See also Severity levels, page 260.

Project>Options>C/C++ Compiler>Diagnostics>Enable remarks

--require_prototypes
Syntax --require_prototypes

Description Use this option to force the compiler to verify that all functions have proper prototypes.
Using this option means that code containing any of the following will generate an error:
● A function call of a function with no declaration, or with a Kernighan & Ritchie
C declaration
● A function definition of a public function with no previous prototype declaration
● An indirect function call through a function pointer with a type that does not include
a prototype.
Project>Options>C/C++ Compiler>Language 1>Require prototypes

--ropi
Syntax --ropi

Description Use this option to make the compiler generate position-independent code and read-only
data.
The --ropi option has some drawbacks and limitations, see Drawbacks and
limitations, page 80.
Note: The --ropi option is deprecated in IAR Embedded Workbench for MSP430
from version 6.50.

IAR C/C++ Compiler User Guide

296 for MSP430

AFE1_AFE2-1:1
 Compiler options

See also Position-independent code and read-only data, page 80, __no_pic, page 326, and
--no_rw_dynamic_init, page 287. For information about the preprocessor symbol
__ROPI__, see Description of predefined preprocessor symbols, page 370.

Project>Options>C/C++ Compiler>Code>Code and read-only data (ropi)

--save_reg20
Syntax --save_reg20

Description Use this option to make all interrupt functions be treated as a __save_reg20 declared
function. This means that you do not have to explicitly use the __save_reg20 keyword
on any interrupt functions.
This is necessary if your application requires that all 20 bits of registers are preserved.
The drawback is that the code will be somewhat slower.
Note: This option is only available when compiling for the MSP430X architecture.

See also __save_reg20, page 329

Project>Options>C/C++ Compiler>Code>20-bit context save on interrupt

--segment
Syntax --segment __memory_attribute=BASENAME
--segment specialsegment=NAME

Parameters
__memory_attribute Can be one of:

__data16 Base name for __data16 memory

__data20 Base name for __data20 memory
__regvar Base name for __regvar variables
BASENAME The segment group name, corresponding to
__memory_attribute.

297

AFE1_AFE2-1:1
Descriptions of compiler options

specialsegment Can be one of:

code Normal code
code16 Normal code, MSP430X small code model
cstack The runtime stack
difunct C++ dynamic initialization
intvec The interrupt vector table
isr_code Interrupt code
ramfunc_code __ramfunc code

NAME The new name of the renamed segment

Description The compiler places functions and data objects into named segments which are referred
to by the IAR XLINK Linker. Use the --segment option to perform one of these
operations:
● To place data objects declared with the __memory_attribute in segments with
names that begin with BASENAME.
● To change the name of a special segment to NAME.
This is useful if you want to place your code or data in different address ranges and you
find the @ notation, alternatively the #pragma location directive, insufficient. Note
that any changes to the segment names require corresponding modifications in the linker
configuration file.

Example --segment __data16=MYDATA

This command places the __data16 int a; defined variable in the MYDATA_Z
segment:
This command names the segment that contains interrupt vectors to MYINTS instead of
the default name INTVEC:
--segment intvec=MYINTS

See also Controlling data and function placement in memory, page 236 and Summary of extended
keywords, page 320.
Project>Options>C/C++ Compiler>Output>Override segment base name

IAR C/C++ Compiler User Guide

298 for MSP430

AFE1_AFE2-1:1
 Compiler options

--silent
Syntax --silent

Description By default, the compiler issues introductory messages and a final statistics report. Use
this option to make the compiler operate without sending these messages to the standard
output stream (normally the screen).
This option does not affect the display of error and warning messages.
This option is not available in the IDE.

--strict
Syntax --strict

Description By default, the compiler accepts a relaxed superset of Standard C and C++. Use this
option to ensure that the source code of your application instead conforms to strict
Standard C and C++.
Note: The -e option and the --strict option cannot be used at the same time.

See also Enabling language extensions, page 199.

Project>Options>C/C++ Compiler>Language 1>Language conformance>Strict

--system_include_dir
Syntax --system_include_dir path

Parameters
path The path to the system include files, see Rules for specifying
a filename or directory as parameters, page 264.

Description By default, the compiler 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.

See also --dlib, page 276, --dlib_config, page 277, and --no_system_include, page 288.
This option is not available in the IDE.

299

AFE1_AFE2-1:1
Descriptions of compiler options

--use_c++_inline
Syntax --use_c++_inline

Description Standard C uses slightly different semantics for the inline keyword than C++ does.
Use this option if you want C++ semantics when you are using C.

See also Inlining functions, page 81.

Project>Options>C/C++ Compiler>Language 1>C dialect>C99>C++ inline
semantics

--version
Syntax --version

Description Use this option to make the compiler send version information to the console and then
exit.
This option is not available in the IDE.

--vla
Syntax --vla

Description Use this option to enable support for C99 variable length arrays. Such arrays are located
on the heap. This option requires Standard C and cannot be used together with the
--c89 compiler option.

Note: --vla should not be used together with the longjmp library function, as that can
lead to memory leakages.

See also C language overview, page 197.

Project>Options>C/C++ Compiler>Language 1>C dialect>Allow VLA

IAR C/C++ Compiler User Guide

300 for MSP430

AFE1_AFE2-1:1
 Compiler options

--warn_about_c_style_casts
Syntax --warn_about_c_style_casts

Description Use this option to make the compiler warn when C-style casts are used in C++ source
code.
This option is not available in the IDE.

--warnings_affect_exit_code
Syntax --warnings_affect_exit_code

Description By default, the exit code is not affected by warnings, because only errors produce a
non-zero exit code. With this option, warnings will also generate a non-zero exit code.
This option is not available in the IDE.

--warnings_are_errors
Syntax --warnings_are_errors

Description Use this option to make the compiler treat all warnings as errors. If the compiler
encounters an error, no object code is generated. Warnings that have been changed into
remarks are not treated as errors.
Note: Any diagnostic messages that have been reclassified as warnings by the option
--diag_warning or the #pragma diag_warning directive will also be treated as
errors when --warnings_are_errors is used.

See also --diag_warning, page 275.

Project>Options>C/C++ Compiler>Diagnostics>Treat all warnings as errors

301

AFE1_AFE2-1:1
Descriptions of compiler options

IAR C/C++ Compiler User Guide

302 for MSP430

AFE1_AFE2-1:1
 Data representation
● Alignment

● Basic data types—integer types

● Basic data types—floating-point types

● Pointer types

● Structure types

● Type qualifiers

● Data types in C++

See the chapter Efficient coding for embedded applications for information about
which data types provide the most efficient code for your application.

Alignment
Every C data object has an alignment that controls how the object can be stored in
memory. Should an object have an alignment of, for example, 4, it must be stored on an
address that is divisible by 4.
The reason for the concept of alignment is that some processors have hardware
limitations for how the memory can be accessed.
Assume that a processor can read 4 bytes of memory using one instruction, but only
when the memory read is placed on an address divisible by 4. Then, 4-byte objects, such
as long integers, will have alignment 4.
Another processor might only be able to read 2 bytes at a time; in that environment, the
alignment for a 4-byte long integer might be 2.
A structure type will have the same alignment as the structure member with the most
strict alignment. To decrease the alignment requirements on the structure and its
members, use #pragma pack.
All data types must have a size that is a multiple of their alignment. Otherwise, only the
first element of an array would be guaranteed to be placed in accordance with the
alignment requirements. This means that the compiler might add pad bytes at the end of

303

AFE1_AFE2-1:1
Basic data types—integer types

the structure. For more information about pad bytes, see Packed structure types, page
311.
Note that with the #pragma data_alignment directive you can increase the
alignment demands on specific variables.

ALIGNMENT ON THE MSP430 MICROCONTROLLER

The MSP430 microcontroller can access memory using 8 or 16-bit accesses. However,
when a 16-bit access is performed, the data must be located at an even address. The
compiler ensures this by assigning an alignment to every data type, which means that
the MSP430 microcontroller can read the data.

Basic data types—integer types

The compiler supports both all Standard C basic data types and some additional types.

INTEGER TYPES—AN OVERVIEW

This table gives the size and range of each integer data type:
Data type Size Range Alignment
bool 8 bits 0 to 1 1
char 8 bits 0 to 255 1
signed char 8 bits -128 to 127 1
unsigned char 8 bits 0 to 255 1
signed short 16 bits -32768 to 32767 2
unsigned short 16 bits 0 to 65535 2
signed int 16 bits -32768 to 32767 2
unsigned int 16 bits 0 to 65535 2
signed long 32 bits -231 to 231-1 2
32-1
unsigned long 32 bits 0 to 2 2
signed long long 64 bits -263 to 263-1 2
64
unsigned long long 64 bits 0 to 2 -1 2
Table 33: Integer types

Signed variables are represented using the two’s complement form.

IAR C/C++ Compiler User Guide

304 for MSP430

AFE1_AFE2-1:1
 Data representation

BOOL
The bool data type is supported by default in the C++ language. If you have enabled
language extensions, the bool type can also be used in C source code if you include the
file stdbool.h. This will also enable the boolean values false and true.

THE LONG LONG TYPE

The long long data type is supported with one restriction:
The CLIB runtime library does not support the long long type.

THE ENUM TYPE

The compiler will use the smallest type required to hold enum constants, preferring
signed rather than unsigned.

When IAR Systems language extensions are enabled, and in C++, the enum constants
and types can also be of the type long, unsigned long, long long, or unsigned
long long.

To make the compiler use a larger type than it would automatically use, define an enum
constant with a large enough value. For example:
/* Disables usage of the char type for enum */
enum Cards{Spade1, Spade2,
DontUseChar=257};

THE CHAR TYPE

The char type is by default unsigned in the compiler, but the --char_is_signed
compiler option allows you to make it signed.
Note: The library is compiled with the char type as unsigned.

THE WCHAR_T TYPE

The wchar_t data type is an integer type whose range of values can represent distinct
codes for all members of the largest extended character set specified among the
supported locals.
The wchar_t data type is supported by default in the C++ language. To use the
wchar_t type also in C source code, you must include the file stddef.h from the
runtime library.
Note: The IAR CLIB Library has only rudimentary support for wchar_t.

305

AFE1_AFE2-1:1
Basic data types—integer types

BITFIELDS
In Standard C, int, signed int, and unsigned int can be used as the base type for
integer bitfields. In standard C++, and in C when language extensions are enabled in the
compiler, any integer or enumeration type can be used as the base type. It is
implementation defined whether a plain integer type (char, short, int, etc) results in
a signed or unsigned bitfield.
Bitfields in expressions will have the same data type as the integer base type.
In the IAR C/C++ Compiler for MSP430, plain integer types are treated as signed.
Bitfields in expressions are treated as int if int can represent all values of the bitfield.
Otherwise, they are treated as the bitfield base type.
Each bitfield is placed into a container of its base type from the least significant bit to
the most significant bit. If the last container is of the same type and has enough bits
available, the bitfield is placed into this container, otherwise a new container is
allocated. This allocation scheme is referred to as the disjoint type bitfield allocation.
If you use the directive #pragma bitfields=reversed, bitfields are placed from the
most significant bit to the least significant bit in each container. See bitfields, page 334.
Assume this example:
struct BitfieldExample
{
uint32_t a : 12;
uint16_t b : 3;
uint16_t c : 7;
uint8_t d;
};

The example in the disjoint types bitfield allocation strategy

To place the first bitfield, a, the compiler allocates a 32-bit container at offset 0 and puts
a into the least significant 12 bits of the container.

To place the second bitfield, b, a new container is allocated at offset 4, because the type
of the bitfield is not the same as that of the previous one. b is placed into the least
significant three bits of this container.
The third bitfield, c, has the same type as b and fits into the same container.
The fourth member, d, is allocated into the byte at offset 6. d cannot be placed into the
same container as b and c because it is not a bitfield, it is not of the same type, and it
would not fit.
When using reverse order, each bitfield is instead placed starting from the most
significant bit of its container.

IAR C/C++ Compiler User Guide

306 for MSP430

AFE1_AFE2-1:1
 Data representation

This is the layout of bitfield_example:

Basic data types—floating-point types

In the IAR C/C++ Compiler for MSP430, floating-point values are represented in
standard IEEE 754 format. The sizes for the different floating-point types are:
Type Size if double=32 Size if double=64
float 32 bits 32 bits
double 32 bits (default) 64 bits
long double 32 bits (default) 64 bits
Table 34: Floating-point types

The compiler does not support subnormal numbers. All operations that should produce
subnormal numbers will instead generate zero.

FLOATING-POINT ENVIRONMENT
Exception flags are not supported. The feraiseexcept function does not raise any
exceptions.

307

AFE1_AFE2-1:1
Basic data types—floating-point types

32-BIT FLOATING-POINT FORMAT

The representation of a 32-bit floating-point number as an integer is:

The exponent is 8 bits, and the mantissa is 23 bits.

The value of the number is:
(-1)S * 2(Exponent-127) * 1.Mantissa

The range of the number is at least:

±1.18E-38 to ±3.39E+38

The precision of the float operators (+, -, *, and /) is approximately 7 decimal digits.

64-BIT FLOATING-POINT FORMAT

The representation of a 64-bit floating-point number as an integer is:

The exponent is 11 bits, and the mantissa is 52 bits.

The value of the number is:
(-1)S * 2(Exponent-1023) * 1.Mantissa

The range of the number is at least:

±2.23E-308 to ±1.79E+308

The precision of the float operators (+, -, *, and /) is approximately 15 decimal digits.

REPRESENTATION OF SPECIAL FLOATING-POINT NUMBERS

This list describes the representation of special floating-point numbers:
● Zero is represented by zero mantissa and exponent. The sign bit signifies positive
or negative zero.
● Infinity is represented by setting the exponent to the highest value and the mantissa
to zero. The sign bit signifies positive or negative infinity.
● Not a number (NaN) is represented by setting the exponent to the highest positive
value and the mantissa to a non-zero value in the upper 16 bit word of the floating-
point value. The value of the sign bit is ignored.

IAR C/C++ Compiler User Guide

308 for MSP430

AFE1_AFE2-1:1
 Data representation

Note: This differs slightly from the standard IEEE754 representation and allows the
runtime library to be smaller and faster.
Note: The IAR CLIB Library does not fully support the special cases of floating-point
numbers, such as infinity, NaN. A library function which gets one of these special cases
of floating-point numbers as an argument might behave unexpectedly.

Pointer types
The compiler has two basic types of pointers: function pointers and data pointers.

FUNCTION POINTERS
For the MSP430 architecture and for the MSP430X architecture when using the Small
code model, function pointers are always 16 bits. For the MSP430X architecture when
using the Large code model, function pointers are 20 bits and they can address the entire
1 Mbyte of memory. See this table:
Architecture Data model Code model In register In memory
MSP430 — — One 16-bit register 2 bytes
MSP430X Any Small One 16-bit register 2 bytes
MSP430X Small Large Two 16-bit registers 4 bytes
MSP430X Medium/Large Large One 20-bit register 4 bytes
Table 35: Function pointers

Note: If ROPI is enabled, a normal function pointer holds the linked address of a
function. The actual address is only computed when the function is called. You can use
the function type attribute __no_pic to change this behavior, see __no_pic, page 326.

DATA POINTERS
These data pointers are available:
Keyword Pointer size Index type Address range In register In memory
__data16 16 bits signed int 0x0–0xFFFF One 16-bit register 2 bytes
__data20* 20 bits signed long 0x0–0xFFFFF One 20-bit register 4 bytes
Table 36: Data pointers

* The __data20 pointer type is not available for the MSP430X architecture when using
the Small data model nor for the MSP430 architecture.
Note: A data pointer always holds the actual address of an object, regardless of whether
ROPI is enabled or not.

309

AFE1_AFE2-1:1
Pointer types

CASTING
Casts between pointers have these characteristics:
● Casting a value of an integer type to a pointer of a smaller type is performed by
truncation
● Casting a value of an integer type to a pointer of a larger type is performed by zero
extension
● Casting a pointer type to a smaller integer type is performed by truncation
● Casting a pointer type to a larger integer type is performed by zero extension
● Casting a data pointer to a function pointer and vice versa is illegal
● Casting a function pointer to an integer type gives an undefined result
● Casting from a smaller pointer to a larger pointer is performed by zero extension
● Casting from a larger pointer to a smaller pointer is performed by truncation.

size_t
size_t is the unsigned integer type of the result of the sizeof operator. For the
MSP430 architecture, and for the MSP430X architecture in the Small and Medium data
models, the type used for size_t is unsigned int. In the Large data model, the type
used for size_t is unsigned long int.

ptrdiff_t
ptrdiff_t is the signed integer type of the result of subtracting two pointers. For the
MSP430 architecture, and for the MSP430X architecture in the Small and Medium data
models, the type used for ptrdiff_t is signed int. In the Large data model, the type
used for inptr_t is signed long int.
Note: It is sometimes possible to create an object that is so large that the result of
subtracting two pointers in that object is negative. See this example:
char buff[60000]; /* Assuming ptrdiff_t is a 16-bit */
char *p1 = buff; /* signed integer type. */
char *p2 = buff + 60000;
ptrdiff_t diff = p2 - p1;

intptr_t
intptr_t is a signed integer type large enough to contain a void *. For the MSP430
architecture, and for the MSP430X architecture in the Small and Medium data models,
the type used for inptr_t is signed int. In the Large data model, the type used for
inptr_t is signed long int.

IAR C/C++ Compiler User Guide

310 for MSP430

AFE1_AFE2-1:1
 Data representation

uintptr_t
uintptr_t is equivalent to intptr_t, with the exception that it is unsigned.

Structure types
The members of a struct are stored sequentially in the order in which they are
declared: the first member has the lowest memory address.

ALIGNMENT OF STRUCTURE TYPES

The struct and union types have the same alignment as the member with the highest
alignment requirement—this alignment requirement also applies to a member that is a
structure. To allow arrays of aligned structure objects, the size of a struct is adjusted
to an even multiple of the alignment.

GENERAL LAYOUT
Members of a struct are always allocated in the order specified in the declaration.
Each member is placed in the struct according to the specified alignment (offsets).
struct First
{
char c;
short s;
} s;

This diagram shows the layout in memory:

The alignment of the structure is 2 bytes, and a pad byte must be inserted to give
short s the correct alignment.

PACKED STRUCTURE TYPES

The #pragma pack directive is used for relaxing the alignment requirements of the
members of a structure. This changes the layout of the structure. The members are
placed in the same order as when declared, but there might be less pad space between
members.
Note: Accessing an object that is not correctly aligned requires code that is both larger
and slower. If such structure members are accessed many times, it is usually better to
construct the correct values in a struct that is not packed, and access this struct
instead.

311

AFE1_AFE2-1:1
Structure types

Special care is also needed when creating and using pointers to misaligned members.
For direct access to misaligned members in a packed struct, the compiler will emit the
correct (but slower and larger) code when needed. However, when a misaligned member
is accessed through a pointer to the member, the normal (smaller and faster) code is
used. In the general case, this will not work, because the normal code might depend on
the alignment being correct.
This example declares a packed structure:
#pragma pack(1)
struct S
{
char c;
short s;
};

#pragma pack()

The structure S has this memory layout:

The next example declares a new non-packed structure, S2, that contains the structure s
declared in the previous example:
struct S2
{
struct S s;
long l;
};

The structure S2 has this memory layout

The structure S will use the memory layout, size, and alignment described in the
previous example. The alignment of the member l is 2, which means that alignment of
the structure S2 will become 2.
For more information, see Alignment of elements in a structure, page 234.

IAR C/C++ Compiler User Guide

312 for MSP430

AFE1_AFE2-1:1
 Data representation

Type qualifiers
According to the C standard, volatile and const are type qualifiers.

DECLARING OBJECTS VOLATILE

By declaring an object volatile, the compiler is informed that the value of the object
can change beyond the compiler’s control. The compiler must also assume that any
accesses can have side effects—therefore all accesses to the volatile object must be
preserved.
There are three main reasons for declaring an object volatile:
● Shared access—the object is shared between several tasks in a multitasking
environment
● Trigger access—as for a memory-mapped SFR where the fact that an access occurs
has an effect
● Modified access—where the contents of the object can change in ways not known to
the compiler.

Definition of access to volatile objects

The C standard defines an abstract machine, which governs the behavior of accesses to
volatile declared objects. In general and in accordance to the abstract machine:

● The compiler considers each read and write access to an object declared volatile
as an access
● The unit for the access is either the entire object or, for accesses to an element in a
composite object—such as an array, struct, class, or union—the element. For
example:
char volatile a;
a = 5; /* A write access */
a += 6; /* First a read then a write access */
● An access to a bitfield is treated as an access to the underlying type
● Adding a const qualifier to a volatile object will make write accesses to the
object impossible. However, the object will be placed in RAM as specified by the C
standard.
However, these rules are not detailed enough to handle the hardware-related
requirements. The rules specific to the IAR C/C++ Compiler for MSP430 are described
below.

313

AFE1_AFE2-1:1
Type qualifiers

Rules for accesses

In the IAR C/C++ Compiler for MSP430, accesses to volatile declared objects are
subject to these rules:
● All accesses are preserved
● All accesses are complete, that is, the whole object is accessed
● All accesses are performed in the same order as given in the abstract machine
● All accesses are atomic, that is, they cannot be interrupted.
The compiler adheres to these rules for all 8-bit and 16-bit memory accesses. For
MSP430X also for all 20-bit memory accesses.
For larger types, all accesses are preserved but it is not guaranteed that all parts of the
object is accessed.
Note: For MSP430X, if the Large code model is used together with the Small data
model, function pointers are accessed as 32-bit data.

DECLARING OBJECTS VOLATILE AND CONST

If you declare a volatile object const, it will be write-protected but it will still be
stored in RAM memory as the C standard specifies.
To store the object in read-only memory instead, but still make it possible to access it as
a const volatile object, declare it with the __ro_placement attribute. See
__ro_placement, page 329.
To store the object in read-only memory instead, but still make it possible to access it as
a const volatile object, follow this example:
/* Header */
extern int const xVar;
#define x (*(int const volatile *) &xVar)

/* Source that uses x */

int DoSomething()
{
return x;
}

/* Source that defines x */

#pragma segment = "FLASH"
int const xVar @ "FLASH" = 6;

The segment FLASH contains the initializers. They must be flashed manually when the
application starts up.
Thereafter, the initializers can be reflashed with other values at any time.

IAR C/C++ Compiler User Guide

314 for MSP430

AFE1_AFE2-1:1
 Data representation

DECLARING OBJECTS CONST

The const type qualifier is used for indicating that a data object, accessed directly or
via a pointer, is non-writable. A pointer to const declared data can point to both
constant and non-constant objects. It is good programming practice to use const
declared pointers whenever possible because this improves the compiler’s possibilities
to optimize the generated code and reduces the risk of application failure due to
erroneously modified data.
Static and global objects declared const are allocated in ROM.
In C++, objects that require runtime initialization cannot be placed in ROM.

Data types in C++

In C++, all plain C data types are represented in the same way as described earlier in this
chapter. However, if any Embedded C++ features are used for a type, no assumptions
can be made concerning the data representation. This means, for example, that it is not
supported to write assembler code that accesses class members.

315

AFE1_AFE2-1:1
Data types in C++

IAR C/C++ Compiler User Guide

316 for MSP430

AFE1_AFE2-1:1
 Extended keywords
● General syntax rules for extended keywords

● Summary of extended keywords

● Descriptions of extended keywords

General syntax rules for extended keywords

The compiler provides a set of attributes that can be used on functions or data objects to
support specific features of the MSP430 microcontroller. There are two types of
attributes—type attributes and object attributes:
● Type attributes affect the external functionality of the data object or function
● Object attributes affect the internal functionality of the data object or function.
The syntax for the keywords differs slightly depending on whether it is a type attribute
or an object attribute, and whether it is applied to a data object or a function.
For more information about each attribute, see Descriptions of extended keywords, page
321. For information about how to use attributes to modify data, see the chapter Data
storage.
Note: The extended keywords are only available when language extensions are enabled
in the compiler.
In the IDE, language extensions are enabled by default.

Use the -e compiler option to enable language extensions. See -e, page 278.

TYPE ATTRIBUTES
Type attributes define how a function is called, or how a data object is accessed. This
means that if you use a type attribute, it must be specified both when a function or data
object is defined and when it is declared.
You can either place the type attributes explicitly in your declarations, or use the pragma
directive #pragma type_attribute.
Type attributes can be further divided into memory type attributes and general type
attributes. Memory type attributes are referred to as simply memory attributes in the rest
of the documentation.

317

AFE1_AFE2-1:1
General syntax rules for extended keywords

Memory attributes
A memory attribute corresponds to a certain logical or physical memory in the
microcontroller.
Available data memory attributes:
__regvar.

Data objects, functions, and destinations of pointers or C++ references always have a
memory attribute. If no attribute is explicitly specified in the declaration or by the
pragma directive #pragma type_attribute, an appropriate default attribute is
implicitly used by the compiler. You can specify one memory attribute for each level of
pointer indirection.

General type attributes

Available function type attributes (affect how the function should be called):
__interrupt, __monitor, __task, __no_pic, __cc_rom, __cc_version1,
__cc_version2

Available data type attributes:

const, volatile

You can specify as many type attributes as required for each level of pointer indirection.

Syntax for type attributes used on data objects

Type attributes use almost the same syntax rules as the type qualifiers const and
volatile. For example:
__data16 int i;
int __data16 j;

Both i and j are placed in data16 memory.

Unlike const and volatile, when a type attribute is used before the type specifier in
a derived type, the type attribute applies to the object, or typedef itself, except in
structure member declarations.

int __data16 * p; /* pointer to integer in data16 memory */

int * __data16 p; /* pointer in data16 memory */

__data16 int * p; /* pointer in data16 memory */

IAR C/C++ Compiler User Guide

318 for MSP430

AFE1_AFE2-1:1
 Extended keywords

In all cases, if a memory attribute is not specified, an appropriate default memory type
is used, which depends on the data model in use.
Using a type definition can sometimes make the code clearer:
typedef __data16 int d16_int;
d16_int *q1;

d16_int is a typedef for integers in data16 memory. The variable q1 can point to such
integers.
You can also use the #pragma type_attributes directive to specify type attributes
for a declaration. The type attributes specified in the pragma directive are applied to the
data object or typedef being declared.
#pragma type_attribute=__data16
int * q2;

The variable q2 is placed in data16 memory.

For more examples of using memory attributes, see More examples, page 64.

Syntax for type attributes used on functions

The syntax for using type attributes on functions differs slightly from the syntax of type
attributes on data objects. For functions, the attribute must be placed either in front of
the return type, or in parentheses, for example:
__interrupt void my_handler(void);

or
void (__interrupt my_handler)(void);

This declaration of my_handler is equivalent with the previous one:

#pragma type_attribute=__interrupt
void my_handler(void);

OBJECT ATTRIBUTES
Normally, object attributes affect the internal functionality of functions and data objects,
but not directly how the function is called or how the data is accessed. This means that
an object attribute does not normally need to be present in the declaration of an object.
Any exceptions to this rule are noted in the description of the attribute.
These object attributes are available:
● Object attributes that can be used for variables:
__no_alloc, __no_alloc16, __no_alloc_str, __no_alloc_str16,
__no_init, __persistent, __ro_placement

319

AFE1_AFE2-1:1
Summary of extended keywords

● Object attributes that can be used for functions and variables:

location, @, __root
● Object attributes that can be used for functions:
__intrinsic, __noreturn, __ramfunc, __raw, __save_reg20, vector

You can specify as many object attributes as required for a specific function or data
object.
For more information about location and @, see Controlling data and function
placement in memory, page 236. For more information about vector, see vector, page
354.

Syntax for object attributes

The object attribute must be placed in front of the type. For example, to place myarray
in memory that is not initialized at startup:
__no_init int myarray[10];

The #pragma object_attribute directive can also be used. This declaration is

equivalent to the previous one:
#pragma object_attribute=__no_init
int myarray[10];

Note: Object attributes cannot be used in combination with the typedef keyword.

Summary of extended keywords

This table summarizes the extended keywords:
Extended keyword Description
__cc_rom Specifies the ROM calling convention
__cc_version1 Specifies the Version1 calling convention
__cc_version2 Specifies the Version2 calling convention
__data16 Controls the storage of data objects
__data20 Controls the storage of data objects
__interrupt Specifies interrupt functions
__intrinsic Reserved for compiler internal use only
__monitor Specifies atomic execution of a function
__no_alloc, Makes a constant available in the execution file
__no_alloc16
Table 37: Extended keywords summary

IAR C/C++ Compiler User Guide

320 for MSP430

AFE1_AFE2-1:1
 Extended keywords

Extended keyword Description

__no_alloc_str, Makes a string literal available in the execution file
__no_alloc_str16
__no_init Places a data object in non-volatile memory
__no_multiplier Suppresses generation of code that directly accesses the hardware
multiplier
__no_pic Controls how functions are called
__noreturn Informs the compiler that the function will not return
__persistent Ensures that a variable is only initialized, for example, by a code
downloader, and not by cstartup.
__ramfunc Makes a function execute in RAM
__raw Prevents saving used registers in interrupt functions
__regvar Permanently places a variable in a specified register
__root Ensures that a function or variable is included in the object code
even if unused
__ro_placement Places const volatile data in read-only memory.
__save_reg20 Saves and restores all 20 bits in 20-bit registers
__task Relaxes the rules for preserving registers
Table 37: Extended keywords summary (Continued)

Descriptions of extended keywords

This section gives detailed information about each extended keyword.

__cc_rom
Syntax See Syntax for type attributes used on functions, page 319.

Description The __cc_rom keyword makes a function use the ROM calling convention instead of
the default calling convention.

Example __cc_rom int func(int arg1, int arg2);

See also The ROM calling convention, page 183

321

AFE1_AFE2-1:1
Descriptions of extended keywords

__cc_version1
Syntax See Syntax for type attributes used on functions, page 319.

Description The __cc_version1 keyword is available for backward compatibility of the interface
for calling assembler routines from C. It makes a function use the calling convention of
the IAR C/C++ Compiler for MSP430 version 1.x–3.x instead of the default calling
convention.

Example __cc_version1 int func(int arg1, double arg2);

See also Calling convention, page 181.

__cc_version2
Syntax See Syntax for type attributes used on functions, page 319.

Description The __cc_version2 keyword sets the default calling convention of the interface for
calling assembler routines from C. It makes a function use the calling convention of the
IAR C/C++ Compiler for MSP430 version 4.x and later.

Example __cc_version2 int func(int arg1, double arg2);

See also Calling convention, page 181.

__data16
Syntax See Syntax for type attributes used on data objects, page 318.

Description The __data16 memory attribute overrides the default storage of variables and places
individual variables and constants in data16 memory, which is the entire 64 Kbytes of
memory in the MSP430 architecture and the lower 64 Kbytes in the MSP430X
architecture. You can also use the __data16 attribute to create a pointer explicitly
pointing to an object located in the data16 memory.

Storage information ● Address range: 0–0xFFFF (64 Kbytes)

● Maximum object size: 65535 bytes
● Pointer size: 2 bytes

Example __data16 int x;

IAR C/C++ Compiler User Guide

322 for MSP430

AFE1_AFE2-1:1
 Extended keywords

See also Memory types (MSP430X only), page 60.

__data20
Syntax See Syntax for type attributes used on data objects, page 318.

Description The __data20 memory attribute overrides the default storage of variables and places
individual variables and constants in data20 memory, which is the entire 1 Mbyte of
memory in the MSP430X architecture. You can also use the __data20 attribute to
create a pointer explicitly pointing to an object located in the data20 memory.
The __data20 attribute cannot be used in the Small data model.

Storage information ● Address range: 0–0xFFFFF (1 Mbyte)

● Maximum object size: 1 Mbyte
● Pointer size: 20 bits in register, 4 bytes in memory

Example __data20 int x;

See also Memory types (MSP430X only), page 60.

__interrupt
Syntax See Syntax for type attributes used on functions, page 319.

Description The __interrupt keyword specifies interrupt functions. To specify one or several
interrupt vectors, use the #pragma vector directive. The range of the interrupt vectors
depends on the device used. It is possible to define an interrupt function without a vector,
but then the compiler will not generate an entry in the interrupt vector table.
An interrupt function must have a void return type and cannot have any parameters.
The header file iodevice.h, where device corresponds to the selected device,
contains predefined names for the existing interrupt vectors.
To make sure that the interrupt handler executes as fast as possible, you should compile
it with -Ohs, or use #pragma optimize=speed if the module is compiled with another
optimization goal.

Example #pragma vector=0x14

__interrupt void my_interrupt_handler(void);

See also Interrupt functions, page 73, vector, page 354, and INTVEC, page 399.

323

AFE1_AFE2-1:1
Descriptions of extended keywords

__intrinsic
Description The __intrinsic keyword is reserved for compiler internal use only.

__monitor
Syntax See Syntax for type attributes used on functions, page 319.

Description The __monitor keyword causes interrupts to be disabled during execution of the
function. This allows atomic operations to be performed, such as operations on
semaphores that control access to resources by multiple processes. A function declared
with the __monitor keyword is equivalent to any other function in all other respects.

Example __monitor int get_lock(void);

See also Monitor functions, page 76. For information about related intrinsic functions, see
__disable_interrupt, page 361, __enable_interrupt, page 362, __get_interrupt_state,
page 362, and __set_interrupt_state, page 366, respectively.

__no_alloc, __no_alloc16
Syntax See Syntax for object attributes, page 320.

Description Use the __no_alloc or __no_alloc16 object attribute on a constant to make the
constant available in the executable file without occupying any space in the linked
application.
You cannot access the contents of such a constant from your application. You can take
its address, which is an integer offset to the segment of the constant. The type of the
offset is unsigned long when __no_alloc is used, and unsigned short when
__no_alloc16 is used.

Example __no_alloc const struct MyData my_data @ "XXX" = {...};

See also __no_alloc_str, __no_alloc_str16, page 325.

IAR C/C++ Compiler User Guide

324 for MSP430

AFE1_AFE2-1:1
 Extended keywords

__no_alloc_str, __no_alloc_str16
Syntax __no_alloc_str(string_literal @ segment)

and
__no_alloc_str16(string_literal @ segment)

where

string_literal The string literal that you want to make available in the
executable file.
segment The name of the segment to place the string literal in.

Description Use the __no_alloc_str or __no_alloc_str16 operators to make string literals

available in the executable file without occupying any space in the linked application.
The value of the expression is the offset of the string literal in the segment. For
__no_alloc_str, the type of the offset is unsigned long. For __no_alloc_str16,
the type of the offset is unsigned short.

Example #define MYSEG "YYY"

#define X(str) __no_alloc_str(str @ MYSEG)

extern void dbg_printf(unsigned long fmt, ...)

#define DBGPRINTF(fmt, ...) dbg_printf(X(fmt), __VA_ARGS__)

void
foo(int i, double d)
{
DBGPRINTF("The value of i is: %d, the value of d is: %f",i,d);
}

Depending on your debugger and the runtime support, this could produce trace output
on the host computer.
Note: There is no such runtime support in C-SPY, unless you use an external plugin
module.

See also __no_alloc, __no_alloc16, page 324.

325

AFE1_AFE2-1:1
Descriptions of extended keywords

__no_init
Syntax See Syntax for object attributes, page 320.

Description Use the __no_init keyword to place a data object in non-volatile memory. This means
that the initialization of the variable, for example at system startup, is suppressed.

Example __no_init int myarray[10];

See also Non-initialized variables, page 251.

__no_multiplier
Syntax See Syntax for type attributes used on functions, page 319.

Description The __no_multiplier keyword suppresses generation of code that directly accesses
the hardware multiplier. When using this keyword, the result is the same as when
compiling without the --multiplier command line option.
Note: The linker might still redirect function calls, including calls to internal runtime
library routines, to variants that use the hardware multiplier.

Example __no_multiplier int mul(int x, int y)

{
return x*y;
}

__no_pic
Syntax See Syntax for type attributes used on functions, page 319.

Description The __no_pic memory attribute allows position-independent code to call functions
that are not position-independent. The attribute can only be used on function pointers
and only when the --ropi option is used. Such function pointers are called with the
normal calling sequence instead of with the position-independent one.

Example int (__no_pic * fPtr)(int arg1, double arg2);

See also Assembler instructions used for calling functions, page 189 and Position-independent
code and read-only data, page 80.

IAR C/C++ Compiler User Guide

326 for MSP430

AFE1_AFE2-1:1
 Extended keywords

__noreturn
Syntax See Syntax for object attributes, page 320.

Description The __noreturn keyword can be used on a function to inform the compiler that the
function will not return. If you use this keyword on such functions, the compiler can
optimize more efficiently. Examples of functions that do not return are abort and exit.
Note: At optimization levels medium or high, the __noreturn keyword might cause
incorrect call stack debug information at any point where it can be determined that the
current function cannot return.

Example __noreturn void terminate(void);

__persistent
Syntax See Syntax for object attributes, page 320.

Description Global or static variables defined with the __persistent attribute will not be
initialized by cstartup, but only by a code downloader or similar add-on functionality.
This attribute cannot be used together with any of the keywords const or __no_init,
and __persistent data cannot be located to an absolute address (using the @
operator).

Example __persistent int x = 0;

See also DATA16_P, page 394.

__ramfunc
Syntax See Syntax for object attributes, page 320.

Description The __ramfunc keyword makes a function execute in RAM. Two code segments will
be created: one for the RAM execution, and one for the ROM initialization.
Functions declared __ramfunc are by default stored in the CODE_I segment.
This attribute cannot be used if you have specified the --ropi option.

Example __ramfunc int FlashPage(char * data, char * page);

See also Execution in RAM, page 79.

327

AFE1_AFE2-1:1
Descriptions of extended keywords

__raw
Syntax See Syntax for object attributes, page 320.

Description This keyword prevents saving used registers in interrupt functions.

Example __raw __interrupt void my_interrupt_function()

__regvar
Syntax See Syntax for type attributes used on functions, page 319.

Description This keyword is used for declaring that a global or static variable should be placed
permanently in the specified register. The registers R4–R5 can be used for this purpose,
provided that they have been reserved with one of the --regvar_r4 or --regvar_r5
compiler options.
The __regvar attribute can be used on integer types, pointers, 32-bit floating-point
numbers, structures with one element and unions of all these. However, it is not possible
to point to an object that has been declared __regvar. An object declared __regvar
cannot have an initial value.
Note: If a module in your application has been compiled using --regvar_r4, it can
only be linked with modules that have been compiled with either --regvar_r4 or
--lock_r4. The same is true for --regvar_r5/--lock_r5.

Example To declare a global register variable, use the following syntax:

__regvar __no_init type variable_name @ location

where location is either __R4 or __R5, declared in intrinsics.h.

This will create a variable called variable_name of type type, located in register R4
or R5, for example:
__regvar __no_init int counter @ __R4;

See also --regvar_r4, page 294 and --regvar_r5, page 295

__root
Syntax See Syntax for object attributes, page 320.

IAR C/C++ Compiler User Guide

328 for MSP430

AFE1_AFE2-1:1
 Extended keywords

Description A function or variable with the __root attribute is kept whether or not it is referenced
from the rest of the application, provided its module is included. Program modules are
always included and library modules are only included if needed.

Example __root int myarray[10];

See also For more information about modules, segments, and the link process, see the IAR Linker
and Library Tools Reference Guide.

__ro_placement
Syntax See Syntax for object attributes, page 320.
Unlike most object attributes, when --ropi is enabled the __ro_placement attribute
must be specified both when a data object is defined and when it is declared.

Description The __ro_placement attribute specifies that a data object should be placed in
read-only memory. There are two cases where you might want to use this object
attribute:
● Data objects declared const volatile are by default placed in read-write
memory. Use the __ro_placement object attribute to place the data object in
read-only memory instead.
● In C++, a data object declared const and that needs dynamic initialization is placed
in read-write memory and initialized at system startup. If you use the
__ro_placement object attribute, the compiler will give an error message if the
data object needs dynamic initialization.
You can only use the __ro_placement object attribute on const objects.
You can use the __ro_placement attribute with C++ objects if the compiler can
optimize the C++ dynamic initialization of the data objects into static initialization. This
is possible only for relatively simple constructors that have been defined in the header
files of the relevant class definitions, so that they are visible to the compiler. If the
compiler cannot find the constructor, or if the constructor is too complex, an error
message will be issued (Error[Go023]) and the compilation will fail.

Example __ro_placement const volatile int x = 10;

__save_reg20
Syntax See Syntax for object attributes, page 320.

329

AFE1_AFE2-1:1
Descriptions of extended keywords

Description When compiling for the MSP430X architecture in the Small data model, use this
keyword to save and restore all 20 bits of the registers that are used, instead of only 16
bits, which are saved and restored by normal functions. This keyword will make the
function save all registers and not only the ones used by the function to guarantee that
20-bit registers are not destroyed by subsequent calls.
This may be necessary if the function is called from assembler routines that use the
upper 4 bits of the 20-bit registers.
Note: The __save_reg20 keyword has only effect when compiling for the MSP430X
architecture.

Example __save_reg20 void myFunction(void);

See also Interrupt functions for the MSP430X architecture, page 75.

__task
Syntax See Syntax for type attributes used on functions, page 319.

Description This keyword allows functions to relax the rules for preserving registers. Typically, the
keyword is used on the start function for a task in an RTOS.
By default, functions save the contents of used preserved registers on the stack upon
entry, and restore them at exit. Functions that are declared __task do not save all
registers, and therefore require less stack space.
Because a function declared __task can corrupt registers that are needed by the calling
function, you should only use __task on functions that do not return or call such a
function from assembler code.
The function main can be declared __task, unless it is explicitly called from the
application. In real-time applications with more than one task, the root function of each
task can be declared __task.

Example __task void my_handler(void);

IAR C/C++ Compiler User Guide

330 for MSP430

AFE1_AFE2-1:1
 Pragma directives
● Summary of pragma directives

● Descriptions of pragma directives

Summary of pragma directives

The #pragma directive is defined by Standard C and is a mechanism for using
vendor-specific extensions in a controlled way to make sure that the source code is still
portable.
The pragma directives control the behavior of the compiler, for example how it allocates
memory for variables and functions, whether it allows extended keywords, and whether
it outputs warning messages.
The pragma directives are always enabled in the compiler.
This table lists the pragma directives of the compiler that can be used either with the
#pragma preprocessor directive or the _Pragma() preprocessor operator:

Pragma directive Description

basic_template_matching Makes a template function fully memory-attribute
aware.
bis_nmi_ie1 Allows non-maskable interrupt routines to enable
interrupts.
bitfields Controls the order of bitfield members.
calls Lists possible called functions for indirect calls.
call_graph_root Specifies that the function is a call graph root.
constseg Places constant variables in a named segment.
cstat_disable See the C-STAT® Static Analysis Guide.
cstat_enable See the C-STAT® Static Analysis Guide.
cstat_restore See the C-STAT® Static Analysis Guide.
cstat_suppress See the C-STAT® Static Analysis Guide.
data_alignment Gives a variable a higher (more strict) alignment.
dataseg Places variables in a named segment.
default_function_attributes Sets default type and object attributes for
declarations and definitions of functions.
Table 38: Pragma directives summary

331

AFE1_AFE2-1:1
Summary of pragma directives

Pragma directive Description

default_variable_attributes Sets default type and object attributes for
declarations and definitions of variables.
diag_default Changes the severity level of diagnostic messages.
diag_error Changes the severity level of diagnostic messages.
diag_remark Changes the severity level of diagnostic messages.
diag_suppress Suppresses diagnostic messages.
diag_warning Changes the severity level of diagnostic messages.
error Signals an error while parsing.
include_alias Specifies an alias for an include file.
inline Controls inlining of a function.
language Controls the IAR Systems language extensions.
location Specifies the absolute address of a variable, or places
groups of functions or variables in named segments.
message Prints a message.
no_epilogue Uses a local return sequence
object_attribute Adds object attributes to the declaration or
definition of a variable or function.
optimize Specifies the type and level of an optimization.
pack Specifies the alignment of structures and union
members.
__printf_args Verifies that a function with a printf-style format
string is called with the correct arguments.
public_equ Defines a public assembler label and gives it a value.
required Ensures that a symbol that is needed by another
symbol is included in the linked output.
rtmodel Adds a runtime model attribute to the module.
__scanf_args Verifies that a function with a scanf-style format
string is called with the correct arguments.
section This directive is an alias for #pragma segment.
segment Declares a segment name to be used by intrinsic
functions.
STDC CX_LIMITED_RANGE Specifies whether the compiler can use normal
complex mathematical formulas or not.
Table 38: Pragma directives summary (Continued)

IAR C/C++ Compiler User Guide

332 for MSP430

AFE1_AFE2-1:1
 Pragma directives

Pragma directive Description

STDC FENV_ACCESS Specifies whether your source code accesses the
floating-point environment or not.
STDC FP_CONTRACT Specifies whether the compiler is allowed to contract
floating-point expressions or not.
type_attribute Adds type attributes to a declaration or to
definitions.
unroll Unrolls loops.
vector Specifies the vector of an interrupt or trap function.
weak Makes a definition a weak definition, or creates a
weak alias for a function or a variable.
Table 38: Pragma directives summary (Continued)

Note: For portability reasons, see also Recognized pragma directives (6.10.6), page
421.

Descriptions of pragma directives

This section gives detailed information about each pragma directive.

basic_template_matching
Syntax #pragma basic_template_matching

Description Use this pragma directive in front of a template function declaration to make the
function fully memory-attribute aware, in the rare cases where this is useful. That
template function will then match the template without the modifications, see Templates
and data memory attributes, page 214.

Example // We assume that __data20 is the memory type of the default

// pointer.
#pragma basic_template_matching
template<typename T> void fun(T *);

void MyF()
{
fun((int __data16 *) 0); // T = int __data16
}

333

AFE1_AFE2-1:1
Descriptions of pragma directives

bis_nmi_ie1
Syntax #pragma bis_nmi_ie1=mask

Parameters
mask A constant expression

Description Use this pragma directive for changing the interrupt control bits in the register IE, within
an NMI service routine. A BIS.W #mask, IE1 instruction is generated immediately
before the RETI instruction at the end of the function, after any POP instructions.
The effect is that NMI interrupts cannot occur until after the BIS instruction. The
advantage of placing it at the end of the POP instructions is that less stack will be used
in the case of nested interrupts.

Example In the following example, the OFIE bit will be set as the last instruction before the RETI
instruction:
#pragma bis_nmi_ie1=OFIE
#pragma vector=NMI_VECTOR
__interrupt void myInterruptFunction(void)
{
...
}

bitfields
Syntax #pragma bitfields={reversed|default}

Parameters
reversed Bitfield members are placed from the most significant bit to
the least significant bit.
default Bitfield members are placed from the least significant bit to
the most significant bit.

Description Use this pragma directive to control the order of bitfield members.

IAR C/C++ Compiler User Guide

334 for MSP430

AFE1_AFE2-1:1
 Pragma directives

Example #pragma bitfields=reversed

/* Structure that uses reversed bitfields. */
struct S
{
unsigned char error : 1;
unsigned char size : 4;
unsigned short code : 10;
};
#pragma bitfields=default /* Restores to default setting. */

See also Bitfields, page 306.

calls
Syntax #pragma calls=function[, function...]

Parameters
function Any declared function

Description Use this pragma directive to list the functions that can be indirectly called in the
following statement. This information can be used for stack usage analysis in the linker.
Note: For an accurate result, you must list all possible called functions.

Example void Fun1(), Fun2();

void Caller(void (*fp)(void))

{
#pragma calls = Fun1, Fun2
(*fp)();
}

See also Stack usage analysis, page 91

call_graph_root
Syntax #pragma call_graph_root[=category]

Parameters
category A string that identifies an optional call graph root category

Description Use this pragma directive to specify that, for stack usage analysis purposes, the
immediately following function is a call graph root. You can also specify an optional

335

AFE1_AFE2-1:1
Descriptions of pragma directives

category. The compiler will usually automatically assign a call graph root category to
interrupt and task functions. If you use the #pragma call_graph_root directive on
such a function you will override the default category. You can specify any string as a
category.

Example #pragma call_graph_root="interrupt"

See also Stack usage analysis, page 91.

constseg
Syntax #pragma constseg=[__memoryattribute ]{SEGMENT_NAME|default}

Parameters
__memoryattribute An optional memory attribute denoting in what memory the
segment will be placed; if not specified, default memory is
used.
SEGMENT_NAME A user-defined segment name; cannot be a segment name
predefined for use by the compiler and linker.
default Uses the default segment for constants.

Description This legacy pragma directive is supported for backward compatibility reasons. It can be
used for placing constant variables in a named segment. The segment name cannot be a
segment name predefined for use by the compiler and linker. The setting remains active
until you turn it off again with the #pragma constseg=default directive.

Example #pragma constseg=__data20 MY_CONSTANTS

const int factorySettings[] = {42, 15, -128, 0};
#pragma constseg=default

data_alignment
Syntax #pragma data_alignment=expression

Parameters
expression A constant which must be a power of two (1, 2, 4, etc.).

Description Use this pragma directive to give the immediately following variable a higher (more
strict) alignment of the start address than it would otherwise have. This directive can be
used on variables with static and automatic storage duration.

IAR C/C++ Compiler User Guide

336 for MSP430

AFE1_AFE2-1:1
 Pragma directives

When you use this directive on variables with automatic storage duration, there is an
upper limit on the allowed alignment for each function, determined by the calling
convention used.
Note: Normally, the size of a variable is a multiple of its alignment. The
data_alignment directive only affects the alignment of the variable’s start address,
and not its size, and can therefore be used for creating situations where the size is not a
multiple of the alignment.
Note: To comply with the ISO C11 standard and later, it is recommended to use the
alignment specifier _Alignas for C code. To comply with the C++11 standard and later,
it is recommended to use the alignment specifier alignas for C++ code.

dataseg
Syntax #pragma dataseg=[__memoryattribute]{SEGMENT_NAME|default}

Parameters
__memoryattribute An optional memory attribute denoting in what memory the
segment will be placed; if not specified, default memory is
used.
SEGMENT_NAME A user-defined segment name; cannot be a segment name
predefined for use by the compiler and linker.
default Uses the default segment.

Description This legacy pragma directive is supported for backward compatibility reasons. It can be
used for placing variables in a named segment. The segment name cannot be a segment
name predefined for use by the compiler and linker. The variable will not be initialized
at startup, and can for this reason not have an initializer, which means it must be declared
__no_init. The setting remains active until you turn it off again with the #pragma
dataseg=default directive.

Example #pragma dataseg=__data16 MY_SEGMENT

__no_init char myBuffer[1000];
#pragma dataseg=default

default_function_attributes
Syntax #pragma default_function_attributes=[ attribute...]

where attribute can be:

type_attribute

337

AFE1_AFE2-1:1
Descriptions of pragma directives

object_attribute
@ segment_name

Parameters
type_attribute See Type attributes, page 317.
object_attribute See Object attributes, page 319.
@ segment_name See Data and function placement in segments, page 239.

Description Use this pragma directive to set default segment placement, type attributes, and object
attributes for function declarations and definitions. The default settings are only used for
declarations and definitions that do not specify type or object attributes or location in
some other way.
Specifying a default_function_attributes pragma directive with no attributes,
restores the initial state where no such defaults have been applied to function
declarations and definitions.

Example /* Place following functions in segment MYSEG" */

#pragma default_function_attributes = @ "MYSEG"
int fun1(int x) { return x + 1; }
int fun2(int x) { return x - 1;
/* Stop placing functions into MYSEG */
#pragma default_function_attributes =

has the same effect as:

int fun1(int x) @ "MYSEG" { return x + 1; }
int fun2(int x) @ "MYSEG" { return x - 1; }

See also location, page 344.

object_attribute, page 345.
type_attribute, page 352.

default_variable_attributes
Syntax #pragma default_variable_attributes=[ attribute...]

where attribute can be:

type_attribute
object_attribute
@ segment_name

IAR C/C++ Compiler User Guide

338 for MSP430

AFE1_AFE2-1:1
 Pragma directives

Parameters
type_attribute See Type attributes, page 317.
object_attributes See Object attributes, page 319.
@ segment_name See Data and function placement in segments, page 239.

Description Use this pragma directive to set default segment placement, type attributes, and object
attributes for declarations and definitions of variables with static storage duration. The
default settings are only used for declarations and definitions that do not specify type or
object attributes or location in some other way.
Specifying a default_variable_attributes pragma directive with no attributes
restores the initial state of no such defaults being applied to variables with static storage
duration.

Example /* Place following variables in segment MYSEG" */

#pragma default_variable_attributes = @ "MYSEG"
int var1 = 42;
int var2 = 17;
/* Stop placing variables into MYSEG */
#pragma default_variable_attributes =

has the same effect as:

int var1 @ "MYSEG" = 42;
int var2 @ "MYSEG" = 17;

See also location, page 344.

object_attribute, page 345.
type_attribute, page 352.

diag_default
Syntax #pragma diag_default=tag[,tag,...]

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

Description Use this pragma directive to change the severity level back to the default, or to the
severity level defined on the command line by any of the options --diag_error,
--diag_remark, --diag_suppress, or --diag_warnings, for the diagnostic

339

AFE1_AFE2-1:1
Descriptions of pragma directives

messages specified with the tags. This level remains in effect until changed by another
diagnostic-level pragma directive.

See also Diagnostics, page 259.

diag_error
Syntax #pragma diag_error=tag[,tag,...]

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

Description Use this pragma directive to change the severity level to error for the specified
diagnostics. This level remains in effect until changed by another diagnostic-level
pragma directive.

See also Diagnostics, page 259.

diag_remark
Syntax #pragma diag_remark=tag[,tag,...]

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

Description Use this pragma directive to change the severity level to remark for the specified
diagnostic messages. This level remains in effect until changed by another
diagnostic-level pragma directive.

See also Diagnostics, page 259.

diag_suppress
Syntax #pragma diag_suppress=tag[,tag,...]

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

IAR C/C++ Compiler User Guide

340 for MSP430

AFE1_AFE2-1:1
 Pragma directives

Description Use this pragma directive to suppress the specified diagnostic messages. This level
remains in effect until changed by another diagnostic-level pragma directive.

See also Diagnostics, page 259.

diag_warning
Syntax #pragma diag_warning=tag[,tag,...]

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

Description Use this pragma directive to change the severity level to warning for the specified
diagnostic messages. This level remains in effect until changed by another
diagnostic-level pragma directive.

See also Diagnostics, page 259.

error
Syntax #pragma error message

Parameters
message A string that represents the error message.

Description Use this pragma directive to cause an error message when it is parsed. This mechanism
is different from the preprocessor directive #error, because the #pragma error
directive can be included in a preprocessor macro using the _Pragma form of the
directive and only causes an error if the macro is used.

Example #if FOO_AVAILABLE

#define FOO ...
#else
#define FOO _Pragma("error\"Foo is not available\"")
#endif

If FOO_AVAILABLE is zero, an error will be signaled if the FOO macro is used in actual
source code.

341

AFE1_AFE2-1:1
Descriptions of pragma directives

include_alias
Syntax #pragma include_alias ("orig_header" , "subst_header")
#pragma include_alias (<orig_header> , <subst_header>)

Parameters
orig_header The name of a header file for which you want to create an
alias.
subst_header The alias for the original header file.

Description Use this pragma directive to provide an alias for a header file. This is useful for
substituting one header file with another, and for specifying an absolute path to a relative
file.
This pragma directive must appear before the corresponding #include directives and
subst_header must match its corresponding #include directive exactly.

Example #pragma include_alias (<stdio.h> , <C:\MyHeaders\stdio.h>)

#include <stdio.h>

This example will substitute the relative file stdio.h with a counterpart located
according to the specified path.

See also Include file search procedure, page 256.

inline
Syntax #pragma inline[=forced|=never]

Parameters
No parameter Has the same effect as the inline keyword.
forced Disables the compiler’s heuristics and forces inlining.
never Disables the compiler’s heuristics and makes sure that the
function will not be inlined.

Description Use #pragma inline to advise the compiler that the function defined immediately after
the directive should be inlined according to C++ inline semantics.
Specifying #pragma inline=forced will always inline the defined function. If the
compiler fails to inline the function for some reason, for example due to recursion, a
warning message is emitted.

IAR C/C++ Compiler User Guide

342 for MSP430

AFE1_AFE2-1:1
 Pragma directives

Inlining is normally performed only on the High optimization level. Specifying

#pragma inline=forced will enable inlining of the function also on the Medium
optimization level.

See also Inlining functions, page 81.

language
Syntax #pragma language={extended|default|save|restore}

Parameters
extended Enables the IAR Systems language extensions from the first
use of the pragma directive and onward.
default From the first use of the pragma directive and onward,
restores the settings for the IAR Systems language
extensions to whatever that was specified by compiler
options.
save|restore Saves and restores, respectively, the IAR Systems language
extensions setting around a piece of source code.
Each use of save must be followed by a matching restore
in the same file without any intervening #include directive.

Description Use this pragma directive to control the use of language extensions.

Example At the top of a file that needs to be compiled with IAR Systems extensions enabled:
#pragma language=extended
/* The rest of the file. */

Around a particular part of the source code that needs to be compiled with IAR Systems
extensions enabled, but where the state before the sequence cannot be assumed to be the
same as that specified by the compiler options in use:
#pragma language=save
#pragma language=extended
/* Part of source code. */
#pragma language=restore

See also -e, page 278 and --strict, page 299.

343

AFE1_AFE2-1:1
Descriptions of pragma directives

location
Syntax #pragma location={address|NAME}

Parameters
address The absolute address of the global or static variable for which
you want an absolute location.
NAME A user-defined segment name—cannot be a segment name
predefined for use by the compiler and linker.

Description Use this pragma directive to specify the location—the absolute address—of the global
or static variable whose declaration follows the pragma directive. The variable must be
declared either __no_init or const. Alternatively, the directive can take a string
specifying a segment for placing either a variable or a function whose declaration
follows the pragma directive. Do not place variables that would normally be in different
segments—for example, variables declared as __no_init and variables declared as
const—in the same named segment.

Example #pragma location=0x22E

__no_init volatile char PORT1; /* PORT1 is located at address
0x22E */

#pragma segment="MY_SEG"
#pragma location="MY_SEG"
__no_init char PORT2; /* PORT2 is located in segment MY_SEG */

/* A better way is to use a corresponding mechanism */

#define MY_SEG _Pragma("location=\"MY_SEG\"")
/* ... */
MY_SEG __no_init int i; /* i is placed in the MY_SEG segment */

See also Controlling data and function placement in memory, page 236 and Placing user-defined
segments, page 105.

message
Syntax #pragma message(message)

Parameters
message The message that you want to direct to the standard output
stream.

IAR C/C++ Compiler User Guide

344 for MSP430

AFE1_AFE2-1:1
 Pragma directives

Description Use this pragma directive to make the compiler print a message to the standard output
stream when the file is compiled.

Example #ifdef TESTING

#pragma message("Testing")
#endif

no_epilogue
Syntax #pragma no_epilogue

Description Use this pragma directive to use a local return sequence instead of a call to the library
routine ?EpilogueN. This pragma directive can be used when a function needs to exist
on its own as in for example a bootloader that needs to be independent of the libraries it
is replacing.

Example #pragma no_epilogue

void bootloader(void) @"BOOTSECTOR"
{...

object_attribute
Syntax #pragma object_attribute=object_attribute[ object_attribute...]

Parameters For information about object attributes that can be used with this pragma directive, see
Object attributes, page 319.

Description Use this pragma directive to add one or more IAR-specific object attributes to the
declaration or definition of a variable or function. Object attributes affect the actual
variable or function and not its type. When you define a variable or function, the union
of the object attributes from all declarations including the definition, is used.

Example #pragma object_attribute=__no_init

char bar;

is equivalent to:
__no_init char bar;

See also General syntax rules for extended keywords, page 317.

345

AFE1_AFE2-1:1
Descriptions of pragma directives

optimize
Syntax #pragma optimize=[goal][level][disable]

Parameters
goal Choose between:
size, optimizes for size

balanced, optimizes balanced between speed and size

speed, optimizes for speed.

no_size_constraints, optimizes for speed, but relaxes the

normal restrictions for code size expansion.
level Specifies the level of optimization—choose between none,
low, medium, or high.

disable Disables one or several optimizations (separated by spaces).

Choose from:
no_code_motion, disables code motion

no_crosscall, disables interprocedural cross call

no_crossjump, disables interprocedural cross jump

no_cse, disables common subexpression elimination

no_inline, disables function inlining

no_relaxed_fp, disables the language relaxation that

optimizes floating-point expressions more aggressively
no_tbaa, disables type-based alias analysis

no_unroll, disables loop unrolling

Description Use this pragma directive to decrease the optimization level, or to turn off some specific
optimizations. This pragma directive only affects the function that follows immediately
after the directive.
The parameters size, balanced, speed, and no_size_constraints only have
effect on the high optimization level and only one of them can be used as it is not
possible to optimize for speed and size at the same time. It is also not possible to use
preprocessor macros embedded in this pragma directive. Any such macro will not be
expanded by the preprocessor.

IAR C/C++ Compiler User Guide

346 for MSP430

AFE1_AFE2-1:1
 Pragma directives

Note: If you use the #pragma optimize directive to specify an optimization level that
is higher than the optimization level you specify using a compiler option, the pragma
directive is ignored.

Example #pragma optimize=speed

int SmallAndUsedOften()
{
/* Do something here. */
}

#pragma optimize=size
int BigAndSeldomUsed()
{
/* Do something here. */
}

See also Fine-tuning enabled transformations, page 243.

pack
Syntax #pragma pack(n)
#pragma pack()
#pragma pack({push|pop}[,name] [,n])

Parameters
n Sets an optional structure alignment—one of: 1, 2, 4, 8, or 16
Empty list Restores the structure alignment to default
push Sets a temporary structure alignment
pop Restores the structure alignment from a temporarily pushed
alignment
name An optional pushed or popped alignment label

Description Use this pragma directive to specify the maximum alignment of struct and union
members.
The #pragma pack directive affects declarations of structures following the pragma
directive to the next #pragma pack or the end of the compilation unit.
Note: This can result in significantly larger and slower code when accessing members
of the structure.

See also Structure types, page 311.

347

AFE1_AFE2-1:1
Descriptions of pragma directives

__printf_args
Syntax #pragma __printf_args

Description Use this pragma directive on a function with a printf-style format string. For any call to
that function, the compiler verifies that the argument to each conversion specifier, for
example %d, is syntactically correct.
You cannot use this pragma directive on functions that are members of an overload set
with more than one member.

Example #pragma __printf_args

int printf(char const *,...);

void PrintNumbers(unsigned short x)

{
printf("%d", x); /* Compiler checks that x is an integer */
}

public_equ
Syntax #pragma public_equ="symbol",value

Parameters
symbol The name of the assembler symbol to be defined (string).
value The value of the defined assembler symbol (integer constant
expression).

Description Use this pragma directive to define a public assembler label and give it a value.

Example #pragma public_equ="MY_SYMBOL",0x123456

See also --public_equ, page 294.

required
Syntax #pragma required=symbol

Parameters
symbol Any statically linked function or variable.

IAR C/C++ Compiler User Guide

348 for MSP430

AFE1_AFE2-1:1
 Pragma directives

Description Use this pragma directive to ensure that a symbol which is needed by a second symbol
is included in the linked output. The directive must be placed immediately before the
second symbol.
Use the directive if the requirement for a symbol is not otherwise visible in the
application, for example, if a variable is only referenced indirectly through the segment
it resides in.

Example const char copyright[] = "Copyright by me";

#pragma required=copyright
int main()
{
/* Do something here. */
}

Even if the copyright string is not used by the application, it will still be included by the
linker and available in the output.

See also Inline assembler, page 171

rtmodel
Syntax #pragma rtmodel="key","value"

Parameters
"key" A text string that specifies the runtime model attribute.
"value" A text string that specifies the value of the runtime model
attribute. Using the special value * is equivalent to not
defining the attribute at all.

Description Use this pragma directive to add a runtime model attribute to a module, which can be
used by the linker to check consistency between modules.
This pragma directive is useful for enforcing 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, or the special value *. It can, however, be useful to state
explicitly that the module can handle any runtime model.
A module can have several runtime model definitions.
Note: The predefined compiler runtime model attributes start with a double underscore.
To avoid confusion, this style must not be used in the user-defined attributes.

349

AFE1_AFE2-1:1
Descriptions of pragma directives

Example #pragma rtmodel="I2C","ENABLED"

The linker will generate an error if a module that contains this definition is linked with
a module that does not have the corresponding runtime model attributes defined.

__scanf_args
Syntax #pragma __scanf_args

Description Use this pragma directive on a function with a scanf-style format string. For any call to
that function, the compiler verifies that the argument to each conversion specifier, for
example %d, is syntactically correct.
You cannot use this pragma directive on functions that are members of an overload set
with more than one member.

Example #pragma __scanf_args

int scanf(char const *,...);

int GetNumber()
{
int nr;
scanf("%d", &nr); /* Compiler checks that
the argument is a
pointer to an integer */

return nr;
}

segment
Syntax #pragma segment="NAME" [__memoryattribute]

alias
#pragma section="NAME" [__memoryattribute] [align]

Parameters
NAME The name of the segment.
__memoryattribute An optional memory attribute identifying the memory the
segment will be placed in; if not specified, default memory is
used.

IAR C/C++ Compiler User Guide

350 for MSP430

AFE1_AFE2-1:1
 Pragma directives

align Specifies an alignment for the segment. The value must be a

constant integer expression to the power of two.

Description Use this pragma directive to define a segment name that can be used by the segment
operators __segment_begin, __segment_end, and __segment_size. All segment
declarations for a specific segment must have the same memory type attribute and
alignment.
The align and the__memoryattribute parameters are only relevant when used
together with the segment operators __segment_begin, __segment_end, and
__segment_size. If you consider using align on an individual variable to achieve a
higher alignment, you must instead use the #pragma data_alignment directive.
If an optional memory attribute is used, the return type of the segment operators
__segment_begin and __segment_end is:
void __memoryattribute *.

Note: To place variables or functions in a specific segment, use the #pragma

location directive or the @ operator.

Example #pragma segment="MYDATA16" __data16 4

See also Dedicated segment operators, page 201 and the chapters Linking overview and Linking
your application.

STDC CX_LIMITED_RANGE
Syntax #pragma STDC CX_LIMITED_RANGE {ON|OFF|DEFAULT}

Parameters
ON Normal complex mathematic formulas can be used.
OFF Normal complex mathematic formulas cannot be used.
DEFAULT Sets the default behavior, that is OFF.

Description Use this pragma directive to specify that the compiler can use the normal complex
mathematic formulas for * (multiplication), / (division), and abs.
Note: This directive is required by Standard C. The directive is recognized but has no
effect in the compiler.

351

AFE1_AFE2-1:1
Descriptions of pragma directives

STDC FENV_ACCESS
Syntax #pragma STDC FENV_ACCESS {ON|OFF|DEFAULT}

Parameters
ON Source code accesses the floating-point environment.
Note: This argument is not supported by the compiler.
OFF Source code does not access the floating-point environment.
DEFAULT Sets the default behavior, that is OFF.

Description Use this pragma directive to specify whether your source code accesses the
floating-point environment or not.
Note: This directive is required by Standard C.

STDC FP_CONTRACT
Syntax #pragma STDC FP_CONTRACT {ON|OFF|DEFAULT}

Parameters
ON The compiler is allowed to contract floating-point
expressions.
OFF The compiler is not allowed to contract floating-point
expressions.
Note: This argument is not supported by the compiler.
DEFAULT Sets the default behavior, that is ON.

Description Use this pragma directive to specify whether the compiler is allowed to contract
floating-point expressions or not. This directive is required by Standard C.

Example #pragma STDC FP_CONTRACT ON

type_attribute
Syntax #pragma type_attribute=type_attr[ type_attr...]

Parameters For information about type attributes that can be used with this pragma directive, see
Type attributes, page 317.

IAR C/C++ Compiler User Guide

352 for MSP430

AFE1_AFE2-1:1
 Pragma directives

Description Use this pragma directive to specify IAR-specific type attributes, which are not part of
Standard C. Note however, that a given type attribute might not be applicable to all kind
of objects.
This directive affects the declaration of the identifier, the next variable, or the next
function that follows immediately after the pragma directive.

Example In this example, an int object with the memory attribute __data16 is defined:
#pragma type_attribute=__data16
int x;

This declaration, which uses extended keywords, is equivalent:

__data16 int x;

See also The chapter Extended keywords.

unroll
Syntax #pragma unroll=n

Parameters
n The number of loop bodies in the unrolled loop, a constant
integer. #pragma unroll = 1 will prevent the unrolling of
a loop.

Description Use this pragma directive to specify that the loop following immediately after the
directive should be unrolled and that the unrolled loop should have n copies of the loop
body. The pragma directive can only be placed immediately before a for, do, or while
loop, whose number of iterations can be determined at compile time.
Normally, unrolling is most effective for relatively small loops. However, in some cases,
unrolling larger loops can be beneficial if it exposes opportunities for further
optimizations between the unrolled loop iterations, for example, common subexpression
elimination or dead code elimination.
The #pragma unroll directive can be used to force a loop to be unrolled if the
unrolling heuristics are not aggressive enough. The pragma directive can also be used to
reduce the aggressiveness of the unrolling heuristics.

Example #pragma unroll=4

for (i = 0; i < 64; ++i)
{
foo(i * k, (i + 1) * k);
}

353

AFE1_AFE2-1:1
Descriptions of pragma directives

See also Loop unrolling, page 244

vector
Syntax #pragma vector=vector1[, vector2, vector3, ...]

Parameters
vectorN The vector number(s) of an interrupt or trap function.

Description Use this pragma directive to specify the vector(s) of an interrupt or trap function whose
declaration follows the pragma directive. Note that several vectors can be defined for
each function.
This pragma directive cannot be used if you have specified the --ropi option.

Example #pragma vector=

__interrupt void my_handler(void);

weak
Syntax #pragma weak symbol1[=symbol2]

Parameters
symbol1 A function or variable with external linkage.
symbol2 A defined function or variable.

Description This pragma directive can be used in one of two ways:

● To make the definition of a function or variable with external linkage a weak
definition.
● To create a weak alias for another function or variable. You can make more than one
alias for the same function or variable.

Example To make the definition of foo a weak definition, write:

#pragma weak foo

To make NMI_Handler a weak alias for Default_Handler, write:

#pragma weak NMI_Handler=Default_Handler

If NMI_Handler is not defined elsewhere in the program, all references to

NMI_Handler will refer to Default_Handler.

IAR C/C++ Compiler User Guide

354 for MSP430

AFE1_AFE2-1:1
 Intrinsic functions
● Summary of intrinsic functions

● Descriptions of intrinsic functions

Summary of intrinsic functions

To use intrinsic functions in an application, include the header file intrinsics.h.
Note that the intrinsic function names start with double underscores, for example:
__disable_interrupt

This table summarizes the intrinsic functions:

Intrinsic function Description
__bcd_add_type Performs a binary coded decimal operation
__bic_SR_register Clears bits in the SR register
__bic_SR_register_on_exit Clears bits in the SR register when an
interrupt or monitor function returns
__bis_GIE_interrupt_state Sets the GIE bit of the processor status
register
__bis_SR_register Sets bits in the SR register
__bis_SR_register_on_exit Sets bits in the SR register when an interrupt
or monitor function returns
__code_distance Returns the distance between the code and
the position it was linked for
__data16_read_addr Reads data to a 20-bit SFR register
__data16_write_addr Writes data to a 20-bit SFR register
__data20_longjmp Like the standard function longjmp, but
allows the jump buffer to be placed in data20
memory
__data20_read_type Reads data which has a 20-bit address
__data20_setjmp Like the standard function setjmp, but
allows the jump buffer to be placed in data20
memory
__data20_write_type Writes data which has a 20-bit address
Table 39: Intrinsic functions summary

355

AFE1_AFE2-1:1
Summary of intrinsic functions

Intrinsic function Description

__delay_cycles Provides cycle-accurate delay functionality
__disable_interrupt Disables interrupts
__enable_interrupt Enables interrupts
__even_in_range Makes switch statements rely on the
specified value being even and within the
specified range
__get_interrupt_state Returns the interrupt state
__get_R4_register Returns the value of the R4 register
__get_R5_register Returns the value of the R5 register
__get_SP_register Returns the value of the stack pointer
__get_SR_register Returns the value of the SR register
__get_SR_register_on_exit Returns the value that the processor status
register will have when the current interrupt
or monitor function returns
__low_power_mode_n Enters a MSP430 low power mode
__low_power_mode_off_on_exit Turns off low power mode when a monitor
or interrupt function returns
__no_operation Inserts a NOP instruction
__op_code Inserts a constant into the instruction stream
__saturated_add_signed_type Performs a saturated addition
__saturated_add_unsigned_type Performs a saturated addition
__saturated_sub_signed_type Performs a saturated subtraction
__saturated_sub_unsigned_type Performs a saturated subtraction
__set_interrupt_state Restores the interrupt state
__set_R4_register Writes a specific value to the R4 register
__set_R5_register Writes a specific value to the R5 register
__set_SP_register Writes a specific value to the SP register
__swap_bytes Executes the SWPB instruction
Table 39: Intrinsic functions summary (Continued)

IAR C/C++ Compiler User Guide

356 for MSP430

AFE1_AFE2-1:1
 Intrinsic functions

Descriptions of intrinsic functions

This section gives reference information about each intrinsic function.

__bcd_add_type
Syntax unsigned type __bcd_add_type(unsigned type x, unsigned type y);

where:

type Can be one of the types short, long, or long long

Description Performs a binary coded decimal addition. The parameters and the return value are
represented as binary coded decimal (BCD) numbers, that is when a hexadecimal
number (0x19) is used for representing the decimal number 19. The following functions
are supported:
Function Return value
__bcd_add_short Returns the sum of the two short parameters. The
parameters and the return value are represented as four-digit
BCD numbers.
__bcd_add_long Returns the sum of the two long parameters. The parameters
and the return value are represented as eight-digit BCD
numbers.
__bcd_add_long_long Returns the sum of the two long long parameters. The
parameters and the return value are represented as
sixteen-digit BCD numbers.
Table 40: Functions for binary coded decimal operations

Example /* c = 0x19 */
c = __bcd_add_short(c, 0x01);
/* c = 0x20 */

__bic_SR_register
Syntax void __bic_SR_register(unsigned short);

Description Clears bits in the processor status register. The function takes an integer as its argument,
that is, a bit mask with the bits to be cleared.

357

AFE1_AFE2-1:1
Descriptions of intrinsic functions

__bic_SR_register_on_exit
Syntax void __bic_SR_register_on_exit(unsigned short);

Description Clears bits in the processor status register when an interrupt or monitor function returns.
The function takes an integer as its argument, that is, a bit mask with the bits to be
cleared.
This intrinsic function is only available in interrupt and monitor functions.

__bis_GIE_interrupt_state
Syntax void __bis_GIE_interrupt_state(__istate_t)

Description Sets the GIE bit of the processor status register, if set in the state.

Example __istate_t state = __get_interrupt_state();

__disable_interrupt();
...
__bis_GIE_interrupt_state(state);

__bis_SR_register
Syntax void __bis_SR_register(unsigned short);

Description Sets bits in the status register. The function takes an integer literal as its argument, that
is, a bit mask with the bits to be set.

__bis_SR_register_on_exit
Syntax void __bis_SR_register_on_exit(unsigned short);

Description Sets bits in the processor status register when an interrupt or monitor function returns.
The function takes an integer literal as its argument, that is, a bit mask with the bits to
be set.
This intrinsic function is only available in interrupt and monitor functions.

__code_distance
Syntax long __code_distance(void);

IAR C/C++ Compiler User Guide

358 for MSP430

AFE1_AFE2-1:1
 Intrinsic functions

Description Returns the number of bytes between the placement of code in memory and the position
it was linked for. For non-position-independent code, the function returns 0.
The actual start address of a position-independent segment MY_SEG is
(char *) __segment_begin("MY_SEG") + __code_distance().

See also Position-independent code and read-only data, page 80 and Dedicated segment
operators, page 201

__data16_read_addr
Syntax unsigned long __data16_read_addr(unsigned short address);

where:

address Specifies the address for the read operation

Description Reads data from a 20-bit SFR register located at the given 16-bit address. This intrinsic
function is only useful on devices based on the MSP430X architecture.
In the Small data model, and if interrupts are not configured to save all 20 bits of the
registers they are using, interrupts must be disabled when you use this intrinsic function.

__data16_write_addr
Syntax void __data16_write_addr(unsigned short address,
unsigned long data);

where:

address Specifies the address for the write operation

data The data to be written

Description Writes a value to a 20-bit SFR register located at the given 16-bit address. This intrinsic
function is only useful on devices based on the MSP430X architecture.
In the Small data model, and if interrupts are not configured to save all 20 bits of the
registers they are using, interrupts must be disabled when you use this intrinsic function.

359

AFE1_AFE2-1:1
Descriptions of intrinsic functions

__data20_longjmp
Syntax void __data20_longjmp(__JMP_BUF_ELEMENT_TYPE__ __data20 *, int);

Description Like the standard function longjmp, but allows you to place the jump buffer in data20
memory.

__data20_read_type
Syntax unsigned type __data20_read_type(unsigned long address);

where:

address Specifies the address for the read operation

type Can be one of the types char, short, or long

Description Reads data from the MSP430X full 1-Mbyte memory area. This intrinsic function is
intended to be used in the Small data model. In the Medium and Large data models it is
recommended to use __data20 variables and pointers.
The following functions are supported:
Function Operation size Alignment
unsigned char __data20_read_char 1 byte 1
unsigned short __data20_read_short 2 bytes 2
unsigned long __data20_read_long 4 bytes 2
Table 41: Functions for reading data that has a 20-bit address

Note: In the Small data model, and if interrupts are not configured to save all 20 bits of
the registers they are using, interrupts must be disabled when you use this intrinsic
function.

__data20_setjmp
Syntax int __data20_setjmp(__JMP_BUF_ELEMENT_TYPE__ __data20 *);

Description Like the standard function setjmp, but allows the jump buffer to be placed in data20
memory.

IAR C/C++ Compiler User Guide

360 for MSP430

AFE1_AFE2-1:1
 Intrinsic functions

__data20_write_type
Syntax void __data20_write_type(unsigned long address, unsigned type);

where:

address Specifies the address for the write operation

type Can be one of the types char, short, or long

Description Writes data to the MSP430X full 1-Mbyte memory area. This intrinsic function is
intended to be used in the Small data model. In the Medium and Large data models it is
recommended to use __data20 variables and pointers.
The following functions are supported:
Function Operation size Alignment
unsigned char __data20_write_char 1 byte 1
unsigned short __data20_write_short 2 bytes 2
unsigned long __data20_write_long 4 bytes 2
Table 42: Functions for writing data that has a 20-bit address

Note: In the Small data model, and if interrupts are not configured to save all 20 bits of
the registers they are using, interrupts must be disabled when you use this intrinsic
function.

__delay_cycles
Syntax void __delay_cycles(unsigned long cycles);

Parameters
cycles The time delay in number of cycles. This must be a constant.

Description Inserts assembler instructions that delay the execution the number of specified clock
cycles, with a minimum of code.

__disable_interrupt
Syntax void __disable_interrupt(void);

Description Disables interrupts by inserting the instruction.

361

AFE1_AFE2-1:1
Descriptions of intrinsic functions

__enable_interrupt
Syntax void __enable_interrupt(void);

Description Enables interrupts by inserting the instruction.

__even_in_range
Syntax unsigned short __even_in_range(unsigned short value,
unsigned short upper_limit);

Parameters
value The switch expression
upper_limit The last value in the allowed range

Description Instructs the compiler to rely on the specified value being even and within the specified
range. The code will be generated accordingly and will only work if the requirement is
fulfilled.
This intrinsic function can be used for achieving optimal code for switch statements
where you know that the only values possible are even values within a given range, for
example an interrupt service routine for an Interrupt Vector Generator interrupt.

Example switch (__even_in_range(TAIV, 10))

See also Interrupt Vector Generator interrupt functions, page 74.

__get_interrupt_state
Syntax __istate_t __get_interrupt_state(void);

Description Returns the global interrupt state. The return value can be used as an argument to the
__set_interrupt_state intrinsic function, which will restore the interrupt state.

IAR C/C++ Compiler User Guide

362 for MSP430

AFE1_AFE2-1:1
 Intrinsic functions

Example #include "intrinsics.h"

void CriticalFn()
{
__istate_t s = __get_interrupt_state();
__disable_interrupt();

/* Do something here. */

__set_interrupt_state(s);
}

The advantage of using this sequence of code compared to using

__disable_interrupt and __enable_interrupt is that the code in this example
will not enable any interrupts disabled before the call of __get_interrupt_state.

__get_R4_register
Syntax unsigned short __get_R4_register(void);

Description Returns the value of the R4 register. This intrinsic function is only available when the
register is locked.

See also --lock_r4, page 283.

__get_R5_register
Syntax unsigned short __get_R5_register(void);

Description Returns the value of the R5 register. This intrinsic function is only available when the
register is locked.

See also --lock_r5, page 283.

__get_SP_register
Syntax unsigned short __get_SP_register(void);

Description Returns the value of the stack pointer register SP.

363

AFE1_AFE2-1:1
Descriptions of intrinsic functions

__get_SR_register
Syntax unsigned short __get_SR_register(void);

Description Returns the value of the processor status register SR.

__get_SR_register_on_exit
Syntax unsigned short __get_SR_register_on_exit(void);

Description Returns the value that the processor status register SR will have when the current
interrupt or monitor function returns.
This intrinsic function is only available in interrupt and monitor functions.

__low_power_mode_n
Syntax void __low_power_mode_n(void);

Description Enters a MSP430 low power mode, where n can be one of 0–4. This also enables global
interrupts by setting the GIE bit in the status register.

__low_power_mode_off_on_exit
Syntax void __low_power_mode_off_on_exit(void);

Description Turns off the low power mode when a monitor or interrupt function returns. This
intrinsic function is only available in interrupt and monitor functions.

__no_operation
Syntax void __no_operation(void);

Description Inserts a NOP instruction.

__op_code
Syntax void __op_code(unsigned short);

IAR C/C++ Compiler User Guide

364 for MSP430

AFE1_AFE2-1:1
 Intrinsic functions

Description Emits the 16-bit value into the instruction stream for the current function by inserting a
DC16 constant.

__saturated_add_signed_type
Syntax __saturated_add_signed_type(signed type, signed type);

where type can be one of char, short, long, and long long

Description Performs a saturated addition. When the mathematical result is outside the range of the
destination type, the result is the smallest or largest value that the type can hold.

Example __saturated_add_signed_char(100, 100) returns 127

__saturated_add_unsigned_type
Syntax __saturated_add_unsigned_type(unsigned type, unsigned type);

where type can be one of char, short, long, and long long

Description Performs a saturated addition. When the mathematical result is outside the range of the
destination type, the result is the smallest or largest value that the type can hold.

Example __saturated_add_unsigned_char(200, 200) returns 255

__saturated_sub_signed_type
Syntax __saturated_sub_signed_type(signed type, signed type);

where type can be one of char, short, long, and long long

Description Performs a saturated subtraction. When the mathematical result is outside the range of
the destination type, the result is the smallest or largest value that the type can hold.

Example __saturated_sub_signed_char(100, 120) returns -20

__saturated_sub_signed_char(-100, 120) returns -128

__saturated_sub_unsigned_type
Syntax __saturated_sub_unsigned_type(unsigned type, unsigned type);

where type can be one of char, short, long, and long long

365

AFE1_AFE2-1:1
Descriptions of intrinsic functions

Description Performs a saturated subtraction. When the mathematical result is outside the range of
the destination type, the result is the smallest or largest value that the type can hold.

Example __saturated_sub_unsigned_char(200, 100) returns 100

__saturated_sub_unsigned_char(100, 200) returns 0

__set_interrupt_state
Syntax void __set_interrupt_state(__istate_t);

Description Restores the interrupt state to a value previously returned by the

__get_interrupt_state function.

The intrinsic function __set_interrupt_state() restores the entire status register.

This includes the Global Interrupt Enable (GIE) bit as well as the bits SCGx, OSC_OFF,
and CPU_OFF.
For information about the __istate_t type, see __get_interrupt_state, page 362.

See also __bis_GIE_interrupt_state, page 358

__set_R4_register
Syntax void __set_R4_register(unsigned short);

Description Writes a specific value to the R4 register. This intrinsic function is only available when
R4 is locked.

See also --lock_r4, page 283.

__set_R5_register
Syntax void __set_R5_register(unsigned short);

Description Writes a specific value to the R5 register. This intrinsic function is only available when
R5 is locked.

See also --lock_r5, page 283.

IAR C/C++ Compiler User Guide

366 for MSP430

AFE1_AFE2-1:1
 Intrinsic functions

__set_SP_register
Syntax void __set_SP_register(unsigned short);

Description Writes a specific value to the SP stack pointer register. A warning message is issued if
the compiler has used the stack in any way at the location where this intrinsic function
is used.

__swap_bytes
Syntax unsigned short __swap_bytes(unsigned short);

Description Inserts an SWPB instruction and returns the argument with the upper and lower parts
interchanged.

Example __swap_bytes(0x1234)

returns 0x3412.

367

AFE1_AFE2-1:1
Descriptions of intrinsic functions

IAR C/C++ Compiler User Guide

368 for MSP430

AFE1_AFE2-1:1
 The preprocessor
● Overview of the preprocessor

● Description of predefined preprocessor symbols

● Descriptions of miscellaneous preprocessor extensions

Overview of the preprocessor

The preprocessor of the IAR C/C++ Compiler for MSP430 adheres to Standard C. The
compiler also makes these preprocessor-related features available to you:
● Predefined preprocessor symbols
These symbols allow you to inspect the compile-time environment, for example, the
time and date of compilation. For more information, see Description of predefined
preprocessor symbols, page 370.
● User-defined preprocessor symbols defined using a compiler option
In addition to defining your own preprocessor symbols using the #define directive,
you can also use the option -D, see -D, page 271.
● Preprocessor extensions
There are several preprocessor extensions, for example, many pragma directives. For
more information, see the chapter Pragma directives. For information about other
extensions related to the preprocessor, see Descriptions of miscellaneous
preprocessor extensions, page 374.
● Preprocessor output
Use the option --preprocess to direct preprocessor output to a named file, see
--preprocess, page 293.
To specify a path for an include file, use forward slashes:
#include "mydirectory/myfile"

In source code, use forward slashes:

file = fopen("mydirectory/myfile","rt");

Note: Backslashes can also be used—use one in include file paths and two in source
code strings.

369

AFE1_AFE2-1:1
Description of predefined preprocessor symbols

Description of predefined preprocessor symbols

This section lists and describes the preprocessor symbols.

__BASE_FILE__
Description A string that identifies the name of the base source file (that is, not the header file), being
compiled.

See also __FILE__, page 371, and --no_path_in_file_macros, page 287.

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

__CODE_MODEL__
Description An integer that identifies the code model in use. The value reflects the setting of the
--code_model option and is defined to __CODE_MODEL_SMALL__ or
__CODE_MODEL_LARGE__. These symbolic names can be used when testing the
__CODE_MODEL__ symbol.

__CORE__
Description An integer that identifies the chip core in use. The value reflects the setting of the
--core option and is defined to __430__ for the MSP430 architecture and to
__430X__ for the MSP430X architecture. These symbolic names can be used when
testing the __CORE__ symbol.

__COUNTER__
Description A macro that expands to a new integer each time it is expanded, starting at zero (0) and
counting up.

__cplusplus
Description An integer which is defined when the compiler runs in any of the C++ modes, otherwise
it is undefined. When defined, its value is 199711L. This symbol can be used with

IAR C/C++ Compiler User Guide

370 for MSP430

AFE1_AFE2-1:1
 The preprocessor

#ifdef to detect whether the compiler accepts C++ code. It is particularly useful when
creating header files that are to be shared by C and C++ code.
This symbol is required by Standard C.

__DATA_MODEL__
Description An integer that identifies the data model in use. The value reflects the setting of the
--data_model option and is defined to __DATA_MODEL_SMALL__,
__DATA_MODEL_MEDIUM__, or __DATA_MODEL_LARGE__. These symbolic names can
be used when testing the __DATA_MODEL__ symbol.

__DATE__
Description A string that identifies the date of compilation, which is returned in the form "Mmm dd
yyyy", for example, "Oct 30 2018".

This symbol is required by Standard C.

__embedded_cplusplus
Description An integer which is defined to 1 when the compiler runs in any of the C++ modes,
otherwise the symbol is undefined. This symbol can be used with #ifdef to detect
whether the compiler accepts C++ code. It is particularly useful when creating header
files that are to be shared by C and C++ code.
This symbol is required by Standard C.

__FILE__
Description A string that identifies the name of the file being compiled, which can be both the base
source file and any included header file.
This symbol is required by Standard C.

See also __BASE_FILE__, page 370, and --no_path_in_file_macros, page 287.

371

AFE1_AFE2-1:1
Description of predefined preprocessor symbols

__func__
Description A predefined string identifier that is initialized with the name of the function in which
the symbol is used. This is useful for assertions and other trace utilities. The symbol
requires that language extensions are enabled.
This symbol is required by Standard C.

See also -e, page 278 and __PRETTY_FUNCTION__, page 373.

__FUNCTION__
Description A predefined string identifier that is initialized with the name of the function in which
the symbol is used, similar to char _FUNCTION_[]="main"; if used in main(). This
is useful for assertions and other trace utilities. The symbol requires that language
extensions are enabled.

See also -e, page 278 and __PRETTY_FUNCTION__, page 373.

__IAR_SYSTEMS_ICC__
Description An integer that identifies the IAR compiler platform. The current value is 8—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 compiled by a compiler from IAR Systems.

__ICC430__
Description An integer that is set to 1 when the code is compiled with the IAR C/C++ Compiler for
MSP430.

__LINE__
Description An integer that identifies the current source line number of the file being compiled,
which can be both the base source file and any included header file.
This symbol is required by Standard C.

__POSITION_INDEPENDENT_CODE__
Description An integer that is set to 1 when the code is compiled with the option --ropi.

IAR C/C++ Compiler User Guide

372 for MSP430

AFE1_AFE2-1:1
 The preprocessor

__PRETTY_FUNCTION__
Description A predefined string identifier that is initialized with the function name, including
parameter types and return type, of the function in which the symbol is used, for
example, "void func(char)". This symbol is useful for assertions and other trace
utilities. The symbol requires that language extensions are enabled.

See also -e, page 278 and__func__, page 372.

__REGISTER_MODEL__
Description An integer that equals one of the following: __REGISTER_MODEL_REG16__ (for
MSP430 and MSP430X in the Small data model) or __REGISTER_MODEL_REG20__
(for MSP430X in the Medium and Large data models).

__REGISTER_R4__
Description An integer that identifies the use of register R4. The value reflects the setting of the
--lock_r4 and --regvar_r4 options and is defined to __REGISTER_FREE__,
__REGISTER_LOCKED__, or __REGISTER_REGVAR__.

__REGISTER_R5__
Description An integer that identifies the use of register R5. The value reflects the setting of the
--lock_r5 and --regvar_r5 options and is defined to __REGISTER_FREE__,
__REGISTER_LOCKED__, or __REGISTER_REGVAR__.

__ROPI__
Description An integer that is set to 1 when the code is compiled with the option --ropi.

__STDC__
Description An integer that is set to 1, which means the compiler adheres to Standard C. This symbol
can be tested with #ifdef to detect whether the compiler in use adheres to Standard C.*
This symbol is required by Standard C.

373

AFE1_AFE2-1:1
Descriptions of miscellaneous preprocessor extensions

__STDC_VERSION__
Description An integer that identifies the version of the C standard in use. The symbol expands to
199901L,unless the --c89 compiler option is used in which case the symbol expands
to 199409L. This symbol does not apply in EC++ mode.
This symbol is required by Standard C.

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

__TIME__
Description A string that identifies the time of compilation in the form "hh:mm:ss".
This symbol is required by Standard C.

__TIMESTAMP__
Description A string constant that identifies the date and time of the last modification of the current
source file. The format of the string is the same as that used by the asctime standard
function (in other words, "Tue Sep 16 13:03:52 2014").

__VER__
Description An integer that identifies the version number of the IAR compiler in use. The value of
the number is calculated in this way: (100 * the major version number + the
minor version number). For example, for compiler version 3.34, 3 is the major
version number and 34 is the minor version number. Hence, the value of __VER__ is
334.

Descriptions of miscellaneous preprocessor extensions

This section gives reference information about the preprocessor extensions that are
available in addition to the predefined symbols, pragma directives, and Standard C
directives.

IAR C/C++ Compiler User Guide

374 for MSP430

AFE1_AFE2-1:1
 The preprocessor

NDEBUG
Description This preprocessor symbol determines whether any assert macros you have written in
your application shall be included or not in the built application.
If this symbol is not defined, all assert macros are evaluated. If the symbol is defined,
all assert macros are excluded from the compilation. In other words, if the symbol is:
● defined, the assert code will not be included
● not defined, the assert code will be included
This means that if you write any assert code and build your application, you should
define this symbol to exclude the assert code from the final application.
Note: The assert macro is defined in the assert.h standard include file.
In the IDE, the NDEBUG symbol is automatically defined if you build your application in
the Release build configuration.

See also __ReportAssert, page 145.

#warning message
Syntax #warning message

where message can be any string.

Description Use this preprocessor directive to produce messages. Typically, this is useful for
assertions and other trace utilities, similar to the way the Standard C #error directive
is used. This directive is not recognized when the --strict compiler option is used.

375

AFE1_AFE2-1:1
Descriptions of miscellaneous preprocessor extensions

IAR C/C++ Compiler User Guide

376 for MSP430

AFE1_AFE2-1:1
 C/C++ standard library
functions
● C/C++ standard library overview

● DLIB runtime environment—implementation details

● CLIB runtime environment—implementation details

For detailed reference information about the library functions, see the online
help system.

C/C++ standard library overview

The compiler comes with two different implementations of the C/C++ standard library:
The IAR DLIB Runtime Environment is a complete implementation of the C/C++
standard library, compliant with Standard C and C++. This library also supports
floating-point numbers in IEEE 754 format and it can be configured to include different
levels of support for locale, file descriptors, multibyte characters, etc.
The IAR CLIB Runtime Environment is a light-weight implementation of the C
standard library, which is not fully compliant with Standard C. Neither does it fully
support floating-point numbers in IEEE 754 format and it does not support C++. Note
that the legacy CLIB runtime environment is provided for backward compatibility and
should not be used for new application projects.
Note: the IEC 60559 format—also known as ISO/IEC/IEEE 60559—is the
floating-point standard that Standard C binds to. It is nearly identical to IEEE 754
format.
Note that different customization methods are normally needed for these two libraries.
For more information about customization, see the chapter The DLIB runtime
environment and The CLIB runtime environment, respectively.
For detailed information about the library functions, see the online documentation
supplied with the product. There is also keyword reference information for the DLIB
library functions. To obtain reference information for a function, select the function
name in the editor window and press F1.
For more information about library functions, see the chapter Implementation-defined
behavior for Standard C.

377

AFE1_AFE2-1:1
C/C++ standard library overview

HEADER FILES
Your application program gains access to library definitions through header files, which
it incorporates using the #include directive. The definitions are divided into several
different header files, each covering a particular functional area, letting you include just
those that are required.
It is essential to include the appropriate header file before making any reference to its
definitions. Failure to do so can cause the call to fail during execution, or generate error
or warning messages at compile time or link time.

LIBRARY OBJECT FILES

Most of the library definitions can be used without modification, that is, directly from
the library object files that are supplied with the product. For information about how to
choose a runtime library, see Basic project configuration, page 54. The linker will
include only those routines that are required—directly or indirectly—by your
application.
For information about how you can override library modules with your own versions,
see Overriding library modules, page 123.

ALTERNATIVE MORE ACCURATE LIBRARY FUNCTIONS

The default implementation of cos, sin, tan, and pow is designed to be fast and small.
As an alternative, there are versions designed to provide better accuracy. They are
named __iar_xxx_accuratef for float variants of the functions and
__iar_xxx_accuratel for long double variants of the functions, and where xxx is
cos, sin, etc.

To use any of these more accurate versions, use the -e linker option.

REENTRANCY
A function that can be simultaneously invoked in the main application and in any
number of interrupts is reentrant. A library function that uses statically allocated data is
therefore not reentrant.
Most parts of the DLIB runtime environment are reentrant, but the following functions
and parts are not reentrant because they need static data:
● Heap functions—malloc, free, realloc, calloc, etc. and the C++ operators
new and delete
● Locale functions—localeconv, setlocale
● Multibyte functions—mblen, mbrlen, mbrtowc, mbsrtowc, mbtowc, wcrtomb,
wcsrtomb, wctomb

IAR C/C++ Compiler User Guide

378 for MSP430

AFE1_AFE2-1:1
 C/C++ standard library functions

● Rand functions—rand, srand

● Time functions—asctime, localtime, gmtime, mktime
● The miscellaneous functions atexit, perror, strerror, strtok
● Functions that use files or the heap in some way. This includes scanf, sscanf,
getchar, getwchar, putchar, and putwchar. In addition, if you are using the
options --enable_multibyte and --dlib_config=Full, the printf and
sprintf functions (or any variants) can also use the heap.

For the CLIB library, the qsort function and functions that use files in some way are
non-reentrant. This includes printf, scanf, getchar, and putchar. However, the
functions sprintf and sscanf are reentrant.
Functions that can set errno are not reentrant, because an errno value resulting from
one of these functions can be destroyed by a subsequent use of the function before it is
read. This applies to math and string conversion functions, among others.
Remedies for this are:
● Do not use non-reentrant functions in interrupt service routines
● Guard calls to a non-reentrant function by a mutex, or a secure region, etc.

THE LONGJMP FUNCTION

A longjmp is in effect a jump to a previously defined setjmp. Any variable length
arrays or C++ objects residing on the stack during stack unwinding will not be
destroyed. This can lead to resource leaks or incorrect application behavior.

DLIB runtime environment—implementation details

The DLIB runtime environment provides most of the important C and C++ standard
library definitions that apply to embedded systems. These are of the following types:
● Adherence to a free-standing implementation of Standard C. The library supports
most of the hosted functionality, but you must implement some of its base
functionality. For additional information, see the chapter Implementation-defined
behavior for Standard C in this guide.
● Standard C library definitions, for user programs.
● C++ library definitions, for user programs.
● CSTARTUP, the module containing the start-up code, see the chapter The DLIB
runtime environment in this guide.
● Runtime support libraries; for example low-level floating-point routines.
● Intrinsic functions, allowing low-level use of MSP430 features. See the chapter
Intrinsic functions for more information.

379

AFE1_AFE2-1:1
DLIB runtime environment—implementation details

In addition, the DLIB runtime environment includes some added C functionality, see
Added C functionality, page 383.

C HEADER FILES
This section lists the C header files specific to the DLIB runtime environment. Header
files may additionally contain target-specific definitions; these are documented in the
chapter Using C.
This table lists the C header files:
Header file Usage
assert.h Enforcing assertions when functions execute
complex.h Computing common complex mathematical functions
ctype.h Classifying characters
errno.h Testing error codes reported by library functions
fenv.h Floating-point exception flags
float.h Testing floating-point type properties
inttypes.h Defining formatters for all types defined in stdint.h
iso646.h Using Amendment 1—iso646.h standard header
limits.h Testing integer type properties
locale.h Adapting to different cultural conventions
math.h Computing common mathematical functions
setjmp.h Executing non-local goto statements
signal.h Controlling various exceptional conditions
stdarg.h Accessing a varying number of arguments
stdbool.h Adds support for the bool data type in C.
stddef.h Defining several useful types and macros
stdint.h Providing integer characteristics
stdio.h Performing input and output
stdlib.h Performing a variety of operations
string.h Manipulating several kinds of strings
tgmath.h Type-generic mathematical functions
time.h Converting between various time and date formats
uchar.h Unicode functionality (IAR extension to Standard C)
wchar.h Support for wide characters
Table 43: Traditional Standard C header files—DLIB

IAR C/C++ Compiler User Guide

380 for MSP430

AFE1_AFE2-1:1
 C/C++ standard library functions

Header file Usage

wctype.h Classifying wide characters
Table 43: Traditional Standard C header files—DLIB (Continued)

C++ HEADER FILES

This section lists the C++ header files:
● The C++ library header files
The header files that constitute the Embedded C++ library.
● The C++ standard template library (STL) header files
The header files that constitute STL for the Extended Embedded C++ library.
● The C++ C header files
The C++ header files that provide the resources from the C library.

The C++ library header files

This table lists the header files that can be used in Embedded C++:
Header file Usage
complex Defining a class that supports complex arithmetic
fstream Defining several I/O stream classes that manipulate external files
iomanip Declaring several I/O stream manipulators that take an argument
ios Defining the class that serves as the base for many I/O streams classes
iosfwd Declaring several I/O stream classes before they are necessarily defined
iostream Declaring the I/O stream objects that manipulate the standard streams
istream Defining the class that performs extractions
new Declaring several functions that allocate and free storage
ostream Defining the class that performs insertions
sstream Defining several I/O stream classes that manipulate string containers
streambuf Defining classes that buffer I/O stream operations
string Defining a class that implements a string container
strstream Defining several I/O stream classes that manipulate in-memory character
sequences
Table 44: C++ header files

381

AFE1_AFE2-1:1
DLIB runtime environment—implementation details

The C++ standard template library (STL) header files

The following table lists the standard template library (STL) header files that can be
used in Extended Embedded C++:
Header file Description
algorithm Defines several common operations on sequences
deque A deque sequence container
functional Defines several function objects
hash_map A map associative container, based on a hash algorithm
hash_set A set associative container, based on a hash algorithm
iterator Defines common iterators, and operations on iterators
list A doubly-linked list sequence container
map A map associative container
memory Defines facilities for managing memory
numeric Performs generalized numeric operations on sequences
queue A queue sequence container
set A set associative container
slist A singly-linked list sequence container
stack A stack sequence container
utility Defines several utility components
vector A vector sequence container
Table 45: Standard template library header files

Using Standard C libraries in C++

The C++ library works in conjunction with some of the header files from the Standard
C library, sometimes with small alterations. The header files come in two forms—new
and traditional—for example, cassert and assert.h.
This table shows the new header files:
Header file Usage
cassert Enforcing assertions when functions execute
cctype Classifying characters
cerrno Testing error codes reported by library functions
cfloat Testing floating-point type properties
cinttypes Defining formatters for all types defined in stdint.h
Table 46: New Standard C header files—DLIB

IAR C/C++ Compiler User Guide

382 for MSP430

AFE1_AFE2-1:1
 C/C++ standard library functions

Header file Usage

climits Testing integer type properties
clocale Adapting to different cultural conventions
cmath Computing common mathematical functions
csetjmp Executing non-local goto statements
csignal Controlling various exceptional conditions
cstdarg Accessing a varying number of arguments
cstdbool Adds support for the bool data type in C.
cstddef Defining several useful types and macros
cstdint Providing integer characteristics
cstdio Performing input and output
cstdlib Performing a variety of operations
cstring Manipulating several kinds of strings
ctime Converting between various time and date formats
cwchar Support for wide characters
cwctype Classifying wide characters
Table 46: New Standard C header files—DLIB (Continued)

LIBRARY FUNCTIONS AS INTRINSIC FUNCTIONS

Certain C library functions will under some circumstances be handled as intrinsic
functions and will generate inline code instead of an ordinary function call, for example,
memcpy, memset, and strcat.

ADDED C FUNCTIONALITY
The DLIB runtime environment includes some added C functionality.
The following include files provide these features:
● fenv.h
● stdio.h
● stdlib.h
● string.h
● time.h

fenv.h
In fenv.h, trap handling support for floating-point numbers is defined with the
functions fegettrapenable and fegettrapdisable.

383

AFE1_AFE2-1:1
DLIB runtime environment—implementation details

stdio.h
These functions provide additional I/O functionality:

fdopen Opens a file based on a low-level file descriptor.

fileno Gets the low-level file descriptor from the file descriptor
(FILE*).
__gets Corresponds to fgets on stdin.
getw Gets a wchar_t character from stdin.
putw Puts a wchar_t character to stdout.
__ungetchar Corresponds to ungetc on stdout.
__write_array Corresponds to fwrite on stdout.

string.h
These are the additional functions defined in string.h:

strdup Duplicates a string on the heap.

strcasecmp Compares strings case-insensitive.
strncasecmp Compares strings case-insensitive and bounded.
strnlen Bounded string length.

time.h
There are two interfaces for using time_t and the associated functions time, ctime,
difftime, gmtime, localtime, and mktime:

● The 32-bit interface supports years from 1900 up to 2035 and uses a 32-bit integer
for time_t. The type and function have names like __time32_t, __time32, etc.
This variant is mainly available for backwards compatibility.
● The 64-bit interface supports years from -9999 up to 9999 and uses a signed
long long for time_t. The type and function have names like __time64_t,
__time64, etc.

In both interfaces, time_t starts at the year 1970.

The interfaces are defined in the system header file time.h.
An application can use either interface, and even mix them by explicitly using the 32-
or 64-bit variants. By default, the library and the header redirect time_t, time etc. to

IAR C/C++ Compiler User Guide

384 for MSP430

AFE1_AFE2-1:1
 C/C++ standard library functions

the 32-bit variants. However, to explicitly redirect them to their 64-bit variants, define
_DLIB_TIME_USES_64 in front of the inclusion of time.h or ctime.

See also, __time32, __time64, page 146.

clock_t is represented by a 32-bit integer type.

SYMBOLS USED INTERNALLY BY THE LIBRARY

The following symbols are used by the library, which means that they are visible in
library source files, etc:

__assignment_by_bitwise_copy_allowed

This symbol determines properties for class objects.

__code

This symbol is used as a memory attribute internally by the compiler, and might have
to be used as an argument in certain templates.
__constrange()

Determines the allowed range for a parameter to an intrinsic function and that the
parameter must be of type const.
__construction_by_bitwise_copy_allowed

This symbol determines properties for class objects.

__has_constructor, __has_destructor

These symbols determine properties for class objects and they function like the sizeof
operator. The symbols are true when a class, base class, or member (recursively) has a
user-defined constructor or destructor, respectively.
__memory_of

Determines the class memory. A class memory determines which memory a class
object can reside in. This symbol can only occur in class definitions as a class memory.

Note: The symbols are reserved and should only be used by the library.
Use the compiler option --predef_macros to determine the value for any predefined
symbols.

385

AFE1_AFE2-1:1
CLIB runtime environment—implementation details

CLIB runtime environment—implementation details

The CLIB runtime environment provides most of the important C standard library
definitions that apply to embedded systems. These are of the following types:
● Standard C library definitions available for user programs. These are documented in
this chapter.
● The system startup code—see the chapter The CLIB runtime environment in this
guide.
● Runtime support libraries, for example low-level floating-point routines.
● Intrinsic functions, allowing low-level use of MSP430 features—see the chapter
Intrinsic functions for more information.

LIBRARY DEFINITIONS SUMMARY

This table lists the C header files specific to the CLIB runtime environment:
Header file Description
assert.h Assertions
ctype.h* Character handling
errno.h Error return values
float.h Limits and sizes of floating-point types
iccbutl.h Low-level routines
limits.h Limits and sizes of integral types
math.h Mathematics
setjmp.h Non-local jumps
stdarg.h Variable arguments
stdbool.h Adds support for the bool data type in C
stddef.h Common definitions including size_t, NULL,
ptrdiff_t, and offsetof
stdio.h Input/output
stdlib.h General utilities
string.h String handling
Table 47: CLIB runtime environment header files

* The functions isxxx, toupper, and tolower declared in the header file ctype.h
evaluate their argument more than once. This is not according to the ISO/ANSI
standard.

IAR C/C++ Compiler User Guide

386 for MSP430

AFE1_AFE2-1:1
 Segment reference
● Summary of segments

● Descriptions of segments

For more information about placement of segments, see the chapter Linking
your application.

Summary of segments
The table below lists the segments that are available in the compiler:
Segment Description
BSLSIGNATURE Holds BSL configuration data recognized by the device.
CHECKSUM Holds the checksum generated by the linker.
CODE Holds the program code.
CODE_I Holds code declared __ramfunc.
CODE_ID Holds the code copied to CODE_I at startup.
CODE_PAD Holds padding NOP instructions between the CODE and MPU_B2
segments.
CODE16 Holds the program code in the Small code model.
CSTACK Holds the stack used by C or C++ programs.
CSTART Holds the startup code.
DATA16_AC Holds absolute located constant data that has the memory attribute
__data16.
DATA16_AN Holds absolute located __no_init data that has the memory
attribute __data16.
DATA16_C Holds constant data that has the memory attribute __data16.
DATA16_HEAP Holds the __data16 heap.
DATA16_I Holds static and global initialized variables that have the memory
attribute __data16.
DATA16_ID Holds initial values for static and global initialized variables in
DATA16_I.
Table 48: Segment summary

387

AFE1_AFE2-1:1
Summary of segments

Segment Description
DATA16_N Holds __no_init static and global variables that have the memory
attribute __data16.
DATA16_P Holds variables that are defined with the __persistent keyword and
that have the __data16 memory attribute.
DATA16_Z Holds zero-initialized static and global variables that have the memory
attribute __data16.
DATA20_AC Holds absolute located constant data that has the memory attribute
__data20.
DATA20_AN Holds absolute located __no_init data that has the
memory attribute __data20.
DATA20_C Holds constant data that has the memory attribute __data20.
DATA20_HEAP Holds the __data20 heap.
DATA20_I Holds static and global initialized variables that have the memory
attribute __data20.
DATA20_ID Holds initial values for static and global initialized variables in
DATA20_I.
DATA20_N Holds __no_init static and global variables that have the memory
attribute __data20.
DATA20_P Holds variables that are defined with the __persistent keyword and
that have the __data20 memory attribute.
DATA20_Z Holds zero-initialized static and global variables that have the memory
attribute __data20.
DIFUNCT Holds pointers to code, typically C++ constructors, that should be
executed by the system startup code before main is called.
INFO Holds data to be placed in the MSP430 information memory.
INFOA Holds data to be placed in bank A of the MSP430 information memory.
INFOB Holds data to be placed in bank B of the MSP430 information memory.
INFOC Holds data to be placed in bank C of the MSP430 information memory.
INFOD Holds data to be placed in bank D of the MSP430 information memory.
INTVEC Holds the interrupt vector.
IPE_B1 Defines the start of the IPE address range.
IPE_B2 Defines the end of the IPE address range.
IPECODE16 Holds code inside the IPE address range.
IPEDATA16_C Holds constant data inside the IPE address range.
Table 48: Segment summary (Continued)

IAR C/C++ Compiler User Guide

388 for MSP430

AFE1_AFE2-1:1
 Segment reference

Segment Description
IPEDATA16_N Holds writable __no_init data inside the IPE address range.
IPESIGNATURE Holds IPE configuration data recognized by the device.
ISR_CODE Holds interrupt functions when compiling for the MSP430X architecture.
JTAGSIGNATURE Holds JTAG configuration data recognized by the device.
MPU_B1 Defines the border between the first and second MPU ranges.
MPU_B2 Defines the border between the second and third MPU ranges.
REGVAR_AN Holds __regvar data.
RESET Holds the reset vector.
SIGNATURE Holds configuration data recognized by the device.
This segment is deprecated but kept for backward compatibility.
TLS16_I Holds thread-local static and global initialized variables used by the main
thread.
TLS16_ID Holds initial values for thread-local static and global variables in
TLS16_I.
Table 48: Segment summary (Continued)

Descriptions of segments
This section gives reference information about each segment.
The segments are placed in memory by the segment placement linker directives -Z and
-P, for sequential and packed placement, respectively. Some segments cannot use
packed placement, as their contents must be continuous. For information about these
directives, see Using the -Z command for sequential placement, page 103 and Using the
-P command for packed placement, page 103, respectively.
For each segment, the segment memory type is specified, which indicates in which type
of memory the segment should be placed. See Segment memory type, page 86.
For information about how to define segments in the linker configuration file, see
Linking your application, page 101.
For more information about the extended keywords mentioned here, see the chapter
Extended keywords.

BSLSIGNATURE
Description Holds BSL configuration data recognized by the device.

Segment memory type CONST

389

AFE1_AFE2-1:1
Descriptions of segments

Memory placement Device-specific, typically 0xFF84-0xFF87.

Access type Read-only

CHECKSUM
Description Holds the checksum bytes generated by the linker. This segment also holds the
__checksum symbol, unless it is explicitly defined elsewhere. Note that the size of this
segment is affected by the linker option -J.

Segment memory type

Memory placement This segment can be placed anywhere in ROM memory.

Access type Read-only

CODE
Description Holds program code, except the code for system initialization, unless the Small code
model is used (MSP430X only). For MSP430, this segment also holds interrupt code.

Segment memory type CODE

Memory placement MSP430: 0x0002–0xFFFD

MSP430X: 0x00002–0xFFFFE

Access type Read-only

CODE_I
Description Holds program code declared __ramfunc. This code will be executed in RAM. The
code is copied from CODE_ID during initialization.

Segment memory type DATA

Memory placement MSP430: 0x0002–0xFFFD

MSP430X: 0x00002–0xFFFFE

Access type Read-write

IAR C/C++ Compiler User Guide

390 for MSP430

AFE1_AFE2-1:1
 Segment reference

CODE_ID
Description This is the permanent storage of program code declared __ramfunc. This code will be
executed in RAM. The code is copied to CODE_I during initialization.

Segment memory type CODE

Memory placement MSP430: 0x0002–0xFFFD

MSP430X: 0x00002–0xFFFFD, 0x10040-0xFFFD

Access type Read-only

CODE_PAD
Description Holds padding NOP instructions between the CODE and MPU_B2 segments, to prevent the
instruction prefetch mechanism from violating MPU access restrictions.

Segment memory type CODE

Memory placement 0x0-0xFFFFF

Access type Read-only

CODE16
Description Holds program code, except the code for system initialization, in the Small code model
(MSP430X only).

Segment memory type CODE

Memory placement 0x00002-0x0FFFD

Access type Read-only

CSTACK
Description Holds the internal data stack.

Segment memory type DATA

391

AFE1_AFE2-1:1
Descriptions of segments

Memory placement 0x0002–0xFFFD (also for the MSP430X architecture)

Access type Read-write

See also Setting up stack memory, page 105.

CSTART
Description Holds the startup code.
This segment cannot be placed in memory by using the -P directive for packed
placement, because the contents must be continuous. Instead, when you define this
segment in the linker configuration file, the -Z directive must be used.

Segment memory type CODE

Memory placement 0x0002–0xFFFD

Access type Read-only

DATA16_AC
Description Holds absolute located constant data that has the memory attribute __data16.
Absolute located means being placed at an absolute location using the @ operator or the
#pragma location directive. Because the location is known, this segment does not
need to be specified in the linker configuration file.

DATA16_AN
Description Holds absolute located __no_init data that has the memory attribute __data16.
Absolute located means being placed at an absolute location using the @ operator or the
#pragma location directive. Because the location is known, this segment does not
need to be specified in the linker configuration file.

DATA16_C
Description Holds constant data that has the memory attribute __data16. This can include constant
variables, string and aggregate literals, etc.

Segment memory type CONST

IAR C/C++ Compiler User Guide

392 for MSP430

AFE1_AFE2-1:1
 Segment reference

Memory placement 0x0001-0xFFFD

Access type Read-only

DATA16_HEAP
Description Holds the heap used for dynamically allocated data that has the memory attribute
__data16, in other words data allocated by data16_malloc and data16_free, and in
C++, new and delete.

Segment memory type DATA

Memory placement 0x0002-0xFFFD

Access type Read-write

See also Setting up heap memory, page 106 and New and Delete operators, page 211.

DATA16_I
Description Holds static and global initialized variables that have the memory attribute __data16
and that are initialized by copying from the segment DATA16_ID at application startup.
This segment cannot be placed in memory by using the -P directive for packed
placement, because the contents must be continuous. Instead, when you define this
segment in the linker configuration file, the -Z directive must be used.

Segment memory type DATA

Memory placement 0x0001-0xFFFD

Access type Read-write

DATA16_ID
Description Holds initial values for static and global initialized variables that have the memory
attribute __data16. These values are copied from DATA16_ID to DATA16_I at
application startup.
This segment cannot be placed in memory by using the -P directive for packed
placement, because the contents must be continuous. Instead, when you define this
segment in the linker configuration file, the -Z directive must be used.

393

AFE1_AFE2-1:1
Descriptions of segments

Segment memory type CONST

Memory placement 0x0001-0FFFD

Access type Read-only

DATA16_N
Description Holds static and global __no_init variables that have the memory attribute __data16.

Segment memory type DATA

Memory placement 0x0001-0xFFFD

Access type Read-write

DATA16_P
Description Holds static and global variables that are defined with the __persistent keyword and
that have the __data16 memory attribute. These variables will only be initialized, for
example, by a code downloader, and not by cstartup.

Segment memory type CONST

Memory placement 0x0001-0xFFFD

Access type Read-write

See also

DATA16_Z
Description Holds zero-initialized static and global variables that have the memory attribute
__data16. The contents of this segment is declared by the system startup code.

This segment cannot be placed in memory by using the -P directive for packed
placement, because the contents must be continuous. Instead, when you define this
segment in the linker configuration file, the -Z directive must be used.

Segment memory type DATA

IAR C/C++ Compiler User Guide

394 for MSP430

AFE1_AFE2-1:1
 Segment reference

Memory placement 0x0001-0xFFFD

Access type Read-write

DATA20_AC
Description Holds absolute located constant data that has the memory attribute __data20.
Absolute located means being placed at an absolute location using the @ operator or the
#pragma location directive. Because the location is known, this segment does not
need to be specified in the linker configuration file.
Note: The compiler requires that no data is placed in the address range
0x10000-0x1003F.

DATA20_AN
Description Holds absolute located __no_init data that has the memory attribute __data20.
Absolute located means being placed at an absolute location using the @ operator or the
#pragma location directive. Because the location is known, this segment does not
need to be specified in the linker configuration file.
Note: The compiler requires that no data is placed in the address range
0x10000-0x1003F.

DATA20_C
Description Holds constant data that has the memory attribute __data20. This can include constant
variables, string and aggregate literals, etc.
This segment is only available if you are using MSP430X.

Segment memory type CONST

Memory placement 0x00001-0x0FFFE, 0x10040-0xFFFFE

Access type Read-only

395

AFE1_AFE2-1:1
Descriptions of segments

DATA20_HEAP
Description Holds the heap used for dynamically allocated data that has the memory attribute
__data20, in other words data allocated by data20_malloc and data20_free, and
in C++, new and delete.
This segment is only available if you are using MSP430X.

Segment memory type DATA

Memory placement 0x00001-0x0FFFE, 0x10040-0xFFFFE

Access type Read-write

See also Setting up heap memory, page 106 and New and Delete operators, page 211.

DATA20_I
Description Holds static and global initialized variables that have the memory attribute __data20
and that are initialized by copying from the segment DATA20_ID at application startup.
This segment cannot be placed in memory by using the -P directive for packed
placement, because the contents must be continuous. Instead, when you define this
segment in the linker configuration file, the -Z directive must be used.
This segment is only available if you are using MSP430X.

Segment memory type DATA

Memory placement 0x00001-0x0FFFE, 0x10040-0xFFFFE

Access type Read-write

DATA20_ID
Description Holds initial values for static and global variables that have the memory attribute
__data20. These values are copied from DATA20_ID to DATA20_I at application
startup.
This segment cannot be placed in memory by using the -P directive for packed
placement, because the contents must be continuous. Instead, when you define this
segment in the linker configuration file, the -Z directive must be used.
This segment is only available if you are using MSP430X.

IAR C/C++ Compiler User Guide

396 for MSP430

AFE1_AFE2-1:1
 Segment reference

Segment memory type CONST

Memory placement 0x00001-0x0FFFE, 0x10040-0xFFFFE

Access type Read-only

DATA20_N
Description Holds static and global __no_init variables that have the memory attribute
__data20.

This segment is only available if you are using MSP430X.

Segment memory type DATA

Memory placement 0x00001-0x0FFFE, 0x10040-0xFFFFE

Access type Read-write

DATA20_P
Description Holds static and global variables that are defined with the __persistent keyword and
that have the __data20 memory attribute. These variables will only be initialized, for
example, by a code downloader, and not by cstartup.
This segment is only available if you are using MSP430X.

Segment memory type CONST

Memory placement 0x00001-0x0FFFE, 0x10040-0xFFFFE

Access type Read-write

See also __persistent, page 327

DATA20_Z
Description Holds zero-initialized static and global variables that have the memory attribute
__data20. The contents of this segment is declared by the system startup code.

397

AFE1_AFE2-1:1
Descriptions of segments

This segment cannot be placed in memory by using the -P directive for packed
placement, because the contents must be continuous. Instead, when you define this
segment in the linker configuration file, the -Z directive must be used.
This segment is only available if you are using MSP430X.

Segment memory type DATA

Memory placement 0x00001-0x0FFFE, 0x10040-0xFFFFE

Access type Read-write

DIFUNCT
Description Holds the dynamic initialization vector used by C++.

Segment memory type CONST

Memory placement This segment must be placed in the first 64 Kbytes of memory.

Access type Read-only

INFO
Description Holds data to be placed in the MSP430 information memory. Note that the INFO
segment and the INFOA–INFOD segments overlap.

Segment memory type CONST

Memory placement Depends on the device.

Access type Read-only

INFOA
Description Holds data to be placed in bank A of the MSP430 information memory. Note that the
INFOA segment and the INFO segment overlap.

Segment memory type CONST

Memory placement Depends on the device.

IAR C/C++ Compiler User Guide

398 for MSP430

AFE1_AFE2-1:1
 Segment reference

Access type Read-only

INFOB
Description Holds data to be placed in bank B of the MSP430 information memory. Note that the
INFOB segment and the INFO segment overlap.

Segment memory type CONST

Memory placement Depends on the device.

Access type Read-only

INFOC
Description Holds data to be placed in bank C of the MSP430 information memory. Note that the
INFOC segment and the INFO segment overlap.

Segment memory type CONST

Memory placement Depends on the device.

Access type Read-only

INFOD
Description Holds data to be placed in bank D of the MSP430 information memory. Note that the
INFOD segment and the INFO segment overlap.

Segment memory type CONST

Memory placement Depends on the device.

Access type Read-only

INTVEC
Description Holds the interrupt vector table generated by the use of the __interrupt extended
keyword in combination with the #pragma vector directive.

399

AFE1_AFE2-1:1
Descriptions of segments

Segment memory type CODE

Memory placement This segment can be placed anywhere in memory.

Access type Read-only

IPE_B1
Description The start of this segment defines the start of the protected IPE address range. It holds the
IPE control struct which is read by the boot code to initialize the IPE.

Segment memory type CONST

Memory placement 0x0-0xFFFF

Access type Read-only

IPE_B2
Description The start of this segment defines the end of the protected IPE address range. It only
contains a zero-size code fragment that constrains the alignment of the IPE end address.

Segment memory type CONST

Memory placement 0x0-0xFFFF

Access type Not applicable

IPECODE16
Description Holds code inside the protected IPE address range. Code in this segment can be used for
reading data located inside the protected IPE address range.

Segment memory type CODE

Memory placement 0x0-0xFFFF, between IPE_B1 and IPE_B2

Access type Read-only

IAR C/C++ Compiler User Guide

400 for MSP430

AFE1_AFE2-1:1
 Segment reference

IPEDATA16_C
Description Holds constants inside the protected IPE address range. Data in this segment can only
be read by code located inside the protected IPE address range.

Segment memory type CONST

Memory placement 0x0-0xFFFF, between IPE_B1 and IPE_B2

Access type Read-only

IPEDATA16_N
Description Holds writable __no_init data inside the protected IPE address range. Data inside this
range can only be read or written by code located inside the protected IPE address range.

Segment memory type DATA

Memory placement 0x0-0xFFFF, between IPE_B1 and IPE_B2.

Access type Read-write

IPESIGNATURE
Description Holds IPE configuration data recognized by the device.

Segment memory type CONST

Memory placement Device-specific, typically 0xFF88-0xFF8F.

Access type Read-only

ISR_CODE
Description Holds interrupt functions when compiling for the MSP430X architecture. This segment
is not used when compiling for the MSP430 architecture.

Segment memory type CODE

Memory placement 0x0002–0xFFFD

401

AFE1_AFE2-1:1
Descriptions of segments

Access type Read-only

JTAGSIGNATURE
Description Holds JTAG configuration data recognized by the device.

Segment memory type CONST

Memory placement Device-specific, typically 0xFF80-0xFF83.

Access type Read-only

MPU_B1
Description The __iar_430_mpu_init function uses the start of this segment to define the border
between the first and second MPU address ranges. This segment only contains a
zero-size code fragment that constrains the alignment of the MPU border.

Segment memory type CONST

Memory placement 0x0-0xFFFFF

Access type Not applicable.

MPU_B2
Description The __iar_430_mpu_init function uses the start of this segment to define the border
between the second and third MPU address ranges. This segment only contains a
zero-size code fragment that constrains the alignment of the MPU border.

Segment memory type CONST

Memory placement 0x0-0xFFFFF

Access type Not applicable.

REGVAR_AN
Description Holds __regvar data.

IAR C/C++ Compiler User Guide

402 for MSP430

AFE1_AFE2-1:1
 Segment reference

Memory placement This segment is placed in the memory area reserved for registers, and does not occupy
space in the normal memory area.

RESET
Description Holds the reset vector.

Segment memory type CODE

Memory placement 0xFFFE–0xFFFF

Access type Read-only

SIGNATURE
Description Holds configuration data recognized by the device, such as the JTAG password and the
IPE signature.
Note: This segment is deprecated, but kept for backward compatibility.

Segment memory type CONST

Memory placement Device-specific, typically 0xFF80-0xFF8F

Access type Read-only

TLS16_I
Description Holds thread-local static and global initialized variables used by the main thread,
initialized by copying from the segment TLS16_ID at application startup.
This segment is only used by custom-built runtime libraries configured with thread
support.
This segment cannot be placed in memory by using the -P directive for packed
placement, because the content must be continuous. Instead, when you define this
segment in the linker configuration file, the -Z directive must be used.

Segment memory type DATA

Memory placement 0x0001–0xFFFD

403

AFE1_AFE2-1:1
Descriptions of segments

Access type Read-write

TLS16_ID
Description Holds initial values for thread-local static and global variables in the TLS16_I segment
for the main thread, and for each started thread. The main thread is initialized by the
startup code; all other threads are initialized by the embedded operating system.
This segment cannot be placed in memory by using the -P directive for packed
placement, because the content must be continuous. Instead, when you define this
segment in the linker configuration file, the -Z directive must be used.

Segment memory type CONST

Memory placement 0x0001–0xFFFD

Access type Read-only

IAR C/C++ Compiler User Guide

404 for MSP430

AFE1_AFE2-1:1
 The stack usage control file
● Overview

● Stack usage control directives

● Syntactic components

Before you read this chapter, see Stack usage analysis, page 91.

Overview
A stack usage control file consists of a sequence of directives that control stack usage
analysis. You can use C ("/*...*/") and C++ ("//...") comments in these files.
The default filename extension for stack usage control files is suc.

C++ NAMES
You can also use wildcards in function names. "#*" matches any sequence of characters,
and "#?" matches a single character.

Stack usage control directives

This section gives detailed reference information about each stack usage control
directive.

call graph root directive

Syntax call graph root [ category ] : func-spec [, func-spec... ];

Parameters
category See category, page 409
func-spec See func-spec, page 409

Description Specifies that the listed functions are call graph roots. You can optionally specify a call
graph root category. Call graph roots are listed under their category in the Stack Usage
chapter in the linker map file.

405

AFE1_AFE2-1:1
Stack usage control directives

The linker will normally issue a warning for functions needed in the application that are
not call graph roots and which do not appear to be called.

Example call graph root [task]: MyFunc10, MyFunc11;

See also call_graph_root, page 335.

check that directive

Syntax check that expression;

Parameters
expression A boolean expression.

Description You can use the check that directive to compare the results of stack usage analysis
against the sizes of blocks and regions. If the expression evaluates to zero, an error is
emitted.
Three extra operators are available for use only in check that expressions:

maxstack(category) The stack depth of the deepest call chain for any call
graph root function in the category.
totalstack(category) The sum of the stack depths of the deepest call chains
for each call graph root function in the category.
size("SEGMENT") The size of the segment.

Example check that maxstack("Program entry")

+ totalstack("interrupt")
+ 1K
<= size("CSTACK");

See also Stack usage analysis, page 91.

exclude directive
Syntax exclude func-spec [, func-spec... ];

Parameters
func-spec See func-spec, page 409

IAR C/C++ Compiler User Guide

406 for MSP430

AFE1_AFE2-1:1
 The stack usage control file

Description Excludes the specified functions, and call trees originating with them, from stack usage
calculations.

Example exclude MyFunc5, MyFunc6;

function directive
Syntax [ override ] function [ category ] func-spec : stack-size
[ , call-info... ];

Parameters
category See category, page 409
func-spec See func-spec, page 409
call-info See call-info, page 410
stack-size See stack-size, page 411

Description Specifies what the maximum stack usage is in a function and which other functions that
are called from that function.
Normally, an error is issued if there already is stack usage information for the function,
but if you start with override, the error will be suppressed and the information
supplied in the directive will be used instead of the previous information.

Example function MyFunc1: 32,

calls MyFunc2,
calls MyFunc3, MyFunc4: 16;

function [interrupt] MyInterruptHandler: 44;

max recursion depth directive

Syntax max recursion depth func-spec : size;

Parameters
func-spec See func-spec, page 409
size See size, page 411

Description Specifies the maximum number of iterations through any of the cycles in the recursion
nest of which the function is a member.

407

AFE1_AFE2-1:1
Stack usage control directives

A recursion nest is a set of cycles in the call graph where each cycle shares at least one
node with another cycle in the nest.
Stack usage analysis will base its result on the max recursion depth multiplied by the
stack usage of the deepest cycle in the nest. If the nest is not entered on a point along
one of the deepest cycles, no stack usage result will be calculated for such calls.

Example max recursion depth MyFunc12: 10;

no calls from directive

Syntax no calls from module-spec to func-spec [, func-spec... ];

Parameters
func-spec See func-spec, page 409
module-spec See module-spec, page 410

Description When you provide stack usage information for some functions in a module without
stack usage information, the linker warns about functions that are referenced from the
module but not listed as called. This is primarily to help avoid problems with C runtime
routines, calls to which are generated by the compiler, beyond user control.
If there actually is no call to some of these functions, use the no calls from directive
to selectively suppress the warning for the specified functions. You can also disable the
warning entirely (--diag_suppress or
Project>Options>Linker>Diagnostics>Suppress these diagnostics).

Example no calls from [file.r43] to MyFunc13, MyFun14;

possible calls directive

Syntax possible calls calling-func : called-func [ , called-func... ];

Parameters
calling-func See func-spec, page 409
called-func See func-spec, page 409

Description Specifies an exhaustive list of possible destinations for all indirect calls in one function.
Use this for functions which are known to perform indirect calls and where you know
exactly which functions that might be called in this particular application. Consider

IAR C/C++ Compiler User Guide

408 for MSP430

AFE1_AFE2-1:1
 The stack usage control file

using the #pragma calls directive if the information about which functions that might
be called is available when compiling.

Example possible calls MyFunc7: MyFunc8, MyFunc9;

When the function does not perform any calls, the list is empty:
possible calls MyFunc8: ;

See also calls, page 335.

Syntactic components
This section describes the syntactical components that can be used by the stack usage
control directives.

category
Syntax [ name ]

Description A call graph root category. You can use any name you like. Categories are not
case-sensitive.

Example category examples:

[interrupt]
[task]

func-spec
Syntax [ ? ] name [ module-spec ]

Description Specifies the name of a symbol, and for module-local symbols, the name of the module
it is defined in. Normally, if func-spec does not match a symbol in the program, a
warning is emitted. Prefixing with ? suppresses this warning.

Example func-spec examples:

xFun
MyFun [file.r43]

409

AFE1_AFE2-1:1
Syntactic components

module-spec
Syntax [name [ (name) ]]

Description Specifies the name of a module, and optionally, in parentheses, the name of the library
it belongs to. To distinguish between modules with the same name, you can specify:
● The complete path of the file ("D:\C1\test\file.o")
● As many path elements as are needed at the end of the path ("test\file.o")
● Some path elements at the start of the path, followed by "...", followed by some
path elements at the end ("D:\...\file.o").
Note: When using multi-file compilation (--mfc), multiple files are compiled into a
single module, named after the first file.

Example module-spec examples:

[file.r43]
[file.r43(lib.a)]
["D:\C1\test\file.r43"]

name
Description A name can be either an identifier or a quoted string.
The first character of an identifier must be either a letter or one of the characters "_",
"$", or ".". The rest of the characters can also be digits.
A quoted string starts and ends with " and can contain any character. Two consecutive
" characters can be used inside a quoted string to represent a single ".

Example name examples:

MyFun
file.r43
"file-1.r43"

call-info
Syntax calls func-spec [ , func-spec... ][ : stack-size ]

Description Specifies one or more called functions, and optionally, the stack size at the calls.

IAR C/C++ Compiler User Guide

410 for MSP430

AFE1_AFE2-1:1
 The stack usage control file

Example call-info examples:

calls MyFunc1 : stack 16

calls MyFunc2, MyFunc3, MyFunc4

stack-size
Syntax [ stack ] size
([ stack ] size)

Description Specifies the size of a stack frame. A stack may not be specified more than once.

Example 24
stack 28

size
Description A decimal integer, or 0x followed by a hexadecimal integer. Either alternative can
optionally be followed by a suffix indicating a power of two (K=210, M=220, G=230,
T=240, P=250).

Example size examples:

24
0x18
2048
2K

411

AFE1_AFE2-1:1
Syntactic components

IAR C/C++ Compiler User Guide

412 for MSP430

AFE1_AFE2-1:1
 Implementation-defined
behavior for Standard C
● Descriptions of implementation-defined behavior

If you are using C89 instead of Standard C, see Implementation-defined behavior

for C89, page 429. For a short overview of the differences between Standard
C and C89, see C language overview, page 197.

The text in this chapter applies to the DLIB runtime environment. Because the
CLIB runtime environment does not follow Standard C, its
implementation-defined behavior is not documented. See also The CLIB runtime
environment, page 161.

Descriptions of implementation-defined behavior

This section follows the same order as the C standard. Each item includes references to
the ISO chapter and section (in parenthesis) that explains the implementation-defined
behavior.
Note: The IAR Systems implementation adheres to a freestanding implementation of
Standard C. This means that parts of a standard library can be excluded in the
implementation.

J.3.1 TRANSLATION

Diagnostics (3.10, 5.1.1.3)

Diagnostics are 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 compiler detected the error, level is the
level of seriousness of the message (remark, warning, error, or fatal error), tag is a
unique tag that identifies the message, and message is an explanatory message, possibly
several lines.

413

AFE1_AFE2-1:1
Descriptions of implementation-defined behavior

White-space characters (5.1.1.2)

At translation phase three, each non-empty sequence of white-space characters is
retained.

J.3.2 ENVIRONMENT

The character set (5.1.1.2)

The source character set is the same as the physical source file multibyte character set.
By default, the standard ASCII character set is used. However, if you use the
--enable_multibytes compiler option, the host character set is used instead.

Main (5.1.2.1)
The function called at program startup is called main. No prototype is declared for
main, and the only definition supported for main is:

int main(void)

To change this behavior for the DLIB runtime environment, see System initialization,
page 138.

The effect of program termination (5.1.2.1)

Terminating the application returns the execution to the startup code (just after the call
to main).

Alternative ways to define main (5.1.2.2.1)

There is no alternative ways to define the main function.

The argv argument to main (5.1.2.2.1)

The argv argument is not supported.

Streams as interactive devices (5.1.2.3)

The streams stdin, stdout, and stderr are treated as interactive devices.

Signals, their semantics, and the default handling (7.14)

In the DLIB runtime environment, the set of supported signals is the same as in Standard
C. A raised signal will do nothing, unless the signal function is customized to fit the
application.

IAR C/C++ Compiler User Guide

414 for MSP430

AFE1_AFE2-1:1
 Implementation-defined behavior for Standard C

Signal values for computational exceptions (7.14.1.1)

In the DLIB runtime environment, there are no implementation-defined values that
correspond to a computational exception.

Signals at system startup (7.14.1.1)

In the DLIB runtime environment, there are no implementation-defined signals that are
executed at system startup.

Environment names (7.20.4.5)

In the DLIB runtime environment, there are no implementation-defined environment
names that are used by the getenv function.

The system function (7.20.4.6)

The system function is not supported.

J.3.3 IDENTIFIERS

Multibyte characters in identifiers (6.4.2)

Additional multibyte characters may not appear in identifiers.

Significant characters in identifiers (5.2.4.1, 6.1.2)

The number of significant initial characters in an identifier with or without external
linkage is guaranteed to be no less than 200.

J.3.4 CHARACTERS

Number of bits in a byte (3.6)

A byte contains 8 bits.

Execution character set member values (5.2.1)

The values of the members of the execution character set are the values of the ASCII
character set, which can be augmented by the values of the extra characters in the host
character set.

Alphabetic escape sequences (5.2.2)

The standard alphabetic escape sequences have the values \a–7, \b–8, \f–12, \n–10,
\r–13, \t–9, and \v–11.

415

AFE1_AFE2-1:1
Descriptions of implementation-defined behavior

Characters outside of the basic executive character set (6.2.5)

A character outside of the basic executive character set that is stored in a char is not
transformed.

Plain char (6.2.5, 6.3.1.1)

A plain char is treated as an unsigned char.

Source and execution character sets (6.4.4.4, 5.1.1.2)

The source character set is the set of legal characters that can appear in source files. By
default, the source character set is the standard ASCII character set. However, if you use
the command line option --enable_multibytes, the source character set will be the
host computer’s default character set.
The execution character set is the set of legal characters that can appear in the execution
environment. By default, the execution character set is the standard ASCII character set.
However, if you use the command line option --enable_multibytes, the execution
character set will be the host computer’s default character set. The DLIB runtime
environment needs a multibyte character scanner to support a multibyte execution
character set. See Locale, page 149.

Integer character constants with more than one character (6.4.4.4)

An integer character constant that contains more than one character will be treated as an
integer constant. The value will be calculated by treating the leftmost character as the
most significant character, and the rightmost character as the least significant character,
in an integer constant. A diagnostic message will be issued if the value cannot be
represented in an integer constant.

Wide character constants with more than one character (6.4.4.4)

A wide character constant that contains more than one multibyte character generates a
diagnostic message.

Locale used for wide character constants (6.4.4.4)

By default, the C locale is used. If the --enable_multibytes compiler option is used,
the default host locale is used instead.

Locale used for wide string literals (6.4.5)

By default, the C locale is used. If the --enable_multibytes compiler option is used,
the default host locale is used instead.

IAR C/C++ Compiler User Guide

416 for MSP430

AFE1_AFE2-1:1
 Implementation-defined behavior for Standard C

Source characters as executive characters (6.4.5)

All source characters can be represented as executive characters.

J.3.5 INTEGERS

Extended integer types (6.2.5)

There are no extended integer types.

Range of integer values (6.2.6.2)

The representation of integer values are in the two's complement form. The most
significant bit holds the sign—1 for negative, 0 for positive and zero.
For information about the ranges for the different integer types, see Basic data types—
integer types, page 304.

The rank of extended integer types (6.3.1.1)

There are no extended integer types.

Signals when converting to a signed integer type (6.3.1.3)

No signal is raised when an integer is converted to a signed integer type.

Signed bitwise operations (6.5)

Bitwise operations on signed integers work the same way as bitwise operations on
unsigned integers—in other words, the sign-bit will be treated as any other bit, except
for the operator >> which will behave as an arithmetic right shift.

J.3.6 FLOATING POINT

Accuracy of floating-point operations (5.2.4.2.2)

The accuracy of floating-point operations is unknown.

Rounding behaviors (5.2.4.2.2)

There are no non-standard values of FLT_ROUNDS.

Evaluation methods (5.2.4.2.2)

There are no non-standard values of FLT_EVAL_METHOD.

417

AFE1_AFE2-1:1
Descriptions of implementation-defined behavior

Converting integer values to floating-point values (6.3.1.4)

When an integral value is converted to a floating-point value that cannot exactly
represent the source value, the round-to-nearest rounding mode is used (FLT_ROUNDS is
defined to 1).

Converting floating-point values to floating-point values (6.3.1.5)

When a floating-point value is converted to a floating-point value that cannot exactly
represent the source value, the round-to-nearest rounding mode is used (FLT_ROUNDS is
defined to 1).

Denoting the value of floating-point constants (6.4.4.2)

The round-to-nearest rounding mode is used (FLT_ROUNDS is defined to 1).

Contraction of floating-point values (6.5)

Floating-point values are contracted. However, there is no loss in precision and because
signaling is not supported, this does not matter.

Default state of FENV_ACCESS (7.6.1)

The default state of the pragma directive FENV_ACCESS is OFF.

Additional floating-point mechanisms (7.6, 7.12)

There are no additional floating-point exceptions, rounding-modes, environments, and
classifications.

Default state of FP_CONTRACT (7.12.2)

The default state of the pragma directive FP_CONTRACT is OFF.

J.3.7 ARRAYS AND POINTERS

Conversion from/to pointers (6.3.2.3)

For information about casting of data pointers and function pointers, see Casting, page
310.

ptrdiff_t (6.5.6)
For information about ptrdiff_t, see ptrdiff_t, page 310.

IAR C/C++ Compiler User Guide

418 for MSP430

AFE1_AFE2-1:1
 Implementation-defined behavior for Standard C

J.3.8 HINTS

Honoring the register keyword (6.7.1)

User requests for register variables are not honored.

Inlining functions (6.7.4)

User requests for inlining functions increases the chance, but does not make it certain,
that the function will actually be inlined into another function. See Inlining functions,
page 81.

J.3.9 STRUCTURES, UNIONS, ENUMERATIONS, AND

BITFIELDS

Sign of 'plain' bitfields (6.7.2, 6.7.2.1)

For information about how a 'plain' int bitfield is treated, see Bitfields, page 306.

Possible types for bitfields (6.7.2.1)

All integer types can be used as bitfields in the compiler’s extended mode, see -e, page
278.

Bitfields straddling a storage-unit boundary (6.7.2.1)

A bitfield is always placed in one—and one only—storage unit, which means that the
bitfield cannot straddle a storage-unit boundary.

Allocation order of bitfields within a unit (6.7.2.1)

For information about how bitfields are allocated within a storage unit, see Bitfields,
page 306.

Alignment of non-bitfield structure members (6.7.2.1)

The alignment of non-bitfield members of structures is the same as for the member
types, see Alignment, page 303.

Integer type used for representing enumeration types (6.7.2.2)

The chosen integer type for a specific enumeration type depends on the enumeration
constants defined for the enumeration type. The chosen integer type is the smallest
possible.

419

AFE1_AFE2-1:1
Descriptions of implementation-defined behavior

J.3.10 QUALIFIERS

Access to volatile objects (6.7.3)

Any reference to an object with volatile qualified type is an access, see Declaring
objects volatile, page 313.

J.3.11 PREPROCESSING DIRECTIVES

Mapping of header names (6.4.7)

Sequences in header names are mapped to source file names verbatim. A backslash '\'
is not treated as an escape sequence. See Overview of the preprocessor, page 369.

Character constants in constant expressions (6.10.1)

A character constant in a constant expression that controls conditional inclusion
matches the value of the same character constant in the execution character set.

The value of a single-character constant (6.10.1)

A single-character constant may only have a negative value if a plain character (char)
is treated as a signed character, see --char_is_signed, page 270.

Including bracketed filenames (6.10.2)

For information about the search algorithm used for file specifications in angle brackets
<>, see Include file search procedure, page 256.

Including quoted filenames (6.10.2)

For information about the search algorithm used for file specifications enclosed in
quotes, see Include file search procedure, page 256.

Preprocessing tokens in #include directives (6.10.2)

Preprocessing tokens in an #include directive are combined in the same way as outside
an #include directive.

Nesting limits for #include directives (6.10.2)

There is no explicit nesting limit for #include processing.

Universal character names (6.10.3.2)

Universal character names (UCN) are not supported.

IAR C/C++ Compiler User Guide

420 for MSP430

AFE1_AFE2-1:1
 Implementation-defined behavior for Standard C

Recognized pragma directives (6.10.6)

In addition to the pragma directives described in the chapter Pragma directives, the
following directives are recognized and will have an indeterminate effect. If a pragma
directive is listed both in the chapter Pragma directives and here, the information
provided in the chapter Pragma directives overrides the information here.
alignment

baseaddr

building_runtime

can_instantiate

codeseg

cspy_support

define_type_info

do_not_instantiate

early_dynamic_initialization

function

function_effects

hdrstop

important_typedef

instantiate

keep_definition

library_default_requirements

library_provides

library_requirement_override

memory

module_name

no_pch

once

system_include

warnings

421

AFE1_AFE2-1:1
Descriptions of implementation-defined behavior

Default __DATE__ and __TIME__ (6.10.8)

The definitions for __TIME__ and __DATE__ are always available.

J.3.12 LIBRARY FUNCTIONS

Additional library facilities (5.1.2.1)

Most of the standard library facilities are supported. Some of them—the ones that need
an operating system—require a low-level implementation in the application. For more
information, see The DLIB runtime environment, page 115.

Diagnostic printed by the assert function (7.2.1.1)

The assert() function prints:
filename:linenr expression -- assertion failed

when the parameter evaluates to zero.

Representation of the floating-point status flags (7.6.2.2)

For information about the floating-point status flags, see fenv.h, page 383.

Feraiseexcept raising floating-point exception (7.6.2.3)

For information about the feraiseexcept function raising floating-point exceptions,
see Floating-point environment, page 307.

Strings passed to the setlocale function (7.11.1.1)

For information about strings passed to the setlocale function, see Locale, page 149.

Types defined for float_t and double_t (7.12)

The FLT_EVAL_METHOD macro can only have the value 0.

Domain errors (7.12.1)

No function generates other domain errors than what the standard requires.

Return values on domain errors (7.12.1)

Mathematic functions return a floating-point NaN (not a number) for domain errors.

Underflow errors (7.12.1)

Mathematic functions set errno to the macro ERANGE (a macro in errno.h) and return
zero for underflow errors.

IAR C/C++ Compiler User Guide

422 for MSP430

AFE1_AFE2-1:1
 Implementation-defined behavior for Standard C

fmod return value (7.12.10.1)

The fmod function returns a floating-point NaN when the second argument is zero.

The magnitude of remquo (7.12.10.3)

The magnitude is congruent modulo INT_MAX.

signal() (7.14.1.1)
The signal part of the library is not supported.
Note: The default implementation of signal does not perform anything. Use the
template source code to implement application-specific signal handling. See signal,
page 145 and raise, page 143, respectively.

NULL macro (7.17)

The NULL macro is defined to 0.

Terminating newline character (7.19.2)

stdout stream functions recognize either newline or end of file (EOF) as the
terminating character for a line.

Space characters before a newline character (7.19.2)

Space characters written to a stream immediately before a newline character are
preserved.

Null characters appended to data written to binary streams (7.19.2)

No null characters are appended to data written to binary streams.

File position in append mode (7.19.3)

The file position is initially placed at the beginning of the file when it is opened in
append-mode.

Truncation of files (7.19.3)

Whether a write operation on a text stream causes the associated file to be truncated
beyond that point, depends on the application-specific implementation of the low-level
file routines. See Briefly about input and output (I/O), page 116.

File buffering (7.19.3)

An open file can be either block-buffered, line-buffered, or unbuffered.

423

AFE1_AFE2-1:1
Descriptions of implementation-defined behavior

A zero-length file (7.19.3)

Whether a zero-length file exists depends on the application-specific implementation of
the low-level file routines.

Legal file names (7.19.3)

The legality of a filename depends on the application-specific implementation of the
low-level file routines.

Number of times a file can be opened (7.19.3)

Whether a file can be opened more than once depends on the application-specific
implementation of the low-level file routines.

Multibyte characters in a file (7.19.3)

The encoding of multibyte characters in a file depends on the application-specific
implementation of the low-level file routines.

remove() (7.19.4.1)
The effect of a remove operation on an open file depends on the application-specific
implementation of the low-level file routines. See Briefly about input and output (I/O),
page 116.

rename() (7.19.4.2)
The effect of renaming a file to an already existing filename depends on the
application-specific implementation of the low-level file routines. See Briefly about
input and output (I/O), page 116.

Removal of open temporary files (7.19.4.3)

Whether an open temporary file is removed depends on the application-specific
implementation of the low-level file routines.

Mode changing (7.19.5.4)

freopen closes the named stream, then reopens it in the new mode. The streams stdin,
stdout, and stderr can be reopened in any new mode.

Style for printing infinity or NaN (7.19.6.1, 7.24.2.1)

The style used for printing infinity or NaN for a floating-point constant is inf and nan
(INF and NAN for the F conversion specifier), respectively. The n-char-sequence is not
used for nan.

IAR C/C++ Compiler User Guide

424 for MSP430

AFE1_AFE2-1:1
 Implementation-defined behavior for Standard C

%p in printf() (7.19.6.1, 7.24.2.1)

The argument to a %p conversion specifier, print pointer, to printf() is treated as
having the type void *. The value will be printed as a hexadecimal number, similar to
using the %x conversion specifier.

Reading ranges in scanf (7.19.6.2, 7.24.2.1)

A - (dash) character is always treated as a range symbol.

%p in scanf (7.19.6.2, 7.24.2.2)

The %p conversion specifier, scan pointer, to scanf() reads a hexadecimal number and
converts it into a value with the type void *.

File position errors (7.19.9.1, 7.19.9.3, 7.19.9.4)

On file position errors, the functions fgetpos, ftell, and fsetpos store EFPOS in
errno.

An n-char-sequence after nan (7.20.1.3, 7.24.4.1.1)

An n-char-sequence after a NaN is read and ignored.

errno value at underflow (7.20.1.3, 7.24.4.1.1)

errno is set to ERANGE if an underflow is encountered.

Zero-sized heap objects (7.20.3)

A request for a zero-sized heap object will return a valid pointer and not a null pointer.

Behavior of abort and exit (7.20.4.1, 7.20.4.4)

A call to abort() or _Exit() will not flush stream buffers, not close open streams, and
not remove temporary files.

Termination status (7.20.4.1, 7.20.4.3, 7.20.4.4)

The termination status will be propagated to __exit() as a parameter. exit() and
_Exit() use the input parameter, whereas abort uses EXIT_FAILURE.

The system function return value (7.20.4.6)

The system function is not supported.

425

AFE1_AFE2-1:1
Descriptions of implementation-defined behavior

The time zone (7.23.1)

The local time zone and daylight savings time must be defined by the application. For
more information, see __time32, __time64, page 146.

Range and precision of time (7.23)

For information about range and precision, see time.h, page 384. The application must
supply the actual implementation for the functions time and clock. See __time32,
__time64, page 146 and clock, page 140, respectively.

clock() (7.23.2.1)
The application must supply an implementation of the clock function. See clock, page
140.

%Z replacement string (7.23.3.5, 7.24.5.1)

By default, ":" is used as a replacement for %Z. Your application should implement the
time zone handling. See __time32, __time64, page 146.

Math functions rounding mode (F.9)

The functions in math.h honor the rounding direction mode in FLT-ROUNDS.

J.3.13 ARCHITECTURE

Values and expressions assigned to some macros (5.2.4.2, 7.18.2,

7.18.3)
There are always 8 bits in a byte.
MB_LEN_MAX is at the most 6 bytes depending on the library configuration that is used.

For information about sizes, ranges, etc for all basic types, see Data representation, page
303.
The limit macros for the exact-width, minimum-width, and fastest minimum-width
integer types defined in stdint.h have the same ranges as char, short, int, long,
and long long.
The floating-point constant FLT_ROUNDS has the value 1 (to nearest) and the
floating-point constant FLT_EVAL_METHOD has the value 0 (treat as is).

The number, order, and encoding of bytes (6.2.6.1)

See Data representation, page 303.

IAR C/C++ Compiler User Guide

426 for MSP430

AFE1_AFE2-1:1
 Implementation-defined behavior for Standard C

The value of the result of the sizeof operator (6.5.3.4)

See Data representation, page 303.

J.4 LOCALE

Members of the source and execution character set (5.2.1)

By default, the compiler accepts all one-byte characters in the host’s default character
set. If the compiler option --enable_multibytes is used, the host multibyte
characters are accepted in comments and string literals as well.

The meaning of the additional character set (5.2.1.2)

Any multibyte characters in the extended source character set is translated verbatim into
the extended execution character set. It is up to your application with the support of the
library configuration to handle the characters correctly.

Shift states for encoding multibyte characters (5.2.1.2)

Using the compiler option --enable_multibytes enables the use of the host’s default
multibyte characters as extended source characters.

Direction of successive printing characters (5.2.2)

The application defines the characteristics of a display device.

The decimal point character (7.1.1)

The default decimal-point character is a '.'. You can redefine it by defining the library
configuration symbol _LOCALE_DECIMAL_POINT.

Printing characters (7.4, 7.25.2)

The set of printing characters is determined by the chosen locale.

Control characters (7.4, 7.25.2)

The set of control characters is determined by the chosen locale.

Characters tested for (7.4.1.2, 7.4.1.3, 7.4.1.7, 7.4.1.9, 7.4.1.10,

7.4.1.11, 7.25.2.1.2, 7.25.5.1.3, 7.25.2.1.7, 7.25.2.1.9, 7.25.2.1.10,
7.25.2.1.11)
The sets of characters tested are determined by the chosen locale.

427

AFE1_AFE2-1:1
Descriptions of implementation-defined behavior

The native environment (7.1.1.1)

The native environment is the same as the "C" locale.

Subject sequences for numeric conversion functions (7.20.1,

7.24.4.1)
There are no additional subject sequences that can be accepted by the numeric
conversion functions.

The collation of the execution character set (7.21.4.3, 7.24.4.4.2)

The collation of the execution character set is determined by the chosen locale.

Message returned by strerror (7.21.6.2)

The messages returned by the strerror function depending on the argument is:
Argument Message
EZERO no error
EDOM domain error
ERANGE range error
EFPOS file positioning error
EILSEQ multi-byte encoding error
<0 || >99 unknown error
all others error nnn
Table 49: Message returned by strerror()—DLIB runtime environment

IAR C/C++ Compiler User Guide

428 for MSP430

AFE1_AFE2-1:1
 Implementation-defined
behavior for C89
● Descriptions of implementation-defined behavior

If you are using Standard C instead of C89, see Implementation-defined behavior

for Standard C, page 413. For a short overview of the differences between
Standard C and C89, see C language overview, page 197.

Descriptions of implementation-defined behavior

The descriptions follow the same order as the ISO appendix. Each item covered includes
references to the ISO chapter and section (in parenthesis) that explains the
implementation-defined behavior.

TRANSLATION

Diagnostics (5.1.1.3)
Diagnostics are 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 compiler detected the error, level is the
level of seriousness of the message (remark, warning, error, or fatal error), tag is a
unique tag that identifies the message, and message is an explanatory message, possibly
several lines.

ENVIRONMENT

Arguments to main (5.1.2.2.2.1)

The function called at program startup is called main. No prototype was declared for
main, and the only definition supported for main is:

int main(void)

To change this behavior for the DLIB runtime environment, see System initialization,
page 138. To change this behavior for the CLIB runtime environment, see Customizing
system initialization, page 166.

429

AFE1_AFE2-1:1
Descriptions of implementation-defined behavior

Interactive devices (5.1.2.3)

The streams stdin and stdout are treated as interactive devices.

IDENTIFIERS

Significant characters without external linkage (6.1.2)

The number of significant initial characters in an identifier without external linkage is
200.

Significant characters with external linkage (6.1.2)

The number of significant initial characters in an identifier with external linkage is 200.

Case distinctions are significant (6.1.2)

Identifiers with external linkage are treated as case-sensitive.

CHARACTERS

Source and execution character sets (5.2.1)

The source character set is the set of legal characters that can appear in source files. The
default source character set is the standard ASCII character set. However, if you use the
command line option --enable_multibytes, the source character set will be the host
computer’s default character set.
The execution character set is the set of legal characters that can appear in the execution
environment. The default execution character set is the standard ASCII character set.
However, if you use the command line option --enable_multibytes, the execution
character set will be the host computer’s default character set. The DLIB runtime
environment needs a multibyte character scanner to support a multibyte execution
character set. The CLIB runtime environment does not support multibyte characters.
See Locale, page 149.

Bits per character in execution character set (5.2.4.2.1)

The number of bits in a character is represented by the manifest constant CHAR_BIT.
The standard include file limits.h defines CHAR_BIT as 8.

Mapping of characters (6.1.3.4)

The mapping of members of the source character set (in character and string literals) to
members of the execution character set is made in a one-to-one way. In other words, the

IAR C/C++ Compiler User Guide

430 for MSP430

AFE1_AFE2-1:1
 Implementation-defined behavior for C89

same representation value is used for each member in the character sets except for the
escape sequences listed in the ISO standard.

Unrepresented character constants (6.1.3.4)

The value of an integer character constant that contains a character or escape sequence
not represented in the basic execution character set or in the extended character set for
a wide character constant generates a diagnostic message, and will be truncated to fit the
execution character set.

Character constant with more than one character (6.1.3.4)

An integer character constant that contains more than one character will be treated as an
integer constant. The value will be calculated by treating the leftmost character as the
most significant character, and the rightmost character as the least significant character,
in an integer constant. A diagnostic message will be issued if the value cannot be
represented in an integer constant.
A wide character constant that contains more than one multibyte character generates a
diagnostic message.

Converting multibyte characters (6.1.3.4)

The only locale supported—that is, the only locale supplied with the IAR C/C++
Compiler—is the ‘C’ locale. If you use the command line option
--enable_multibytes, the DLIB runtime environment will support multibyte
characters if you add a locale with multibyte support or a multibyte character scanner to
the library. The CLIB runtime environment does not support multibyte characters.
See Locale, page 149.

Range of 'plain' char (6.2.1.1)

A ‘plain’ char has the same range as an unsigned char.

INTEGERS

Range of integer values (6.1.2.5)

The representation of integer values are in the two's complement form. The most
significant bit holds the sign—1 for negative, 0 for positive and zero.
See Basic data types—integer types, page 304, for information about the ranges for the
different integer types.

431

AFE1_AFE2-1:1
Descriptions of implementation-defined behavior

Demotion of integers (6.2.1.2)

Converting an integer to a shorter signed integer is made by truncation. If the value
cannot be represented when converting an unsigned integer to a signed integer of equal
length, the bit-pattern remains the same. In other words, a large enough value will be
converted into a negative value.

Signed bitwise operations (6.3)

Bitwise operations on signed integers work the same way as bitwise operations on
unsigned integers—in other words, the sign-bit will be treated as any other bit, except
for the operator >> which will behave as an arithmetic right shift.

Sign of the remainder on integer division (6.3.5)

The sign of the remainder on integer division is the same as the sign of the dividend.

Negative valued signed right shifts (6.3.7)

The result of a right-shift of a negative-valued signed integral type preserves the sign-bit.
For example, shifting 0xFF00 down one step yields 0xFF80.

FLOATING POINT

Representation of floating-point values (6.1.2.5)

The representation and sets of the various floating-point numbers adheres to IEEE 854–
1987. A typical floating-point number is built up of a sign-bit (s), a biased exponent (e),
and a mantissa (m).
See Basic data types—floating-point types, page 307, for information about the ranges
and sizes for the different floating-point types: float and double.

Converting integer values to floating-point values (6.2.1.3)

When an integral number is cast to a floating-point value that cannot exactly represent
the value, the value is rounded (up or down) to the nearest suitable value.

Demoting floating-point values (6.2.1.4)

When a floating-point value is converted to a floating-point value of narrower type that
cannot exactly represent the value, the value is rounded (up or down) to the nearest
suitable value.

IAR C/C++ Compiler User Guide

432 for MSP430

AFE1_AFE2-1:1
 Implementation-defined behavior for C89

ARRAYS AND POINTERS

size_t (6.3.3.4, 7.1.1)

See size_t, page 310, for information about size_t.

Conversion from/to pointers (6.3.4)

See Casting, page 310, for information about casting of data pointers and function
pointers.

ptrdiff_t (6.3.6, 7.1.1)

See ptrdiff_t, page 310, for information about the ptrdiff_t.

REGISTERS

Honoring the register keyword (6.5.1)

User requests for register variables are not honored.

STRUCTURES, UNIONS, ENUMERATIONS, AND BITFIELDS

Improper access to a union (6.3.2.3)

If a union gets its value stored through a member and is then accessed using a member
of a different type, the result is solely dependent on the internal storage of the first
member.

Padding and alignment of structure members (6.5.2.1)

See the section Basic data types—integer types, page 304, for information about the
alignment requirement for data objects.

Sign of 'plain' bitfields (6.5.2.1)

A 'plain' int bitfield is treated as a signed int bitfield. All integer types are allowed
as bitfields.

Allocation order of bitfields within a unit (6.5.2.1)

Bitfields are allocated within an integer from least-significant to most-significant bit.

Can bitfields straddle a storage-unit boundary (6.5.2.1)

Bitfields cannot straddle a storage-unit boundary for the chosen bitfield integer type.

433

AFE1_AFE2-1:1
Descriptions of implementation-defined behavior

Integer type chosen to represent enumeration types (6.5.2.2)

The chosen integer type for a specific enumeration type depends on the enumeration
constants defined for the enumeration type. The chosen integer type is the smallest
possible.

QUALIFIERS

Access to volatile objects (6.5.3)

Any reference to an object with volatile qualified type is an access.

DECLARATORS

Maximum numbers of declarators (6.5.4)

The number of declarators is not limited. The number is limited only by the available
memory.

STATEMENTS

Maximum number of case statements (6.6.4.2)

The number of case statements (case values) in a switch statement is not limited. The
number is limited only by the available memory.

PREPROCESSING DIRECTIVES

Character constants and conditional inclusion (6.8.1)

The character set used in the preprocessor directives is the same as the execution
character set. The preprocessor recognizes negative character values if a 'plain' character
is treated as a signed character.

Including bracketed filenames (6.8.2)

For file specifications enclosed in angle brackets, the preprocessor does not search
directories of the parent files. A parent file is the file that contains the #include
directive. Instead, it begins by searching for the file in the directories specified on the
compiler command line.

Including quoted filenames (6.8.2)

For file specifications enclosed in quotes, the preprocessor directory search begins with
the directories of the parent file, then proceeds through the directories of any
grandparent files. Thus, searching begins relative to the directory containing the source

IAR C/C++ Compiler User Guide

434 for MSP430

AFE1_AFE2-1:1
 Implementation-defined behavior for C89

file currently being processed. If there is no grandparent file and the file is not found,
the search continues as if the filename was enclosed in angle brackets.

Character sequences (6.8.2)

Preprocessor directives use the source character set, except for escape sequences. Thus,
to specify a path for an include file, use only one backslash:
#include "mydirectory\myfile"

Within source code, two backslashes are necessary:

file = fopen("mydirectory\\myfile","rt");

Recognized pragma directives (6.8.6)

In addition to the pragma directives described in the chapter Pragma directives, the
following directives are recognized and will have an indeterminate effect. If a pragma
directive is listed both in the chapter Pragma directives and here, the information
provided in the chapter Pragma directives overrides the information here.
alignment

baseaddr

building_runtime

can_instantiate

codeseg

cspy_support

define_type_info

do_not_instantiate

early_dynamic_initialization

function

function_effects

hdrstop

important_typedef

instantiate

keep_definition

library_default_requirements

library_provides

435

AFE1_AFE2-1:1
Descriptions of implementation-defined behavior

library_requirement_override

memory

module_name

no_pch

once

system_include

warnings

Default __DATE__ and __TIME__ (6.8.8)

The definitions for __TIME__ and __DATE__ are always available.

LIBRARY FUNCTIONS FOR THE IAR DLIB RUNTIME

ENVIRONMENT
Note: Some items in this list only apply when file descriptors are supported by the
library configuration. For more information about runtime library configurations, see
the chapter The DLIB runtime environment.

NULL macro (7.1.6)

The NULL macro is defined to 0.

Diagnostic printed by the assert function (7.2)

The assert() function prints:
filename:linenr expression -- assertion failed

when the parameter evaluates to zero.

Domain errors (7.5.1)

NaN (Not a Number) will be returned by the mathematic functions on domain errors.

Underflow of floating-point values sets errno to ERANGE (7.5.1)

The mathematics functions set the integer expression errno to ERANGE (a macro in
errno.h) on underflow range errors.

fmod() functionality (7.5.6.4)

If the second argument to fmod() is zero, the function returns NaN—errno is set to
EDOM.

IAR C/C++ Compiler User Guide

436 for MSP430

AFE1_AFE2-1:1
 Implementation-defined behavior for C89

signal() (7.7.1.1)
The signal part of the library is not supported.
Note: The default implementation of signal does not perform anything. Use the
template source code to implement application-specific signal handling. See signal,
page 145 and raise, page 143, respectively.

Terminating newline character (7.9.2)

stdout stream functions recognize either newline or end of file (EOF) as the
terminating character for a line.

Blank lines (7.9.2)

Space characters written to the stdout stream immediately before a newline character
are preserved. There is no way to read the line through the stdin stream that was
written through the stdout stream.

Null characters appended to data written to binary streams (7.9.2)

No null characters are appended to data written to binary streams.

Files (7.9.3)
Whether the file position indicator of an append-mode stream is initially positioned at
the beginning or the end of the file, depends on the application-specific implementation
of the low-level file routines.
Whether a write operation on a text stream causes the associated file to be truncated
beyond that point, depends on the application-specific implementation of the low-level
file routines. See Briefly about input and output (I/O), page 116.
The characteristics of the file buffering is that the implementation supports files that are
unbuffered, line buffered, or fully buffered.
Whether a zero-length file actually exists depends on the application-specific
implementation of the low-level file routines.
Rules for composing valid file names depends on the application-specific
implementation of the low-level file routines.
Whether the same file can be simultaneously open multiple times depends on the
application-specific implementation of the low-level file routines.

437

AFE1_AFE2-1:1
Descriptions of implementation-defined behavior

remove() (7.9.4.1)
The effect of a remove operation on an open file depends on the application-specific
implementation of the low-level file routines. See Briefly about input and output (I/O),
page 116.

rename() (7.9.4.2)
The effect of renaming a file to an already existing filename depends on the
application-specific implementation of the low-level file routines. See Briefly about
input and output (I/O), page 116.

%p in printf() (7.9.6.1)
The argument to a %p conversion specifier, print pointer, to printf() is treated as
having the type void *. The value will be printed as a hexadecimal number, similar to
using the %x conversion specifier.

%p in scanf() (7.9.6.2)
The %p conversion specifier, scan pointer, to scanf() reads a hexadecimal number and
converts it into a value with the type void *.

Reading ranges in scanf() (7.9.6.2)

A - (dash) character is always treated as a range symbol.

File position errors (7.9.9.1, 7.9.9.4)

On file position errors, the functions fgetpos and ftell store EFPOS in errno.

Message generated by perror() (7.9.10.4)

The generated message is:
usersuppliedprefix:errormessage

Allocating zero bytes of memory (7.10.3)

The calloc(), malloc(), and realloc() functions accept zero as an argument.
Memory will be allocated, a valid pointer to that memory is returned, and the memory
block can be modified later by realloc.

Behavior of abort() (7.10.4.1)

The abort() function does not flush stream buffers, and it does not handle files,
because this is an unsupported feature.

IAR C/C++ Compiler User Guide

438 for MSP430

AFE1_AFE2-1:1
 Implementation-defined behavior for C89

Behavior of exit() (7.10.4.3)

The argument passed to the exit function will be the return value returned by the main
function to cstartup.

Environment (7.10.4.4)
The set of available environment names and the method for altering the environment list
is described in getenv, page 141.

system() (7.10.4.5)
How the command processor works depends on how you have implemented the system
function. See system, page 146.

Message returned by strerror() (7.11.6.2)

The messages returned by strerror() depending on the argument is:
Argument Message
EZERO no error
EDOM domain error
ERANGE range error
EFPOS file positioning error
EILSEQ multi-byte encoding error
<0 || >99 unknown error
all others error nnn
Table 50: Message returned by strerror()—DLIB runtime environment

The time zone (7.12.1)

The local time zone and daylight savings time implementation is described in __time32,
__time64, page 146.

clock() (7.12.2.1)
From where the system clock starts counting depends on how you have implemented the
clock function. See clock, page 140.

LIBRARY FUNCTIONS FOR THE CLIB RUNTIME

ENVIRONMENT

NULL macro (7.1.6)

The NULL macro is defined to (void *) 0.

439

AFE1_AFE2-1:1
Descriptions of implementation-defined behavior

Diagnostic printed by the assert function (7.2)

The assert() function prints:
Assertion failed: expression, file Filename, line linenumber

when the parameter evaluates to zero.

Domain errors (7.5.1)

HUGE_VAL, the largest representable value in a double floating-point type, will be
returned by the mathematic functions on domain errors.

Underflow of floating-point values sets errno to ERANGE (7.5.1)

The mathematics functions set the integer expression errno to ERANGE (a macro in
errno.h) on underflow range errors.

fmod() functionality (7.5.6.4)

If the second argument to fmod() is zero, the function returns zero (it does not change
the integer expression errno).

signal() (7.7.1.1)
The signal part of the library is not supported.

Terminating newline character (7.9.2)

stdout stream functions recognize either newline or end of file (EOF) as the
terminating character for a line.

Blank lines (7.9.2)

Space characters written to the stdout stream immediately before a newline character
are preserved. There is no way to read the line through the stdin stream that was
written through the stdout stream.

Null characters appended to data written to binary streams (7.9.2)

There are no binary streams implemented.

Files (7.9.3)
There are no other streams than stdin and stdout. This means that a file system is not
implemented.

IAR C/C++ Compiler User Guide

440 for MSP430

AFE1_AFE2-1:1
 Implementation-defined behavior for C89

remove() (7.9.4.1)
There are no other streams than stdin and stdout. This means that a file system is not
implemented.

rename() (7.9.4.2)
There are no other streams than stdin and stdout. This means that a file system is not
implemented.

%p in printf() (7.9.6.1)
The argument to a %p conversion specifier, print pointer, to printf() is treated as
having the type 'char *'. The value will be printed as a hexadecimal number, similar
to using the %x conversion specifier.

%p in scanf() (7.9.6.2)
The %p conversion specifier, scan pointer, to scanf() reads a hexadecimal number and
converts it into a value with the type 'void *'.

Reading ranges in scanf() (7.9.6.2)

A - (dash) character is always treated explicitly as a - character.

File position errors (7.9.9.1, 7.9.9.4)

There are no other streams than stdin and stdout. This means that a file system is not
implemented.

Message generated by perror() (7.9.10.4)

perror() is not supported.

Allocating zero bytes of memory (7.10.3)

The calloc(), malloc(), and realloc() functions accept zero as an argument.
Memory will be allocated, a valid pointer to that memory is returned, and the memory
block can be modified later by realloc.

Behavior of abort() (7.10.4.1)

The abort() function does not flush stream buffers, and it does not handle files,
because this is an unsupported feature.

Behavior of exit() (7.10.4.3)

The exit() function does not return.

441

AFE1_AFE2-1:1
Descriptions of implementation-defined behavior

Environment (7.10.4.4)
Environments are not supported.

system() (7.10.4.5)
The system() function is not supported.

Message returned by strerror() (7.11.6.2)

The messages returned by strerror() depending on the argument are:
Argument Message
EZERO no error
EDOM domain error
ERANGE range error
<0 || >99 unknown error
all others error No.xx
Table 51: Message returned by strerror()—CLIB runtime environment

The time zone (7.12.1)

The time zone function is not supported.

clock() (7.12.2.1)
The clock() function is not supported.

IAR C/C++ Compiler User Guide

442 for MSP430

AFE1_AFE2-1:1
 Index

Index
of incomplete types . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
A single-value initialization . . . . . . . . . . . . . . . . . . . . . . . 203
abort asm, __asm (language extension) . . . . . . . . . . . . . . . . . . . 172
implementation-defined behavior . . . . . . . . . . . . . . . . 425 assembler code
implementation-defined behavior in C89 (CLIB) . . . . 441 calling from C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
implementation-defined behavior in C89 (DLIB) . . . . 438 calling from C++ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
system termination (DLIB) . . . . . . . . . . . . . . . . . . . . . 137 inserting inline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
absolute location assembler directives
data, placing at (@) . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 for call frame information . . . . . . . . . . . . . . . . . . . . . . 193
language support for . . . . . . . . . . . . . . . . . . . . . . . . . . 200 using in inline assembler code . . . . . . . . . . . . . . . . . . . 171
#pragma location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 assembler instructions, inserting inline . . . . . . . . . . . . . . . 171
ADC12 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 assembler labels
addressing. See memory types, data models, default for application startup . . . . . . . . . . . . . . . . . . . . 54
and code models making public (--public_equ) . . . . . . . . . . . . . . . . . . . . 294
algorithm (STL header file) . . . . . . . . . . . . . . . . . . . . . . . 382 assembler language interface . . . . . . . . . . . . . . . . . . . . . . 169
alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 calling convention. See assembler code
forcing stricter (#pragma data_alignment) . . . . . . . . . . 336 assembler list file, generating . . . . . . . . . . . . . . . . . . . . . . 282
in structures (#pragma pack) . . . . . . . . . . . . . . . . . . . . 347 assembler output file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
in structures, causing problems . . . . . . . . . . . . . . . . . . 234 asserts
of an object (__ALIGNOF__) . . . . . . . . . . . . . . . . . . . 200 implementation-defined behavior of . . . . . . . . . . . . . . 422
of data types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 implementation-defined behavior of in C89, (CLIB) . . 440
alignment (pragma directive) . . . . . . . . . . . . . . . . . . 421, 435 implementation-defined behavior of in C89, (DLIB) . . 436
__ALIGNOF__ (operator) . . . . . . . . . . . . . . . . . . . . . . . . 200 including in application . . . . . . . . . . . . . . . . . . . . . . . . 375
anonymous structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 assert.h (CLIB header file) . . . . . . . . . . . . . . . . . . . . . . . . 386
anonymous symbols, creating . . . . . . . . . . . . . . . . . . . . . . 197 assert.h (DLIB header file) . . . . . . . . . . . . . . . . . . . . . . . . 380
ANSI C. See C89 __assignment_by_bitwise_copy_allowed, symbol used
application in library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
building, overview of . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 @ (operator)
execution, overview of . . . . . . . . . . . . . . . . . . . . . . . . . . 50 placing at absolute address . . . . . . . . . . . . . . . . . . . . . . 237
startup and termination (CLIB) . . . . . . . . . . . . . . . . . . 165 placing in segments . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
startup and termination (DLIB) . . . . . . . . . . . . . . . . . . 135 atomic operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
argv (argument), implementation-defined behavior . . . . . 414 __monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
arrays attributes
designated initializers in . . . . . . . . . . . . . . . . . . . . . . . 197 object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
global, accessing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
implementation-defined behavior . . . . . . . . . . . . . . . . 418 auto variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
implementation-defined behavior in C89 . . . . . . . . . . . 433 at function entrance . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
incomplete at end of structs . . . . . . . . . . . . . . . . . . . . . 197 programming hints for efficient code . . . . . . . . . . . . . . 246
non-lvalue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 using in inline assembler statements . . . . . . . . . . . . . . 171

443

AFE1_AFE2-1:1
 building_runtime (pragma directive). . . . . . . . . . . . . 421, 435
B __BUILD_NUMBER__ (predefined symbol) . . . . . . . . . 370
backtrace information See call frame information
Barr, Michael . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
baseaddr (pragma directive) . . . . . . . . . . . . . . . . . . . 421, 435
C
__BASE_FILE__ (predefined symbol) . . . . . . . . . . . . . . . 370 C and C++ linkage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
basic type names, using in preprocessor expressions C/C++ calling convention. See calling convention
(--migration_preprocessor_extensions) . . . . . . . . . . . . . . . 284 C header files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
basic_template_matching (pragma directive) . . . . . . . . . . 333 C language, overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
using . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 call frame information . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
batch files in assembler list file . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
error return codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258 in assembler list file (-lA) . . . . . . . . . . . . . . . . . . . . . . 282
none for building library from command line . . . . . . . 125 call frame information, disabling (--no_call_frame_info) . 286
__bcd_add_long (intrinsic function) . . . . . . . . . . . . . . . . . 357 call graph root (stack usage control directive) . . . . . . . . . . 405
__bcd_add_long_long (intrinsic function) . . . . . . . . . . . . 357 call stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
__bcd_add_short (intrinsic function) . . . . . . . . . . . . . . . . 357 callee-save registers, stored on stack . . . . . . . . . . . . . . . . . . 68
__bic_SR_register (intrinsic function) . . . . . . . . . . . . . . . 357 calling convention
__bic_SR_register_on_exit (intrinsic function) . . . . . . . . 358 C++, requiring C linkage . . . . . . . . . . . . . . . . . . . . . . . 180
binary streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423 in compiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
binary streams in C89 (CLIB) . . . . . . . . . . . . . . . . . . . . . . 440 overriding default (__cc_rom) . . . . . . . . . . . . . . . . . . . 321
binary streams in C89 (DLIB). . . . . . . . . . . . . . . . . . . . . . 437 overriding default (__cc_version1) . . . . . . . . . . . . . . . 322
__bis_GIE_interrupt_state (intrinsic function) . . . . . . . . . 358 overriding default (__cc_version2) . . . . . . . . . . . . . . . 322
bis_nmi_ie1 (pragma directive) . . . . . . . . . . . . . . . . . . . . 334 calloc (library function) . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
__bis_SR_register (intrinsic function) . . . . . . . . . . . . . . . 358 See also heap
__bis_SR_register_on_exit (intrinsic function). . . . . . . . . 358 implementation-defined behavior in C89 (CLIB) . . . . 441
bit negation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 implementation-defined behavior in C89 (DLIB) . . . . 438
bitfields calls (pragma directive). . . . . . . . . . . . . . . . . . . . . . . . . . . 335
data representation of . . . . . . . . . . . . . . . . . . . . . . . . . . 306 call_graph_root (pragma directive) . . . . . . . . . . . . . . . . . . 335
hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 call-info (in stack usage control file). . . . . . . . . . . . . . . . . 410
implementation-defined behavior . . . . . . . . . . . . . . . . 419 can_instantiate (pragma directive) . . . . . . . . . . . . . . 421, 435
implementation-defined behavior in C89 . . . . . . . . . . . 433 cassert (library header file) . . . . . . . . . . . . . . . . . . . . . . . . 382
non-standard types in . . . . . . . . . . . . . . . . . . . . . . . . . . 200 cast operators
bitfields (pragma directive) . . . . . . . . . . . . . . . . . . . . . . . . 334 in Extended EC++ . . . . . . . . . . . . . . . . . . . . . . . . 206, 217
bits in a byte, implementation-defined behavior . . . . . . . . 415 missing from Embedded C++ . . . . . . . . . . . . . . . . . . . 206
bold style, in this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 casting
bool (data type) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 between pointer types . . . . . . . . . . . . . . . . . . . . . . . . . . 63
adding support for in CLIB . . . . . . . . . . . . . . . . . . . . . 386 of pointers and integers . . . . . . . . . . . . . . . . . . . . . . . . 310
adding support for in DLIB . . . . . . . . . . . . . . . . . 380, 383 pointers to integers, language extension . . . . . . . . . . . . 202
BSLSIGNATURE (segment) . . . . . . . . . . . . . . . . . . . . . . 389 category (in stack usage control file) . . . . . . . . . . . . . . . . 409

IAR C/C++ Compiler User Guide

444 for MSP430

AFE1_AFE2-1:1
 Index

cctype (DLIB header file) . . . . . . . . . . . . . . . . . . . . . . . . . 382 clock (library function), implementation-defined

__cc_rom (extended keyword) . . . . . . . . . . . . . . . . . . . . . 321 behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
__cc_version1 (extended keyword) . . . . . . . . . . . . . . . . . 322 cmath (DLIB header file) . . . . . . . . . . . . . . . . . . . . . . . . . 383
cerrno (DLIB header file) . . . . . . . . . . . . . . . . . . . . . . . . . 382 code
cexit (system termination code) execution of . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
customizing system termination . . . . . . . . . . . . . . . . . . 138 facilitating for good generation of . . . . . . . . . . . . . . . . 245
CFI (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . . 193 interruption of execution . . . . . . . . . . . . . . . . . . . . . . . . 73
cfloat (DLIB header file) . . . . . . . . . . . . . . . . . . . . . . . . . 382 verifying linked result . . . . . . . . . . . . . . . . . . . . . . . . . 110
char (data type) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 code models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
changing default representation (--char_is_signed) . . . 270 calling functions in. . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
changing representation (--char_is_unsigned) . . . . . . . 270 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
implementation-defined behavior . . . . . . . . . . . . . . . . 416 identifying (__CODE_MODEL__) . . . . . . . . . . . . . . . 370
signed and unsigned . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 selecting (--code_model) . . . . . . . . . . . . . . . . . . . . . . . 271
character set, implementation-defined behavior . . . . . . . . 414 code motion (compiler transformation) . . . . . . . . . . . . . . . 244
characters disabling (--no_code_motion) . . . . . . . . . . . . . . . . . . . 286
implementation-defined behavior . . . . . . . . . . . . . . . . 415 CODE (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
implementation-defined behavior in C89 . . . . . . . . . . . 430 using . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
character-based I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 codeseg (pragma directive) . . . . . . . . . . . . . . . . . . . . 421, 435
--char_is_signed (compiler option) . . . . . . . . . . . . . . . . . . 270 __code_distance (intrinsic function) . . . . . . . . . . . . . . . . . 358
--char_is_unsigned (compiler option) . . . . . . . . . . . . . . . . 270 CODE_I (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
check that (linker directive) . . . . . . . . . . . . . . . . . . . . . . . 406 linker considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 108
checksum, calculation of . . . . . . . . . . . . . . . . . . . . . . . . . . 224 CODE_ID (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
CHECKSUM (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . 390 linker considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 108
cinttypes (DLIB header file) . . . . . . . . . . . . . . . . . . . . . . . 382 __CODE_MODEL__ (predefined symbol). . . . . . . . . . . . 370
class memory (extended EC++) . . . . . . . . . . . . . . . . . . . . 208 --code_model (compiler option) . . . . . . . . . . . . . . . . . . . . 270
class template partial specialization CODE_PAD (segment). . . . . . . . . . . . . . . . . . . . . . . . . . . 391
matching (extended EC++) . . . . . . . . . . . . . . . . . . . . . . . . 214 __code, symbol used in library . . . . . . . . . . . . . . . . . . . . . 385
CLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386 CODE16 (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
library reference information for . . . . . . . . . . . . . . . . . . 32 using . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
naming convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 command line options
runtime environment . . . . . . . . . . . . . . . . . . . . . . . . . . 161 See also compiler options
summary of definitions . . . . . . . . . . . . . . . . . . . . . . . . 386 part of compiler invocation syntax . . . . . . . . . . . . . . . . 255
--clib (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 passing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
climits (DLIB header file) . . . . . . . . . . . . . . . . . . . . . . . . . 383 typographic convention . . . . . . . . . . . . . . . . . . . . . . . . . 34
clobber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 command prompt icon, in this guide . . . . . . . . . . . . . . . . . . 34
clocale (DLIB header file) . . . . . . . . . . . . . . . . . . . . . . . . 383 comments
clock (CLIB library function), implementation-defined after preprocessor directives . . . . . . . . . . . . . . . . . . . . 203
behavior in C89 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 C++ style, using in C code . . . . . . . . . . . . . . . . . . . . . . 197
clock (DLIB library function), implementation-defined common block (call frame information) . . . . . . . . . . . . . . 193
behavior in C89 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439

445

AFE1_AFE2-1:1
 common subexpr elimination (compiler transformation) . 243 for locale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
disabling (--no_cse) . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 for printf and scanf . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
compilation date for strtod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
exact time of (__TIME__) . . . . . . . . . . . . . . . . . . . . . . 374 in library configuration files. . . . . . . . . . . . . . . . . . . . . 125
identifying (__DATE__) . . . . . . . . . . . . . . . . . . . . . . . 371 consistency, module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
compiler const
environment variables . . . . . . . . . . . . . . . . . . . . . . . . . 256 declaring objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
invocation syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 non-top level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
output from . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258 constants, placing in named segment . . . . . . . . . . . . . . . . 336
compiler listing, generating (-l). . . . . . . . . . . . . . . . . . . . . 282 __constrange(), symbol used in library . . . . . . . . . . . . . . . 385
compiler object file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 __construction_by_bitwise_copy_allowed, symbol used
including debug information in (--debug, -r) . . . . . . . . 272 in library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
output from compiler . . . . . . . . . . . . . . . . . . . . . . . . . . 258 constseg (pragma directive) . . . . . . . . . . . . . . . . . . . . . . . 336
compiler optimization levels . . . . . . . . . . . . . . . . . . . . . . . 242 const_cast (cast operator) . . . . . . . . . . . . . . . . . . . . . . . . . 206
compiler options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 contents, of this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
passing to compiler . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 control characters,
reading from file (-f) . . . . . . . . . . . . . . . . . . . . . . . . . . 280 implementation-defined behavior . . . . . . . . . . . . . . . . . . . 427
specifying parameters . . . . . . . . . . . . . . . . . . . . . . . . . 265 conventions, used in this guide . . . . . . . . . . . . . . . . . . . . . . 33
summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 copy initialization, of segments. . . . . . . . . . . . . . . . . . . . . 108
syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 copyright notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
for creating skeleton code . . . . . . . . . . . . . . . . . . . . . . 179 __CORE__ (predefined symbol). . . . . . . . . . . . . . . . . . . . 370
--warnings_affect_exit_code . . . . . . . . . . . . . . . . . . . . 259 core, identifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
compiler platform, identifying . . . . . . . . . . . . . . . . . . . . . 372 cos (library function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
compiler subversion number . . . . . . . . . . . . . . . . . . . . . . . 374 cos (library routine) . . . . . . . . . . . . . . . . . . . . . . . . . 133–134
compiler transformations . . . . . . . . . . . . . . . . . . . . . . . . . 240 cosf (library routine) . . . . . . . . . . . . . . . . . . . . . . . . . 133–134
compiler version number . . . . . . . . . . . . . . . . . . . . . . . . . 374 cosl (library routine) . . . . . . . . . . . . . . . . . . . . . . . . . 133–134
compiling __COUNTER__ (predefined symbol). . . . . . . . . . . . . . . . 370
from the command line . . . . . . . . . . . . . . . . . . . . . . . . . 54 __cplusplus (predefined symbol) . . . . . . . . . . . . . . . . . . . 370
syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 csetjmp (DLIB header file) . . . . . . . . . . . . . . . . . . . . . . . . 383
complex numbers, supported in Embedded C++ . . . . . . . . 206 csignal (DLIB header file) . . . . . . . . . . . . . . . . . . . . . . . . 383
complex (library header file). . . . . . . . . . . . . . . . . . . . . . . 381 cspy_support (pragma directive) . . . . . . . . . . . . . . . . 421, 435
complex.h (library header file) . . . . . . . . . . . . . . . . . . . . . 380 CSTACK (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
compound literals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 See also stack
computer style, typographic convention . . . . . . . . . . . . . . . 34 CSTART (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
configuration cstartup (system startup code)
basic project settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 customizing system initialization . . . . . . . . . . . . . . . . . 138
__low_level_init . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 source files for (CLIB) . . . . . . . . . . . . . . . . . . . . . . . . . 165
configuration symbols source files for (DLIB). . . . . . . . . . . . . . . . . . . . . . . . . 135
for file input and output . . . . . . . . . . . . . . . . . . . . . . . . 149 cstat_disable (pragma directive) . . . . . . . . . . . . . . . . . . . . 331
cstat_enable (pragma directive) . . . . . . . . . . . . . . . . . . . . 331

IAR C/C++ Compiler User Guide

446 for MSP430

AFE1_AFE2-1:1
 Index

cstat_restore (pragma directive) . . . . . . . . . . . . . . . . . . . . 331 C99. See Standard C

cstat_suppress (pragma directive) . . . . . . . . . . . . . . . . . . . 331
cstdarg (DLIB header file) . . . . . . . . . . . . . . . . . . . . . . . . 383
cstdbool (DLIB header file) . . . . . . . . . . . . . . . . . . . . . . . 383 D
cstddef (DLIB header file) . . . . . . . . . . . . . . . . . . . . . . . . 383 -D (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
cstdio (DLIB header file) . . . . . . . . . . . . . . . . . . . . . . . . . 383 data
cstdlib (DLIB header file) . . . . . . . . . . . . . . . . . . . . . . . . . 383 alignment of . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
cstring (DLIB header file) . . . . . . . . . . . . . . . . . . . . . . . . . 383 different ways of storing . . . . . . . . . . . . . . . . . . . . . . . . 60
ctime (DLIB header file) . . . . . . . . . . . . . . . . . . . . . . . . . . 383 located, declaring extern . . . . . . . . . . . . . . . . . . . . . . . 238
ctype.h (library header file) . . . . . . . . . . . . . . . . . . . . 380, 386 placing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236, 298, 337
cwctype.h (library header file) . . . . . . . . . . . . . . . . . . . . . 383 at absolute location . . . . . . . . . . . . . . . . . . . . . . . . . 237
?C_EXIT (assembler label) . . . . . . . . . . . . . . . . . . . . . . . . 167 representation of . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
?C_GETCHAR (assembler label) . . . . . . . . . . . . . . . . . . . 167 storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
C_INCLUDE (environment variable) . . . . . . . . . . . . . . . . 256 verifying linked result . . . . . . . . . . . . . . . . . . . . . . . . . 110
?C_PUTCHAR (assembler label) . . . . . . . . . . . . . . . . . . . 167 data block (call frame information) . . . . . . . . . . . . . . . . . . 193
C-SPY data memory attributes, using . . . . . . . . . . . . . . . . . . . . . . . 61
debug support for C++ . . . . . . . . . . . . . . . . . . . . . . . . . 213 data models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
interface to system termination . . . . . . . . . . . . . . . . . . 138 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
low-level interface (CLIB) . . . . . . . . . . . . . . . . . . . . . . 166 identifying (__DATA_MODEL__) . . . . . . . . . . . . . . . 371
C-STAT for static analysis, documentation for . . . . . . . . . . 32 Large . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
C++ Medium . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
See also Embedded C++ and Extended Embedded C++ setting (--data_model) . . . . . . . . . . . . . . . . . . . . . . . . . 272
absolute location . . . . . . . . . . . . . . . . . . . . . . . . . 238–239 Small . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
calling convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 data pointers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
dynamic initialization in . . . . . . . . . . . . . . . . . . . . . . . 108 data types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
header files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 avoiding large . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
language extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 floating point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
standard template library (STL) . . . . . . . . . . . . . . . . . . 382 in C++ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
static member variables . . . . . . . . . . . . . . . . . . . . 238–239 integer types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
support for . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 dataseg (pragma directive) . . . . . . . . . . . . . . . . . . . . . . . . 337
C++ header files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 data_alignment (pragma directive) . . . . . . . . . . . . . . . . . . 336
C++ names, in assembler code . . . . . . . . . . . . . . . . . . . . . 181 __DATA_MODEL__ (predefined symbol) . . . . . . . . . . . 371
C++ objects, placing in memory type . . . . . . . . . . . . . . . . . 65 --data_model (compiler option) . . . . . . . . . . . . . . . . . . . . 272
C++ terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 __data16 (extended keyword) . . . . . . . . . . . . . . . . . . . . . . 322
C++-style comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 DATA16_AC (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . 392
C89 DATA16_AN (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . 392
implementation-defined behavior . . . . . . . . . . . . . . . . 429 DATA16_C (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
support for . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 DATA16_HEAP (segment) . . . . . . . . . . . . . . . . . . . . . . . 393
--c89 (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 DATA16_I (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

447

AFE1_AFE2-1:1
 DATA16_ID (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . 393 delete (keyword) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
DATA16_N (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . 394 --dependencies (compiler option) . . . . . . . . . . . . . . . . . . . 273
DATA16_P (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . 394 deque (STL header file) . . . . . . . . . . . . . . . . . . . . . . . . . . 382
__data16_read_addr (intrinsic function) . . . . . . . . . . . . . . 359 destructors and interrupts, using . . . . . . . . . . . . . . . . . . . . 212
__data16_size_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 device description files, preconfigured for C-SPY . . . . . . . 42
DATA16_Z (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . 394 diagnostic messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
__data20 (extended keyword) . . . . . . . . . . . . . . . . . . . . . . 323 classifying as compilation errors . . . . . . . . . . . . . . . . . 274
DATA20_AC (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . 395 classifying as compilation remarks . . . . . . . . . . . . . . . 274
DATA20_AN (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . 395 classifying as compiler warnings . . . . . . . . . . . . . . . . . 275
DATA20_C (segment) . . . . . . . . . . . . . . . . . . . . . . . 395–396 disabling compiler warnings . . . . . . . . . . . . . . . . . . . . 290
DATA20_HEAP (segment) . . . . . . . . . . . . . . . . . . . . . . . 396 disabling wrapping of in compiler . . . . . . . . . . . . . . . . 290
DATA20_I (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 enabling compiler remarks . . . . . . . . . . . . . . . . . . . . . . 296
DATA20_ID (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . 396 listing all used by compiler . . . . . . . . . . . . . . . . . . . . . 275
__data20_longjmp (intrinsic function) . . . . . . . . . . . . . . . 360 suppressing in compiler . . . . . . . . . . . . . . . . . . . . . . . . 275
DATA20_N (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 --diagnostics_tables (compiler option) . . . . . . . . . . . . . . . 275
DATA20_P (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 diagnostics, implementation-defined behavior . . . . . . . . . 413
__data20_read_char (intrinsic function) . . . . . . . . . . . . . . 360 diag_default (pragma directive) . . . . . . . . . . . . . . . . . . . . 339
__data20_read_long (intrinsic function) . . . . . . . . . . . . . . 360 --diag_error (compiler option) . . . . . . . . . . . . . . . . . . . . . 274
__data20_read_short (intrinsic function) . . . . . . . . . . . . . 360 diag_error (pragma directive) . . . . . . . . . . . . . . . . . . . . . . 340
__data20_setjmp (intrinsic function). . . . . . . . . . . . . . . . . 360 --diag_remark (compiler option) . . . . . . . . . . . . . . . . . . . . 274
__data20_write_char (intrinsic function) . . . . . . . . . . . . . 361 diag_remark (pragma directive) . . . . . . . . . . . . . . . . . . . . 340
__data20_write_long (intrinsic function) . . . . . . . . . . . . . 361 --diag_suppress (compiler option) . . . . . . . . . . . . . . . . . . 275
__data20_write_short (intrinsic function) . . . . . . . . . . . . . 361 diag_suppress (pragma directive) . . . . . . . . . . . . . . . . . . . 340
DATA20_Z (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 --diag_warning (compiler option) . . . . . . . . . . . . . . . . . . . 275
__DATE__ (predefined symbol). . . . . . . . . . . . . . . . . . . . 371 diag_warning (pragma directive) . . . . . . . . . . . . . . . . . . . 341
date (library function), configuring support for . . . . . . . . . 123 DIFUNCT (segment) . . . . . . . . . . . . . . . . . . . . . . . . 108, 398
--debug (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . 272 directives, pragma . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 331
debug information, including in object file . . . . . . . . . . . . 272 directory, specifying as parameter . . . . . . . . . . . . . . . . . . 264
decimal point, implementation-defined behavior . . . . . . . 427 __disable_interrupt (intrinsic function) . . . . . . . . . . . . . . . 361
declarations --discard_unused_publics (compiler option) . . . . . . . . . . . 276
empty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
in for loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 DLIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Kernighan & Ritchie . . . . . . . . . . . . . . . . . . . . . . . . . . 247 configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
of functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124, 277
declarations and statements, mixing . . . . . . . . . . . . . . . . . 197 naming convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
declarators, implementation-defined behavior in C89 . . . . 434 reference information. See the online help system . . . . 377
define_type_info (pragma directive) . . . . . . . . . . . . . 421, 435 runtime environment . . . . . . . . . . . . . . . . . . . . . . . . . . 115
__delay_cycles (intrinsic function) . . . . . . . . . . . . . . . . . . 361 --dlib (compiler option). . . . . . . . . . . . . . . . . . . . . . . . . . . 276
delete operator (extended EC++) . . . . . . . . . . . . . . . . . . . 211 --dlib_config (compiler option). . . . . . . . . . . . . . . . . . . . . 277

IAR C/C++ Compiler User Guide

448 for MSP430

AFE1_AFE2-1:1
 Index

DLib_Defaults.h (library configuration file) . . . . . . . . . . . 125 enabling restrict keyword . . . . . . . . . . . . . . . . . . . . . . . . . 279

__DLIB_FILE_DESCRIPTOR (configuration symbol) . . 149 entry label, program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 enumerations
documentation implementation-defined behavior . . . . . . . . . . . . . . . . 419
contents of this . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 implementation-defined behavior in C89 . . . . . . . . . . . 433
how to use this . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 enums
overview of guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 data representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
who should read this . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 forward declarations of . . . . . . . . . . . . . . . . . . . . . . . . 202
domain errors, implementation-defined behavior . . . . . . . 422 environment
domain errors, implementation-defined behavior in C89 implementation-defined behavior . . . . . . . . . . . . . . . . 414
(CLIB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 implementation-defined behavior in C89 . . . . . . . . . . . 429
domain errors, implementation-defined behavior in C89 runtime (CLIB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
(DLIB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436 runtime (DLIB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
--double (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . 277 environment names, implementation-defined behavior . . . 415
double (data type) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 environment variables, C_INCLUDE . . . . . . . . . . . . . . . . 256
avoiding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 environment (native), implementation-defined behavior. . 428
configuring size of floating-point type . . . . . . . . . . . . . . 57 epilogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
do_not_instantiate (pragma directive) . . . . . . . . . . . . 421, 435 EQU (assembler directive) . . . . . . . . . . . . . . . . . . . . . . . . 294
dynamic initialization . . . . . . . . . . . . . . . . . . . . . . . . 135, 165 ERANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
and C++ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 ERANGE (C89) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
dynamic memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 errno value at underflow, implementation-defined
behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425

E errno.h (library header file) . . . . . . . . . . . . . . . . . . . . 380, 386

error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
-e (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 classifying for compiler . . . . . . . . . . . . . . . . . . . . . . . . 274
early_initialization (pragma directive) . . . . . . . . . . . 421, 435 error return codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
--ec++ (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . . 278 error (pragma directive) . . . . . . . . . . . . . . . . . . . . . . . . . . 341
edition, of this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 errors and warnings, listing all used by the compiler
--eec++ (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . 279 (--diagnostics_tables) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Embedded C++ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 --error_limit (compiler option) . . . . . . . . . . . . . . . . . . . . . 280
differences from C++ . . . . . . . . . . . . . . . . . . . . . . . . . . 206 escape sequences, implementation-defined behavior . . . . 415
enabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 __even_in_range (intrinsic function) . . . . . . . . . . . . . . . . 362
language extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 exception handling, missing from Embedded C++ . . . . . . 206
embedded systems, IAR special support for . . . . . . . . . . . . 42 exception vectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
__embedded_cplusplus (predefined symbol) . . . . . . . . . . 371 exclude (stack usage control directive) . . . . . . . . . . . . . . . 406
__enable_interrupt (intrinsic function) . . . . . . . . . . . . . . . 362 _Exit (library function) . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
--enable_multibytes (compiler option) . . . . . . . . . . . . . . . 279 exit (library function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
--enable_restrict (compiler option) . . . . . . . . . . . . . . . . . . 279 implementation-defined behavior . . . . . . . . . . . . . . . . 425
implementation-defined behavior in C89 . . . . . . . 439, 441

449

AFE1_AFE2-1:1
 _exit (library function) . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 file dependencies, tracking . . . . . . . . . . . . . . . . . . . . . . . . 273
__exit (library function) . . . . . . . . . . . . . . . . . . . . . . . . . . 137 file input and output, configuration symbols for . . . . . . . . 149
exp (library routine) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 file paths, specifying for #include files . . . . . . . . . . . . . . . 282
expf (library routine) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 file position, implementation-defined behavior . . . . . . . . . 423
expl (library routine) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 file streams lock interface . . . . . . . . . . . . . . . . . . . . . . . . . 156
export keyword, missing from Extended EC++ . . . . . . . . 213 file systems in C89 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
extended command line file file (zero-length), implementation-defined behavior . . . . . 424
for compiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 filename
passing options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 extension for device description files . . . . . . . . . . . . . . . 42
Extended Embedded C++ . . . . . . . . . . . . . . . . . . . . . . . . . 206 extension for header files . . . . . . . . . . . . . . . . . . . . . . . . 41
enabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 of object file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
extended keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 search procedure for. . . . . . . . . . . . . . . . . . . . . . . . . . . 256
enabling (-e) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 specifying as parameter . . . . . . . . . . . . . . . . . . . . . . . . 264
overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 filenames (legal), implementation-defined behavior . . . . . 424
summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 fileno, in stdio.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
syntax files, implementation-defined behavior
object attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 handling of temporary . . . . . . . . . . . . . . . . . . . . . . . . . 424
type attributes on data objects . . . . . . . . . . . . . . 62, 318 multibyte characters in . . . . . . . . . . . . . . . . . . . . . . . . . 424
type attributes on functions . . . . . . . . . . . . . . . . . . . 319 opening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
__ramfunc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 float (data type) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
extern "C" linkage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 floating-point constants
hexadecimal notation . . . . . . . . . . . . . . . . . . . . . . . . . . 197

F hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
floating-point environment, accessing or not . . . . . . . . . . 352
-f (compiler option). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 floating-point expressions
far (memory type) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 contracting or not . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
fatal error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 using in preprocessor extensions . . . . . . . . . . . . . . . . . 284
fdopen, in stdio.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 floating-point format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
fegettrapdisable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
fegettrapenable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 implementation-defined behavior . . . . . . . . . . . . . . . . 417
FENV_ACCESS, implementation-defined behavior . . . . 418 implementation-defined behavior in C89 . . . . . . . . . . . 432
fenv.h (library header file) . . . . . . . . . . . . . . . . . . . . . . . . 380 special cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
additional C functionality. . . . . . . . . . . . . . . . . . . . . . . 383 32-bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
fgetpos (library function) 64-bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
implementation-defined behavior in C89 . . . . . . . . . . . 438 floating-point numbers, support for in printf formatters . . 163
implementation-defined behavior. . . . . . . . . . . . . . . . . 425 floating-point status flags . . . . . . . . . . . . . . . . . . . . . . . . . 383
field width, library support for . . . . . . . . . . . . . . . . . . . . . 164 floating-point type, configuring size of double . . . . . . . . . . 57
__FILE__ (predefined symbol) . . . . . . . . . . . . . . . . . . . . . 371 float.h (library header file) . . . . . . . . . . . . . . . . . . . . 380, 386
file buffering, implementation-defined behavior . . . . . . . . 423 FLT_EVAL_METHOD, implementation-defined
behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417, 422, 426

IAR C/C++ Compiler User Guide

450 for MSP430

AFE1_AFE2-1:1
 Index

FLT_ROUNDS, implementation-defined behavior . 417, 426 functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

fmod (library function), implementation-defined calling in different code models . . . . . . . . . . . . . . . . . . 189
behavior in C89 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436, 440 declaring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184, 247
for loops, declarations in . . . . . . . . . . . . . . . . . . . . . . . . . . 197 inlining. . . . . . . . . . . . . . . . . . . . . . . . . 197, 244, 246, 342
formats interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73, 76
floating-point values . . . . . . . . . . . . . . . . . . . . . . . . . . 307 intrinsic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169, 246
standard IEEE (floating point) . . . . . . . . . . . . . . . . . . . 307 monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
_formatted_write (library function) . . . . . . . . . . . . . . . . . 163 omitting type info . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
FP_CONTRACT, pragma directive for . . . . . . . . . . . . . . 352 parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
FP_CONTRACT, implementation-defined behavior . . . . 418 placing in memory . . . . . . . . . . . . . . . . . . . . 236, 239, 298
fragmentation, of heap memory . . . . . . . . . . . . . . . . . . . . . 70 placing segments for . . . . . . . . . . . . . . . . . . . . . . . . . . 104
FRAM memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 recursive
free (library function). See also heap . . . . . . . . . . . . . . . . . 69 avoiding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
fsetpos (library function), implementation-defined storing data on stack . . . . . . . . . . . . . . . . . . . . . . . . . 69
behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425 reentrancy (DLIB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
fstream (library header file) . . . . . . . . . . . . . . . . . . . . . . . 381 related extensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
ftell (library function), implementation-defined behavior return values from . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
in C89 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 special function types. . . . . . . . . . . . . . . . . . . . . . . . . . . 73
ftell (library function), implementation-defined behavior . 425 verifying linked result . . . . . . . . . . . . . . . . . . . . . . . . . 110
Full DLIB (library configuration) . . . . . . . . . . . . . . . . . . . 127 function_effects (pragma directive) . . . . . . . . . . . . . 421, 435
__func__ (predefined symbol) . . . . . . . . . . . . . . . . . 204, 372 function-spec (in stack usage control file). . . . . . . . . . . . . 409
__FUNCTION__ (predefined symbol) . . . . . . . . . . . 204, 372
function calls
calling convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
eliminating overhead of by inlining . . . . . . . . . . . . . . . . 81
G
getchar (library function) . . . . . . . . . . . . . . . . . . . . . . . . . 163
preserved registers across. . . . . . . . . . . . . . . . . . . . . . . 185
getw, in stdio.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
function declarations, Kernighan & Ritchie . . . . . . . . . . . 247
getzone (library function), configuring support for . . . . . . 123
function entrance, preventing registers from being saved . . 74
__get_interrupt_state (intrinsic function) . . . . . . . . . . . . . 362
function execution, in RAM . . . . . . . . . . . . . . . . . . . . . . . . 79
__get_R4_register (intrinsic function) . . . . . . . . . . . . . . . 363
function inlining (compiler transformation) . . . . . . . . . . . 244
__get_R5_register (intrinsic function) . . . . . . . . . . . . . . . 363
disabling (--no_inline) . . . . . . . . . . . . . . . . . . . . . . . . . 287
__get_SP_register (intrinsic function). . . . . . . . . . . . . . . . 363
function pointers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
__get_SR_register (intrinsic function) . . . . . . . . . . . . . . . 364
function prototypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
__get_SR_register_on_exit (intrinsic function) . . . . . . . . 364
enforcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
global arrays, accessing . . . . . . . . . . . . . . . . . . . . . . . . . . 191
function template parameter deduction (extended EC++) . 214
global variables
function type information, omitting in object output . . . . . 291
accessing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
function (pragma directive) . . . . . . . . . . . . . . . . . . . . 421, 435
handled during system termination . . . . . . . . . . . . . . . 137
function (stack usage control directive) . . . . . . . . . . . . . . 407
hints for not using . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
functional (STL header file) . . . . . . . . . . . . . . . . . . . . . . . 382
initialized during system startup . . . . . . . . . . . . . . . . . 136

451

AFE1_AFE2-1:1
 --guard_calls (compiler option). . . . . . . . . . . . . . . . . . . . . 280 HEAP (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
guidelines, reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 heap (zero-sized), implementation-defined behavior . . . . 425
hints

H for good code generation . . . . . . . . . . . . . . . . . . . . . . . 245

implementation-defined behavior . . . . . . . . . . . . . . . . 419
Harbison, Samuel P. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 using efficient data types . . . . . . . . . . . . . . . . . . . . . . . 233
hardware multiplier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 --hw_workaround (compiler option) . . . . . . . . . . . . . . . . . 281
enabling on command line . . . . . . . . . . . . . . . . . . . . . . 285
hardware support in compiler . . . . . . . . . . . . . . . . . . . . . . 116
hash_map (STL header file) . . . . . . . . . . . . . . . . . . . . . . . 382 I
hash_set (STL header file) . . . . . . . . . . . . . . . . . . . . . . . . 382 -I (compiler option). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
__has_constructor, symbol used in library . . . . . . . . . . . . 385 IAR Command Line Build Utility. . . . . . . . . . . . . . . . . . . 125
__has_destructor, symbol used in library . . . . . . . . . . . . . 385 IAR Systems Technical Support . . . . . . . . . . . . . . . . . . . . 261
hdrstop (pragma directive) . . . . . . . . . . . . . . . . . . . . 421, 435 iarbuild.exe (utility) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
header files __iar_cos_accurate (library routine) . . . . . . . . . . . . . . . . . 134
C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 __iar_cos_accuratef (library routine) . . . . . . . . . . . . . . . . 134
C++ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 __iar_cos_accuratef (library function) . . . . . . . . . . . . . . . 378
library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 __iar_cos_accuratel (library routine) . . . . . . . . . . . . . . . . 134
special function registers . . . . . . . . . . . . . . . . . . . . . . . 249 __iar_cos_accuratel (library function) . . . . . . . . . . . . . . . 378
STL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382 __iar_cos_small (library routine) . . . . . . . . . . . . . . . . . . . 133
DLib_Defaults.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 __iar_cos_smallf (library routine) . . . . . . . . . . . . . . . . . . . 133
including stdbool.h for bool . . . . . . . . . . . . . . . . . . . . . 305 __iar_cos_smalll (library routine) . . . . . . . . . . . . . . . . . . . 133
including stddef.h for wchar_t . . . . . . . . . . . . . . . . . . . 305 __IAR_DLIB_PERTHREAD_INIT_SIZE (macro) . . . . . 158
header names, implementation-defined behavior . . . . . . . 420 __IAR_DLIB_PERTHREAD_SIZE (macro) . . . . . . . . . . 158
--header_context (compiler option) . . . . . . . . . . . . . . . . . . 281 __IAR_DLIB_PERTHREAD_SYMBOL_OFFSET
heap (symbolptr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
dynamic memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 __iar_exp_small (library routine) . . . . . . . . . . . . . . . . . . . 133
segments for . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 __iar_exp_smallf (library routine) . . . . . . . . . . . . . . . . . . 133
storing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 __iar_exp_smalll (library routine) . . . . . . . . . . . . . . . . . . 133
VLA allocated on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 __iar_log_small (library routine) . . . . . . . . . . . . . . . . . . . 133
heap segments __iar_log_smallf (library routine) . . . . . . . . . . . . . . . . . . . 133
CLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 __iar_log_smalll (library routine) . . . . . . . . . . . . . . . . . . . 133
DATA16_HEAP (segment) . . . . . . . . . . . . . . . . . . . . . 393 __iar_log10_small (library routine) . . . . . . . . . . . . . . . . . 133
DATA20_HEAP (segment) . . . . . . . . . . . . . . . . . . . . . 396 __iar_log10_smallf (library routine) . . . . . . . . . . . . . . . . . 133
DLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 __iar_log10_smalll (library routine) . . . . . . . . . . . . . . . . . 133
placing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 __iar_Powf (library routine) . . . . . . . . . . . . . . . . . . . . . . . 134
heap size __iar_Powl (library routine) . . . . . . . . . . . . . . . . . . . . . . . 134
and standard I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 __iar_Pow_accurate (library routine) . . . . . . . . . . . . . . . . 134
changing default. . . . . . . . . . . . . . . . . . . . . . . . . . 105–106 __iar_pow_accurate (library routine) . . . . . . . . . . . . . . . . 134

IAR C/C++ Compiler User Guide

452 for MSP430

AFE1_AFE2-1:1
 Index

__iar_Pow_accuratef (library routine) . . . . . . . . . . . . . . . 134 IDE

__iar_pow_accuratef (library routine). . . . . . . . . . . . . . . . 134 building a library from . . . . . . . . . . . . . . . . . . . . . . . . . 125
__iar_pow_accuratef (library function). . . . . . . . . . . . . . . 378 overview of build tools . . . . . . . . . . . . . . . . . . . . . . . . . 39
__iar_Pow_accuratel (library routine). . . . . . . . . . . . . . . . 134 identifiers, implementation-defined behavior in C89 . . . . 430
__iar_pow_accuratel (library routine) . . . . . . . . . . . . . . . . 134 identifiers, implementation-defined behavior . . . . . . . . . . 415
__iar_pow_accuratel (library function) . . . . . . . . . . . . . . . 378 IEEE format, floating-point values . . . . . . . . . . . . . . . . . . 307
__iar_pow_small (library routine) . . . . . . . . . . . . . . . . . . 133 important_typedef (pragma directive) . . . . . . . . . . . . 421, 435
__iar_pow_smallf (library routine) . . . . . . . . . . . . . . . . . . 133 include files
__iar_pow_smalll (library routine) . . . . . . . . . . . . . . . . . . 133 including before source files . . . . . . . . . . . . . . . . . . . . 293
__iar_program_start (label). . . . . . . . . . . . . . . . . . . . . . . . 135 specifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
__iar_Sin (library routine) . . . . . . . . . . . . . . . . . . . . . . . . 133 include_alias (pragma directive) . . . . . . . . . . . . . . . . . . . . 342
__iar_Sinf (library routine) . . . . . . . . . . . . . . . . . . . . . . . . 134 infinity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
__iar_Sinl (library routine) . . . . . . . . . . . . . . . . . . . . . . . . 134 infinity (style for printing), implementation-defined
__iar_Sin_accurate (library routine) . . . . . . . . . . . . . . . . . 134 behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
__iar_sin_accurate (library routine) . . . . . . . . . . . . . . . . . 134 INFO (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
__iar_Sin_accuratef (library routine) . . . . . . . . . . . . . . . . 134 INFOA (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
__iar_sin_accuratef (library routine) . . . . . . . . . . . . . . . . . 134 INFOB (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
__iar_sin_accuratef (library function) . . . . . . . . . . . . . . . . 378 INFOC (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
__iar_Sin_accuratel (library routine) . . . . . . . . . . . . . . . . 134 INFOD (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
__iar_sin_accuratel (library routine) . . . . . . . . . . . . . . . . . 134 information memory, linker segment for. . . . . . . . . . 398–399
__iar_sin_accuratel (library function) . . . . . . . . . . . . . . . . 378 inheritance, in Embedded C++ . . . . . . . . . . . . . . . . . . . . . 205
__iar_Sin_small (library routine) . . . . . . . . . . . . . . . . . . . 133 initialization
__iar_sin_small (library routine). . . . . . . . . . . . . . . . . . . . 133 dynamic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135, 165
__iar_Sin_smallf (library routine) . . . . . . . . . . . . . . . . . . . 133 single-value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
__iar_sin_smallf (library routine) . . . . . . . . . . . . . . . . . . . 133 initializers, static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
__iar_Sin_smalll (library routine) . . . . . . . . . . . . . . . . . . . 133 inline assembler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
__iar_sin_smalll (library routine) . . . . . . . . . . . . . . . . . . . 133 avoiding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
__IAR_SYSTEMS_ICC__ (predefined symbol) . . . . . . . 372 See also assembler language interface
__iar_tan_accurate (library routine) . . . . . . . . . . . . . . . . . 134 inline functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
__iar_tan_accuratef (library routine). . . . . . . . . . . . . . . . . 134 in compiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
__iar_tan_accuratef (library function). . . . . . . . . . . . . . . . 378 inline (pragma directive) . . . . . . . . . . . . . . . . . . . . . . . . . . 342
__iar_tan_accuratel (library routine) . . . . . . . . . . . . . . . . . 134 inlining functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
__iar_tan_accuratel (library function) . . . . . . . . . . . . . . . . 378 implementation-defined behavior . . . . . . . . . . . . . . . . 419
__iar_tan_small (library routine) . . . . . . . . . . . . . . . . . . . 133 installation directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
__iar_tan_smallf (library routine) . . . . . . . . . . . . . . . . . . . 133 instantiate (pragma directive) . . . . . . . . . . . . . . . . . . 421, 435
__iar_tan_smalll (library routine) . . . . . . . . . . . . . . . . . . . 133 int (data type) signed and unsigned . . . . . . . . . . . . . . . . . . 304
iccbutl.h (library header file) . . . . . . . . . . . . . . . . . . . . . . 386 integer types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
icons, in this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 casting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
implementation-defined behavior . . . . . . . . . . . . . . . . 417
implementation-defined behavior in C89 . . . . . . . . . . . 431

453

AFE1_AFE2-1:1
 intptr_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 iostream (library header file). . . . . . . . . . . . . . . . . . . . . . . 381
ptrdiff_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 IPE (Intellectual Property Encapsulation) . . . . . . . . . . . . . 153
size_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 IPECODE16 (segment). . . . . . . . . . . . . . . . . . . . . . . . . . . 400
uintptr_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 IPEDATA16_C (segment) . . . . . . . . . . . . . . . . . . . . . . . . 401
integral promotion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 IPEDATA16_N (segment) . . . . . . . . . . . . . . . . . . . . . . . . 401
Intellectual Property Encapsulation (IPE) . . . . . . . . . . . . . 153 IPESIGNATURE (segment) . . . . . . . . . . . . . . . . . . . . . . . 401
internal error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 IPE_B1 (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
__interrupt (extended keyword) . . . . . . . . . . . . . . . . . 74, 323 IPE_B2 (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
using in pragma directives . . . . . . . . . . . . . . . . . . . . . . 354 iso646.h (library header file) . . . . . . . . . . . . . . . . . . . . . . . 380
interrupt functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 ISR_CODE (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
for MSP430X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 using . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
placement in memory . . . . . . . . . . . . . . . . . . . . . . . . . . 107 istream (library header file). . . . . . . . . . . . . . . . . . . . . . . . 381
interrupt handler. See interrupt service routine italic style, in this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
interrupt service routine . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 iterator (STL header file) . . . . . . . . . . . . . . . . . . . . . . . . . 382
interrupt state, restoring . . . . . . . . . . . . . . . . . . . . . . . . . . 366 I/O register. See SFR
interrupt vector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 I/O, character-based . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
specifying with pragma directive . . . . . . . . . . . . . . . . . 354 I2C (I2CIV) module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Interrupt Vector Generators, writing interrupt service
routines for . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
interrupt vector table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 J
in linker configuration file . . . . . . . . . . . . . . . . . . . . . . 107 JTAGSIGNATURE (segment) . . . . . . . . . . . . . . . . . . . . . 402
INTVEC segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
interrupts
disabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
during function execution . . . . . . . . . . . . . . . . . . . . . 76
K
keep_definition (pragma directive) . . . . . . . . . . . . . . 421, 435
processor state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Kernighan & Ritchie function declarations . . . . . . . . . . . . 247
using with C++ destructors . . . . . . . . . . . . . . . . . . . . . 212
disallowing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
intptr_t (integer type) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
__intrinsic (extended keyword). . . . . . . . . . . . . . . . . . . . . 324
extended, overview of . . . . . . . . . . . . . . . . . . . . . . . . . . 42
intrinsic functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
intrinsics.h (header file) . . . . . . . . . . . . . . . . . . . . . . . . . . 355
L
-l (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
inttypes.h (library header file) . . . . . . . . . . . . . . . . . . . . . . 380
for creating skeleton code . . . . . . . . . . . . . . . . . . . . . . 179
INTVEC (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . 107, 399
labels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
intwri.c (library source code) . . . . . . . . . . . . . . . . . . . . . . 164
assembler, making public . . . . . . . . . . . . . . . . . . . . . . . 294
invocation syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
__iar_program_start . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
iomanip (library header file) . . . . . . . . . . . . . . . . . . . . . . . 381
__program_start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
ios (library header file) . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Labrosse, Jean J. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
iosfwd (library header file) . . . . . . . . . . . . . . . . . . . . . . . . 381

IAR C/C++ Compiler User Guide

454 for MSP430

AFE1_AFE2-1:1
 Index

language extensions linker. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Embedded C++ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 linker configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
enabling using pragma . . . . . . . . . . . . . . . . . . . . . . . . . 343 for placing code and data . . . . . . . . . . . . . . . . . . . . . . . . 88
enabling (-e) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 in depth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
language overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 overview of . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
language (pragma directive) . . . . . . . . . . . . . . . . . . . . . . . 343 using the -P command . . . . . . . . . . . . . . . . . . . . . . . . . 103
Large (code model) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 using the -Z command . . . . . . . . . . . . . . . . . . . . . . . . . 103
Large (data model) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 linker map file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
_large_write (library function) . . . . . . . . . . . . . . . . . . . . . 163 linker options
libraries typographic convention . . . . . . . . . . . . . . . . . . . . . . . . . 34
reason for using . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 -Q. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
standard template library . . . . . . . . . . . . . . . . . . . . . . . 382 linker segment. See segment
using a prebuilt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 linking
using a prebuilt (CLIB) . . . . . . . . . . . . . . . . . . . . . . . . 161 from the command line . . . . . . . . . . . . . . . . . . . . . . . . . 54
library configuration files in the build process . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
DLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
DLib_Defaults.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 process for . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
modifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 list (STL header file) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
specifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 listing, generating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
library documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 literals, compound. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
library features, missing from Embedded C++ . . . . . . . . . 206 literature, recommended . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
library functions local variables, See auto variables
summary, CLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386 locale
summary, DLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 adding support for in library . . . . . . . . . . . . . . . . . . . . 150
online help for . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 changing at runtime . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
library header files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 implementation-defined behavior . . . . . . . . . . . . 416, 427
library modules removing support for . . . . . . . . . . . . . . . . . . . . . . . . . . 150
creating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 support for . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
overriding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 locale.h (library header file) . . . . . . . . . . . . . . . . . . . . . . . 380
library object files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 located data segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
library project, building using a template . . . . . . . . . . . . . 125 located data, declaring extern . . . . . . . . . . . . . . . . . . . . . . 238
library_default_requirements (pragma directive) . . . 421, 435 location (pragma directive) . . . . . . . . . . . . . . . . . . . . 237, 344
--library_module (compiler option) . . . . . . . . . . . . . . . . . 283 --lock_r4 (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . 283
library_provides (pragma directive) . . . . . . . . . . . . . 421, 435 --lock_r5 (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . 283
library_requirement_override (pragma directive) . . . 421, 436 log (library routine). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
lightbulb icon, in this guide. . . . . . . . . . . . . . . . . . . . . . . . . 34 logf (library routine) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
limits.h (library header file) . . . . . . . . . . . . . . . . . . . 380, 386 logl (library routine) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
__LINE__ (predefined symbol) . . . . . . . . . . . . . . . . . . . . 372 log10 (library routine) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
linkage, C and C++ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 log10f (library routine) . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

455

AFE1_AFE2-1:1
 log10l (library routine) . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 implementation-defined behavior in C89 . . . . . . . 438, 441
long double (data type) . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 Mann, Bernhard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
long float (data type), synonym for double . . . . . . . . . . . . 202 map (STL header file) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
long long (data type) map, linker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
avoiding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 math functions rounding mode,
restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 implementation-defined behavior . . . . . . . . . . . . . . . . . . . 426
long long (data type), signed and unsigned . . . . . . . . . . . . 304 math functions (library functions) . . . . . . . . . . . . . . . . . . . 131
long (data type), signed and unsigned . . . . . . . . . . . . . . . . 304 MathLib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
longjmp, restrictions for using . . . . . . . . . . . . . . . . . . . . . 379 math.h (library header file) . . . . . . . . . . . . . . . . . . . . 380, 386
loop unrolling (compiler transformation) . . . . . . . . . . . . . 244 max recursion depth (stack usage control directive) . . . . . 407
disabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 MB_LEN_MAX, implementation-defined behavior . . . . . 426
#pragma unroll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 Medium (data model) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
loop-invariant expressions . . . . . . . . . . . . . . . . . . . . . . . . 244 _medium_write (library function) . . . . . . . . . . . . . . . . . . . 163
__low_level_init . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 memory
customizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 accessing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56, 60, 191
initialization phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 using data16 method . . . . . . . . . . . . . . . . . . . . . . . . 192
low_level_init.c . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135, 165 using data20 method . . . . . . . . . . . . . . . . . . . . . . . . 192
__low_power_mode_n (intrinsic function) . . . . . . . . . . . . 364 allocating in C++ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
__low_power_mode_off_on_exit (intrinsic function) . . . . 364 dynamic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
low-level processor operations . . . . . . . . . . . . . . . . . . . . . 198 heap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
accessing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 non-initialized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
RAM, saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
releasing in C++. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
M stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
macros saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
embedded in #pragma optimize . . . . . . . . . . . . . . . . . . 346 used by global or static variables . . . . . . . . . . . . . . . . . . 60
ERANGE (in errno.h) . . . . . . . . . . . . . . . . . . . . . 422, 436 memory clobber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
inclusion of assert . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 memory consumption, reducing . . . . . . . . . . . . . . . . . . . . 163
NULL, implementation-defined behavior . . . . . . . . . . 423 memory management, type-safe . . . . . . . . . . . . . . . . . . . . 205
in C89 for CLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 memory map
in C89 for DLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . 436 initializing SFRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
substituted in #pragma directives . . . . . . . . . . . . . . . . . 198 linker configuration for . . . . . . . . . . . . . . . . . . . . . . . . 101
variadic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 memory placement
--macro_positions_in_diagnostics (compiler option) . . . . 284 of linker segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
main (function) using type definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
definition (C89) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429 Memory Protection Unit (MPU) . . . . . . . . . . . . . . . . . . . . 152
implementation-defined behavior . . . . . . . . . . . . . . . . 414 memory segment. See segment
malloc (library function) memory types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
See also heap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 C++ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
placing variables in . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

IAR C/C++ Compiler User Guide

456 for MSP430

AFE1_AFE2-1:1
 Index

pointers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 supported devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

specifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 MSP430X
structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 code models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 data models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
memory (pragma directive) . . . . . . . . . . . . . . . . . . . . 421, 436 interrupt functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
memory (STL header file) . . . . . . . . . . . . . . . . . . . . . . . . 382 support for . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
__memory_of multibyte character support . . . . . . . . . . . . . . . . . . . . . . . . 279
operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 multibyte characters, implementation-defined
symbol used in library . . . . . . . . . . . . . . . . . . . . . . . . . 385 behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415, 427
message (pragma directive) . . . . . . . . . . . . . . . . . . . . . . . 344 multiple inheritance
messages in Extended EC++ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
disabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 missing from Embedded C++ . . . . . . . . . . . . . . . . . . . 206
forcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 --multiplier (compiler option) . . . . . . . . . . . . . . . . . . . . . . 285
Meyers, Scott . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 multithreaded environment . . . . . . . . . . . . . . . . . . . . . . . . 154
--mfc (compiler option). . . . . . . . . . . . . . . . . . . . . . . . . . . 284 multi-file compilation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
--migration_preprocessor_extensions (compiler option) . . 284 mutable attribute, in Extended EC++ . . . . . . . . . . . . 206, 218
migration, from earlier IAR compilers . . . . . . . . . . . . . . . . 32
MISRA C, documentation . . . . . . . . . . . . . . . . . . . . . . . . . 32
--misrac (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . 267 N
--misrac_verbose (compiler option) . . . . . . . . . . . . . . . . . 267 name (in stack usage control file) . . . . . . . . . . . . . . . . . . . 410
--misrac1998 (compiler option) . . . . . . . . . . . . . . . . . . . . 267 names block (call frame information) . . . . . . . . . . . . . . . . 193
--misrac2004 (compiler option) . . . . . . . . . . . . . . . . . . . . 267 namespace support
mode changing, implementation-defined behavior . . . . . . 424 in Extended EC++ . . . . . . . . . . . . . . . . . . . . . . . . 206, 218
module consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 missing from Embedded C++ . . . . . . . . . . . . . . . . . . . 206
rtmodel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 naming conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
module map, in linker map file . . . . . . . . . . . . . . . . . . . . . 111 NaN
module name, specifying (--module_name) . . . . . . . . . . . 285 implementation of . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
module summary, in linker map file . . . . . . . . . . . . . . . . . 111 implementation-defined behavior . . . . . . . . . . . . . . . . 424
--module_name (compiler option) . . . . . . . . . . . . . . . . . . 285 native environment,
module_name (pragma directive) . . . . . . . . . . . . . . . 421, 436 implementation-defined behavior . . . . . . . . . . . . . . . . . . . 428
module-spec (in stack usage control file) . . . . . . . . . . . . . 410 NDEBUG (preprocessor symbol) . . . . . . . . . . . . . . . . . . . 375
__monitor (extended keyword) . . . . . . . . . . . . . . . . . . . . . 324 near (memory type). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
monitor functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76, 324 new operator (extended EC++) . . . . . . . . . . . . . . . . . . . . . 211
MPU (Memory Protection Unit) . . . . . . . . . . . . . . . . . . . . 152 new (keyword) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
MPU_B1 (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 new (library header file) . . . . . . . . . . . . . . . . . . . . . . . . . . 381
MPU_B2 (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 no calls from (stack usage control directive) . . . . . . . . . . . 408
MSP430 non-initialized variables, hints for . . . . . . . . . . . . . . . . . . . 251
information memory . . . . . . . . . . . . . . . . . . . . . . 398–399 non-scalar parameters, avoiding . . . . . . . . . . . . . . . . . . . . 246
memory access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 NOP (assembler instruction) . . . . . . . . . . . . . . . . . . . . . . . 364

457

AFE1_AFE2-1:1
 __noreturn (extended keyword) . . . . . . . . . . . . . . . . . . . . 327
Normal DLIB (library configuration) . . . . . . . . . . . . . . . . 127 O
Not a number (NaN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 -O (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
__no_alloc (extended keyword) . . . . . . . . . . . . . . . . . . . . 324 -o (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
__no_alloc_str (operator) . . . . . . . . . . . . . . . . . . . . . . . . . 325 object attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
__no_alloc_str16 (operator) . . . . . . . . . . . . . . . . . . . . . . . 325 object filename, specifying (-o) . . . . . . . . . . . . . . . . . . . . 292
__no_alloc16 (extended keyword) . . . . . . . . . . . . . . . . . . 324 object module name, specifying (--module_name) . . . . . . 285
--no_call_frame_info (compiler option) . . . . . . . . . . . . . . 286 object_attribute (pragma directive) . . . . . . . . . . . . . . 251, 345
--no_code_motion (compiler option) . . . . . . . . . . . . . . . . 286 offsetof . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
no_crosscall (#pragma optimize parameter) . . . . . . . . . . . 346 --omit_types (compiler option) . . . . . . . . . . . . . . . . . . . . . 291
no_crossjump (#pragma optimize parameter) . . . . . . . . . . 346 once (pragma directive) . . . . . . . . . . . . . . . . . . . . . . 421, 436
--no_cse (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . 286 --only_stdout (compiler option) . . . . . . . . . . . . . . . . . . . . 292
no_epilogue (pragma directive) . . . . . . . . . . . . . . . . . . . . 345 operators
__no_init (extended keyword) . . . . . . . . . . . . . . . . . 251, 326 See also @ (operator)
--no_inline (compiler option) . . . . . . . . . . . . . . . . . . . . . . 287 for cast
__no_multiplier (extended keyword) . . . . . . . . . . . . . . . . 326 in Extended EC++. . . . . . . . . . . . . . . . . . . . . . . . . . 206
__no_operation (intrinsic function) . . . . . . . . . . . . . . . . . . 364 missing from Embedded C++ . . . . . . . . . . . . . . . . . 206
--no_path_in_file_macros (compiler option). . . . . . . . . . . 287 for segment control . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
no_pch (pragma directive) . . . . . . . . . . . . . . . . . . . . 421, 436 new and delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
__no_pic (extended keyword) . . . . . . . . . . . . . . . . . . . . . . 326 precision for 32-bit float . . . . . . . . . . . . . . . . . . . . . . . 308
--no_rw_dynamic_init (compiler option) . . . . . . . . . . . . . 287 precision for 64-bit float . . . . . . . . . . . . . . . . . . . . . . . 308
--no_size_constraints (compiler option) . . . . . . . . . . . . . . 288 sizeof, implementation-defined behavior . . . . . . . . . . . 427
--no_static_destruction (compiler option) . . . . . . . . . . . . . 288 variants for cast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
--no_system_include (compiler option) . . . . . . . . . . . . . . 288 _Pragma (preprocessor) . . . . . . . . . . . . . . . . . . . . . . . . 197
--no_tbaa (compiler option) . . . . . . . . . . . . . . . . . . . . . . . 289 __ALIGNOF__, for alignment control. . . . . . . . . . . . . 200
--no_typedefs_in_diagnostics (compiler option) . . . . . . . . 289 __memory_of. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
--no_ubrof_messages (compiler option) . . . . . . . . . . . . . . 290 ?, language extensions for . . . . . . . . . . . . . . . . . . . . . . 219
--no_unroll (compiler option) . . . . . . . . . . . . . . . . . . . . . . 290 optimization
--no_warnings (compiler option) . . . . . . . . . . . . . . . . . . . 290 code motion, disabling . . . . . . . . . . . . . . . . . . . . . . . . . 286
--no_wrap_diagnostics (compiler option) . . . . . . . . . . . . . 290 common sub-expression elimination, disabling . . . . . . 286
NULL configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
implementation-defined behavior . . . . . . . . . . . . . . . . 423 disabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
implementation-defined behavior in C89 (CLIB) . . . . 439 function inlining, disabling (--no_inline) . . . . . . . . . . . 287
implementation-defined behavior in C89 (DLIB) . . . . 436 hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
in library header file (CLIB) . . . . . . . . . . . . . . . . . . . . 386 loop unrolling, disabling . . . . . . . . . . . . . . . . . . . . . . . 290
pointer constant, relaxation to Standard C . . . . . . . . . . 202 specifying (-O) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
numeric conversion functions, implementation-defined techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428 type-based alias analysis, disabling (--tbaa) . . . . . . . . . 289
numeric (STL header file) . . . . . . . . . . . . . . . . . . . . . . . . . 382 using pragma directive . . . . . . . . . . . . . . . . . . . . . . . . . 346

IAR C/C++ Compiler User Guide

458 for MSP430

AFE1_AFE2-1:1
 Index

optimization levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 differences between . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

optimize (pragma directive) . . . . . . . . . . . . . . . . . . . . . . . 346 mixing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
option parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 pointers
options, compiler. See compiler options casting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63, 310
__op_code (intrinsic function) . . . . . . . . . . . . . . . . . . . . . 364 data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Oram, Andy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
ostream (library header file) . . . . . . . . . . . . . . . . . . . . . . . 381 implementation-defined behavior . . . . . . . . . . . . . . . . 418
output implementation-defined behavior in C89 . . . . . . . . . . . 433
from preprocessor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 polymorphism, in Embedded C++ . . . . . . . . . . . . . . . . . . 205
specifying for linker . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 porting, code containing pragma directives . . . . . . . . . . . . 333
supporting non-standard. . . . . . . . . . . . . . . . . . . . . . . . 164 __POSITION_INDEPENDENT_CODE__ (predefined
--output (compiler option). . . . . . . . . . . . . . . . . . . . . . . . . 292 symbol) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
overhead, reducing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 position-independent code and read-only data (ROPI) . . . . 80
possible calls (stack usage control directive) . . . . . . . . . . 408
pow (library routine) . . . . . . . . . . . . . . . . . . . . . . . . . 133–134
P alternative implementation of . . . . . . . . . . . . . . . . . . . 378
pack (pragma directive) . . . . . . . . . . . . . . . . . . . . . . 311, 347 powf (library routine) . . . . . . . . . . . . . . . . . . . . . . . . 133–134
packed structure types . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 powl (library routine) . . . . . . . . . . . . . . . . . . . . . . . . 133–134
parameters pragma directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 basic_template_matching, using . . . . . . . . . . . . . . . . . 215
non-scalar, avoiding . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 for absolute located data . . . . . . . . . . . . . . . . . . . . . . . 237
register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185–186 list of all recognized . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
rules for specifying a file or directory . . . . . . . . . . . . . 264 list of all recognized (C89). . . . . . . . . . . . . . . . . . . . . . 435
specifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311, 347
stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185–186 _Pragma (preprocessor operator) . . . . . . . . . . . . . . . . . . . 197
typographic convention . . . . . . . . . . . . . . . . . . . . . . . . . 34 precision arguments, library support for . . . . . . . . . . . . . . 164
part number, of this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 predefined symbols
--pending_instantiations (compiler option) . . . . . . . . . . . . 292 overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
permanent registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
perror (library function), --predef_macro (compiler option) . . . . . . . . . . . . . . . . . . . 293
implementation-defined behavior in C89 . . . . . . . . . 438, 441 --preinclude (compiler option) . . . . . . . . . . . . . . . . . . . . . 293
__persistent (extended keyword) . . . . . . . . . . . . . . . . . . . 327 --preprocess (compiler option) . . . . . . . . . . . . . . . . . . . . . 293
cannot be used with ROPI . . . . . . . . . . . . . . . . . . . . . . . 80 preprocessor
placement operator (_Pragma) . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
in named segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
of code and data, introduction to . . . . . . . . . . . . . . . . . . 88 preprocessor directives
plain char, implementation-defined behavior . . . . . . . . . . 416 comments at the end of . . . . . . . . . . . . . . . . . . . . . . . . 203
pointer types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 implementation-defined behavior . . . . . . . . . . . . . . . . 420
implementation-defined behavior in C89 . . . . . . . . . . . 434

459

AFE1_AFE2-1:1
 #pragma . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 putw, in stdio.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
preprocessor extensions
compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
__VA_ARGS__ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Q
#warning message . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 -Q (linker option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
preprocessor symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 qualifiers
defining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 const and volatile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
preserved registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 implementation-defined behavior . . . . . . . . . . . . . . . . 420
__PRETTY_FUNCTION__ (predefined symbol). . . . . . . 373 implementation-defined behavior in C89 . . . . . . . . . . . 434
primitives, for special functions . . . . . . . . . . . . . . . . . . . . . 73 queue (STL header file) . . . . . . . . . . . . . . . . . . . . . . . . . . 382
print formatter, selecting . . . . . . . . . . . . . . . . . . . . . . . . . . 130
printf (library function) . . . . . . . . . . . . . . . . . . . . . . . 129, 163
choosing formatter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
configuration symbols . . . . . . . . . . . . . . . . . . . . . . . . . 148
R
-r (compiler option). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
customizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 RAM
implementation-defined behavior . . . . . . . . . . . . . . . . 425 function execution in . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
implementation-defined behavior in C89 . . . . . . . 438, 441 initializers copied from ROM . . . . . . . . . . . . . . . . . . . . 52
selecting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 saving memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
__printf_args (pragma directive). . . . . . . . . . . . . . . . . . . . 348 __ramfunc (extended keyword) . . . . . . . . . . . . . . . . . . . . 327
printing characters, implementation-defined behavior . . . 427 cannot be used with ROPI . . . . . . . . . . . . . . . . . . . . . . . 80
processor configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 range errors, in linker . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
processor operations __raw (extended keyword) . . . . . . . . . . . . . . . . . . . . . . . . 328
accessing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
low-level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 read formatter, selecting . . . . . . . . . . . . . . . . . . . . . . 131, 165
program entry label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 reading guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
program termination, implementation-defined behavior . . 414 reading, recommended . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
programming hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 realloc (library function) . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
__program_start (label) . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 implementation-defined behavior in C89 . . . . . . . 438, 441
projects See also heap
basic settings for . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 recursive functions
setting up for a library . . . . . . . . . . . . . . . . . . . . . . . . . 125 avoiding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
prototypes, enforcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 storing data on stack . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
ptrdiff_t (integer type) . . . . . . . . . . . . . . . . . . . . . . . 310, 386 --reduce_stack_usage (compiler option) . . . . . . . . . . . . . . 294
PUBLIC (assembler directive) . . . . . . . . . . . . . . . . . . . . . 294 reentrancy (DLIB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
publication date, of this guide . . . . . . . . . . . . . . . . . . . . . . . . 2 reference information, typographic convention . . . . . . . . . . 34
--public_equ (compiler option) . . . . . . . . . . . . . . . . . . . . . 294 register keyword, implementation-defined behavior . . . . . 419
public_equ (pragma directive) . . . . . . . . . . . . . . . . . . . . . 348 register parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 185–186
putchar (library function) . . . . . . . . . . . . . . . . . . . . . . . . . 163 registered trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
putenv (library function), absent from DLIB . . . . . . . . . . 141

IAR C/C++ Compiler User Guide

460 for MSP430

AFE1_AFE2-1:1
 Index

registers implementation-defined behavior in C89 (CLIB) . . . . 441

assigning to parameters . . . . . . . . . . . . . . . . . . . . . . . . 186 implementation-defined behavior in C89 (DLIB) . . . . 438
callee-save, stored on stack . . . . . . . . . . . . . . . . . . . . . . 68 remquo, magnitude of . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
for function returns . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 rename (library function)
implementation-defined behavior in C89 . . . . . . . . . . . 433 implementation-defined behavior . . . . . . . . . . . . . . . . 424
in assembler-level routines. . . . . . . . . . . . . . . . . . . . . . 181 implementation-defined behavior in C89 (CLIB) . . . . 441
not saving at function entrance . . . . . . . . . . . . . . . . . . . 74 implementation-defined behavior in C89 (DLIB) . . . . 438
preserved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 __ReportAssert (library function) . . . . . . . . . . . . . . . . . . . 145
R4 required (pragma directive) . . . . . . . . . . . . . . . . . . . . . . . . 348
excluding from use (--lock_R4) . . . . . . . . . . . . . . . 283 --require_prototypes (compiler option) . . . . . . . . . . . . . . . 296
getting the value of (__get_R4_register) . . . . . . . . . 363 RESET (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
reserving for register variables (--regvar_R4) . . . . . 294 restrict keyword, enabling . . . . . . . . . . . . . . . . . . . . . . . . . 279
writing to (__set_R4_register) . . . . . . . . . . . . . . . . 366 return values, from functions . . . . . . . . . . . . . . . . . . . . . . 187
R5 ROM calling convention . . . . . . . . . . . . . . . . . . . . . . . . . . 182
excluding from use (--lock_R5) . . . . . . . . . . . . . . . 283 __root (extended keyword) . . . . . . . . . . . . . . . . . . . . . . . . 329
getting the value of (__get_R5_register) . . . . . . . . . 363 ROPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
reserving for register variables (--regvar_R5) . . . . . 295 __ROPI__ (predefined symbol) . . . . . . . . . . . . . . . . . . . . 373
writing to (__set_R5_register) . . . . . . . . . . . . . . . . 366 --ropi (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . . 296
scratch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 routines, time-critical . . . . . . . . . . . . . . . . . . . . . . . . 169, 198
SP __ro_placement (extended keyword) . . . . . . . . . . . . . . . . 329
getting the value of (__get_SP_register) . . . . . . . . . 363 rtmodel (assembler directive) . . . . . . . . . . . . . . . . . . . . . . 112
writing to (__set_SP_register). . . . . . . . . . . . . . . . . 367 rtmodel (pragma directive) . . . . . . . . . . . . . . . . . . . . . . . . 349
SR rtti support, missing from STL . . . . . . . . . . . . . . . . . . . . . 207
getting the value of on exit . . . . . . . . . . . . . . . . . . . 364 __rt_version (runtime model attribute) . . . . . . . . . . . . . . . 113
getting the value of (__get_SR_register) . . . . . . . . . 364 runtime environment
__REGISTER_MODEL__ (predefined symbol) . . . . . . . 373 CLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
__REGISTER_R4__ (predefined symbol) . . . . . . . . . . . . 373 DLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
__REGISTER_R5__ (predefined symbol) . . . . . . . . . . . . 373 setting up (DLIB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
REGVAR_AN (segment) . . . . . . . . . . . . . . . . . . . . . . . . . 402 runtime libraries (CLIB)
--regvar_r4 (compiler option) . . . . . . . . . . . . . . . . . . . . . . 294 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
--regvar_r5 (compiler option) . . . . . . . . . . . . . . . . . . . . . . 295 filename syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
reinterpret_cast (cast operator) . . . . . . . . . . . . . . . . . . . . . 206 using prebuilt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
--relaxed_fp (compiler option) . . . . . . . . . . . . . . . . . . . . . 295 runtime libraries (DLIB)
remark (diagnostic message) . . . . . . . . . . . . . . . . . . . . . . . 260 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
classifying for compiler . . . . . . . . . . . . . . . . . . . . . . . . 274 customizing system startup code . . . . . . . . . . . . . . . . . 138
enabling in compiler . . . . . . . . . . . . . . . . . . . . . . . . . . 296 filename syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
--remarks (compiler option) . . . . . . . . . . . . . . . . . . . . . . . 296 overriding modules in . . . . . . . . . . . . . . . . . . . . . . . . . 123
remove (library function) using prebuilt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
implementation-defined behavior . . . . . . . . . . . . . . . . 424 runtime model attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 111

461

AFE1_AFE2-1:1
 runtime model definitions . . . . . . . . . . . . . . . . . . . . . . . . . 349 placing in sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
runtime type information, missing from Embedded C++ . 206 specifying (--segment) . . . . . . . . . . . . . . . . . . . . . . . . . 297
R4. See registers summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
R5. See registers too long for address range . . . . . . . . . . . . . . . . . . . . . . 110
too long, in linker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

S __segment_begin (extended operator) . . . . . . . . . . . . . . . 201

__segment_end (extended operator) . . . . . . . . . . . . . . . . . 201
__saturated_add_signed_type (intrinsic function) . . . . . . . 365 __segment_size (extended operator) . . . . . . . . . . . . . . . . . 201
__saturated_add_unsigned_type (intrinsic function) . . . . . 365 semaphores
__saturated_sub_signed_type (intrinsic function) . . . . . . . 365 C example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
__saturated_sub_unsigned_type (intrinsic function) . . . . . 365 C++ example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
--save_reg20 (compiler option) . . . . . . . . . . . . . . . . . . . . . 297 operations on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
scanf (library function) set (STL header file) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
choosing formatter (CLIB). . . . . . . . . . . . . . . . . . . . . . 164 setjmp.h (library header file) . . . . . . . . . . . . . . . . . . . 380, 386
choosing formatter (DLIB) . . . . . . . . . . . . . . . . . . . . . 130 setlocale (library function) . . . . . . . . . . . . . . . . . . . . . . . . 151
configuration symbols . . . . . . . . . . . . . . . . . . . . . . . . . 148 settings, basic for project configuration . . . . . . . . . . . . . . . 54
implementation-defined behavior . . . . . . . . . . . . . . . . 425 __set_interrupt_state (intrinsic function) . . . . . . . . . . . . . 366
implementation-defined behavior in C89 . . . . . . . . . . . 441 __set_R4_register (intrinsic function) . . . . . . . . . . . . . . . . 366
implementation-defined behavior in C89 (CLIB) . . . . 441 __set_R5_register (intrinsic function) . . . . . . . . . . . . . . . . 366
implementation-defined behavior in C89 (DLIB) . . . . 438 __set_SP_register (intrinsic function) . . . . . . . . . . . . . . . . 367
__scanf_args (pragma directive) . . . . . . . . . . . . . . . . . . . . 350 severity level, of diagnostic messages . . . . . . . . . . . . . . . . 260
scratch registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 specifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
section (pragma directive). . . . . . . . . . . . . . . . . . . . . . . . . 350 SFR
segment group name . . . . . . . . . . . . . . . . . . . . . . . . . . 90, 297 accessing special function registers . . . . . . . . . . . . . . . 249
segment map, in linker map file . . . . . . . . . . . . . . . . . . . . 110 declaring extern special function registers . . . . . . . . . . 238
segment memory types, in XLINK . . . . . . . . . . . . . . . . . . . 86 shared object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
--segment (compiler option) . . . . . . . . . . . . . . . . . . . . . . . 297 short (data type) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
segment (pragma directive) . . . . . . . . . . . . . . . . . . . . . . . . 350 signal (library function)
segments implementation-defined behavior . . . . . . . . . . . . . . . . 423
allocation of . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 implementation-defined behavior in C89 . . . . . . . . . . . 437
CODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 signals, implementation-defined behavior. . . . . . . . . . . . . 414
CODE16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 at system startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
declaring (#pragma segment) . . . . . . . . . . . . . . . . . . . . 351 signal.h (library header file) . . . . . . . . . . . . . . . . . . . . . . . 380
definition of . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 SIGNATURE (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . 403
HEAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 signed char (data type) . . . . . . . . . . . . . . . . . . . . . . . 304–305
ISR_CODE, for interrupt functions (MSP430X) . . . . . 107 specifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
located data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 signed int (data type). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 signed long long (data type) . . . . . . . . . . . . . . . . . . . . . . . 304
packing in memory . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 signed long (data type) . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

IAR C/C++ Compiler User Guide

462 for MSP430

AFE1_AFE2-1:1
 Index

signed short (data type) . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 stack segments

--silent (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . 299 CSTACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
silent operation, specifying in compiler . . . . . . . . . . . . . . 299 placing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
sin (library function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 stack (STL header file) . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
sin (library routine) . . . . . . . . . . . . . . . . . . . . . . . . . . 133–134 stack-size (in stack usage control file) . . . . . . . . . . . . . . . 411
sinf (library routine) . . . . . . . . . . . . . . . . . . . . . . . . . 133–134 Standard C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
sinl (library routine) . . . . . . . . . . . . . . . . . . . . . . . . . 133–134 library compliance with . . . . . . . . . . . . . . . . . . . . . . . . 377
64-bits (floating-point format) . . . . . . . . . . . . . . . . . . . . . 308 specifying strict usage . . . . . . . . . . . . . . . . . . . . . . . . . 299
size (in stack usage control file) . . . . . . . . . . . . . . . . . . . . 411 standard error
sizeof, using in preprocessor extensions . . . . . . . . . . . . . . 284 redirecting in compiler . . . . . . . . . . . . . . . . . . . . . . . . . 292
size_t (integer type) . . . . . . . . . . . . . . . . . . . . . . . . . 310, 386 See also diagnostic messages . . . . . . . . . . . . . . . . . . . . 258
skeleton code, creating for assembler language interface . 178 standard output, specifying in compiler . . . . . . . . . . . . . . 292
slist (STL header file) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382 standard template library (STL)
Small (code model) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 in C++ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Small (data model) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 in Extended EC++ . . . . . . . . . . . . . . . . . . . . . . . . 206, 214
_small_write (library function) . . . . . . . . . . . . . . . . . . . . . 164 missing from Embedded C++ . . . . . . . . . . . . . . . . . . . 206
source files, list all referred . . . . . . . . . . . . . . . . . . . . . . . . 281 startup code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
space characters, implementation-defined behavior . . . . . 423 cstartup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
special function registers (SFR) . . . . . . . . . . . . . . . . . . . . 249 placement of . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
special function types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 startup system. See system startup
sprintf (library function) . . . . . . . . . . . . . . . . . . . . . . 129, 163 statements, implementation-defined behavior in C89 . . . . 434
choosing formatter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 static analysis, documentation for . . . . . . . . . . . . . . . . . . . . 32
customizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 static data, in configuration file . . . . . . . . . . . . . . . . . . . . . 104
SP. See registers static variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
sscanf (library function) taking the address of . . . . . . . . . . . . . . . . . . . . . . . . . . 246
choosing formatter (CLIB). . . . . . . . . . . . . . . . . . . . . . 164 static_assert() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
choosing formatter (DLIB) . . . . . . . . . . . . . . . . . . . . . 130 static_cast (cast operator) . . . . . . . . . . . . . . . . . . . . . . . . . 206
sstream (library header file) . . . . . . . . . . . . . . . . . . . . . . . 381 status flags for floating-point . . . . . . . . . . . . . . . . . . . . . . 383
stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 std namespace, missing from EC++
advantages and problems using . . . . . . . . . . . . . . . . . . . 69 and Extended EC++ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
cleaning after function return . . . . . . . . . . . . . . . . . . . . 187 stdarg.h (library header file) . . . . . . . . . . . . . . . . . . . 380, 386
contents of . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 stdbool.h (library header file) . . . . . . . . . . . . . . 305, 380, 386
layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 __STDC__ (predefined symbol) . . . . . . . . . . . . . . . . . . . . 373
saving space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 STDC CX_LIMITED_RANGE (pragma directive) . . . . . 351
setting up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 STDC FENV_ACCESS (pragma directive) . . . . . . . . . . . 352
size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 STDC FP_CONTRACT (pragma directive) . . . . . . . . . . . 352
stack parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185–186 __STDC_VERSION__ (predefined symbol) . . . . . . . . . . 374
stack pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 stddef.h (library header file) . . . . . . . . . . . . . . . 305, 380, 386
stderr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122, 292
stdin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

463

AFE1_AFE2-1:1
 implementation-defined behavior in C89 (CLIB) . . . . 440 anonymous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200, 235
implementation-defined behavior in C89 (DLIB) . . . . 437 implementation-defined behavior . . . . . . . . . . . . . . . . 419
stdint.h (library header file) . . . . . . . . . . . . . . . . . . . 380, 383 implementation-defined behavior in C89 . . . . . . . . . . . 433
stdio.h (library header file) . . . . . . . . . . . . . . . . . . . . 380, 386 packing and unpacking . . . . . . . . . . . . . . . . . . . . . . . . 235
stdio.h, additional C functionality . . . . . . . . . . . . . . . . . . . 384 placing in memory type . . . . . . . . . . . . . . . . . . . . . . . . . 64
stdlib.h (library header file) . . . . . . . . . . . . . . . . . . . 380, 386 subnormal numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
stdout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122, 292 support, technical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
implementation-defined behavior . . . . . . . . . . . . . . . . 423 Sutter, Herb. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
implementation-defined behavior in C89 (CLIB) . . . . 440 __swap_bytes (intrinsic function) . . . . . . . . . . . . . . . . . . . 367
implementation-defined behavior in C89 (DLIB) . . . . 437 switch statements, hints for using . . . . . . . . . . . . . . . . . . . 252
Steele, Guy L. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 SWPB (assembler instruction) . . . . . . . . . . . . . . . . . . . . . 367
STL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 symbol names, using in preprocessor extensions . . . . . . . 285
strcasecmp, in string.h . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 symbols
strdup, in string.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 anonymous, creating . . . . . . . . . . . . . . . . . . . . . . . . . . 197
streambuf (library header file) . . . . . . . . . . . . . . . . . . . . . 381 including in output . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
streams listing in linker map file . . . . . . . . . . . . . . . . . . . . . . . . 111
implementation-defined behavior . . . . . . . . . . . . . . . . 414 overview of predefined . . . . . . . . . . . . . . . . . . . . . . . . . 43
supported in Embedded C++ . . . . . . . . . . . . . . . . . . . . 206 preprocessor, defining . . . . . . . . . . . . . . . . . . . . . . . . . 271
strerror (library function) syntax
implementation-defined behavior in C89 (CLIB) . . . . . . . 442 command line options . . . . . . . . . . . . . . . . . . . . . . . . . 263
strerror (library function), implementation-defined extended keywords . . . . . . . . . . . . . . . . . . . . 62, 318–320
behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428 invoking compiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
strerror (library function), implementation-defined system function, implementation-defined behavior. . 415, 425
behavior in C89 (DLIB) . . . . . . . . . . . . . . . . . . . . . . . . . . 439 system locks interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
--strict (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . . 299 system startup
string (library header file) . . . . . . . . . . . . . . . . . . . . . . . . . 381 CLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
strings, supported in Embedded C++ . . . . . . . . . . . . . . . . 206 customizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
string.h (library header file) . . . . . . . . . . . . . . . . . . . 380, 386 DLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
string.h, additional C functionality . . . . . . . . . . . . . . . . . . 384 initialization phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
strncasecmp, in string.h. . . . . . . . . . . . . . . . . . . . . . . . . . . 384 system termination
strnlen, in string.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 CLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
strstream (library header file) . . . . . . . . . . . . . . . . . . . . . . 381 C-SPY interface to . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
strtod (library function), configuring support for . . . . . . . 151 DLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
structure types system (library function)
alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 implementation-defined behavior in C89 . . . . . . . . . . . 442
layout of . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 implementation-defined behavior in C89 (DLIB) . . . . 439
packed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 system_include (pragma directive) . . . . . . . . . . . . . . 421, 436
structures --system_include_dir (compiler option) . . . . . . . . . . . . . . 299
accessing using a pointer . . . . . . . . . . . . . . . . . . . . . . . 191
aligning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

IAR C/C++ Compiler User Guide

464 for MSP430

AFE1_AFE2-1:1
 Index

TLS handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

T TLS16_I (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
tan (library function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 TLS16_ID (segment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
tan (library routine) . . . . . . . . . . . . . . . . . . . . . . . . . . 133–134 tools icon, in this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
tanf (library routine) . . . . . . . . . . . . . . . . . . . . . . . . . 133–134 trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
tanl (library routine) . . . . . . . . . . . . . . . . . . . . . . . . . 133–134 transformations, compiler . . . . . . . . . . . . . . . . . . . . . . . . . 240
__task (extended keyword) . . . . . . . . . . . . . . . . . . . . . . . . 330 translation
technical support, IAR Systems . . . . . . . . . . . . . . . . . . . . 261 implementation-defined behavior . . . . . . . . . . . . . . . . 413
template support implementation-defined behavior in C89 . . . . . . . . . . . 429
in Extended EC++ . . . . . . . . . . . . . . . . . . . . . . . . 206, 213 trap vectors, specifying with pragma directive . . . . . . . . . 354
missing from Embedded C++ . . . . . . . . . . . . . . . . . . . 206 type attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Terminal I/O window specifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
making available (CLIB) . . . . . . . . . . . . . . . . . . . . . . . 167 type definitions, used for specifying memory storage . . . . . 63
not supported when . . . . . . . . . . . . . . . . . . . . . . . 123–124 type information, omitting . . . . . . . . . . . . . . . . . . . . . . . . 291
termination of system. See system termination type qualifiers
termination status, implementation-defined behavior . . . . 425 const and volatile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 implementation-defined behavior . . . . . . . . . . . . . . . . 420
Texas Instruments MathLib . . . . . . . . . . . . . . . . . . . . . . . 134 implementation-defined behavior in C89 . . . . . . . . . . . 434
tgmath.h (library header file) . . . . . . . . . . . . . . . . . . . . . . 380 typedefs
32-bits (floating-point format) . . . . . . . . . . . . . . . . . . . . . 308 excluding from diagnostics . . . . . . . . . . . . . . . . . . . . . 289
this (pointer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 repeated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
class memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 using in preprocessor extensions . . . . . . . . . . . . . . . . . 285
referring to a class object . . . . . . . . . . . . . . . . . . . . . . . 208 type_attribute (pragma directive) . . . . . . . . . . . . . . . . . . . 352
threaded environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 type-based alias analysis (compiler transformation) . . . . . 244
thread-local storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 disabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
__TIME__ (predefined symbol) . . . . . . . . . . . . . . . . . . . . 374 type-safe memory management . . . . . . . . . . . . . . . . . . . . 205
time zone (library function) typographic conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
implementation-defined behavior in C89 . . . . . . . . . 439, 442
time zone (library function), implementation-defined
behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426 U
Timer A (TAIV) module . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 UBROF
Timer B (TBIV) module . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 format of linkable object files . . . . . . . . . . . . . . . . . . . 258
__TIMESTAMP__ (predefined symbol) . . . . . . . . . . . . . 374 specifying, example of . . . . . . . . . . . . . . . . . . . . . . . . . . 54
time-critical routines . . . . . . . . . . . . . . . . . . . . . . . . . 169, 198 uchar.h (library header file) . . . . . . . . . . . . . . . . . . . . . . . 380
time.h (library header file) . . . . . . . . . . . . . . . . . . . . . . . . 380 uintptr_t (integer type) . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
additional C functionality. . . . . . . . . . . . . . . . . . . . . . . 384 underflow errors, implementation-defined behavior . 422–423
time32 (library function), configuring support for . . . . . . 123 underflow range errors, implementation-defined
time64 (library function), configuring support for . . . . . . 123 behavior in C89 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436, 440
tips, programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 __ungetchar, in stdio.h . . . . . . . . . . . . . . . . . . . . . . . . . . . 384

465

AFE1_AFE2-1:1
 unions version
anonymous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200, 235 compiler subversion number . . . . . . . . . . . . . . . . . . . . 374
implementation-defined behavior . . . . . . . . . . . . . . . . 419 identifying C standard in use (__STDC_VERSION__) 374
implementation-defined behavior in C89 . . . . . . . . . . . 433 of compiler (__VER__) . . . . . . . . . . . . . . . . . . . . . . . . 374
universal character names, implementation-defined of this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420 version1 calling convention . . . . . . . . . . . . . . . . . . . . . . . 182
unroll (pragma directive) . . . . . . . . . . . . . . . . . . . . . . . . . 353 version2 calling convention . . . . . . . . . . . . . . . . . . . . . . . 182
unsigned char (data type) . . . . . . . . . . . . . . . . . . . . . 304–305 --version (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . 300
changing to signed char . . . . . . . . . . . . . . . . . . . . . . . . 270 --vla (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
unsigned int (data type) . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 void, pointers to . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
unsigned long long (data type) . . . . . . . . . . . . . . . . . . . . . 304 volatile
unsigned long (data type) . . . . . . . . . . . . . . . . . . . . . . . . . 304 and const, declaring objects . . . . . . . . . . . . . . . . . . . . . 314
unsigned short (data type) . . . . . . . . . . . . . . . . . . . . . . . . . 304 declaring objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
--use_c++_inline (compiler option) . . . . . . . . . . . . . . . . . 300 protecting simultaneously accesses variables . . . . . . . . 248
utility (STL header file) . . . . . . . . . . . . . . . . . . . . . . . . . . 382 rules for access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

V W
variable type information, omitting in object output . . . . . 291 #warning message (preprocessor extension) . . . . . . . . . . . 375
variables warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
auto . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 classifying in compiler . . . . . . . . . . . . . . . . . . . . . . . . . 275
defined inside a function . . . . . . . . . . . . . . . . . . . . . . . . 68 disabling in compiler . . . . . . . . . . . . . . . . . . . . . . . . . . 290
global exit code in compiler . . . . . . . . . . . . . . . . . . . . . . . . . . 301
accessing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 warnings icon, in this guide . . . . . . . . . . . . . . . . . . . . . . . . 35
placement in memory . . . . . . . . . . . . . . . . . . . . . . . . 60 warnings (pragma directive) . . . . . . . . . . . . . . . . . . . 421, 436
hints for choosing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 --warnings_affect_exit_code (compiler option) . . . . 259, 301
local. See auto variables --warnings_are_errors (compiler option) . . . . . . . . . . . . . 301
non-initialized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 --warn_about_c_style_casts (compiler option) . . . . . . . . . 301
omitting type info . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 wchar_t (data type), adding support for in C . . . . . . . . . . . 305
placing at absolute addresses . . . . . . . . . . . . . . . . . . . . 239 wchar.h (library header file) . . . . . . . . . . . . . . . . . . . 380, 383
placing in named segments . . . . . . . . . . . . . . . . . . . . . 239 wctype.h (library header file) . . . . . . . . . . . . . . . . . . . . . . 381
static weak (pragma directive) . . . . . . . . . . . . . . . . . . . . . . . . . . 354
placement in memory . . . . . . . . . . . . . . . . . . . . . . . . 60 web sites, recommended . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
taking the address of . . . . . . . . . . . . . . . . . . . . . . . . 246 white-space characters, implementation-defined behavior 414
variadic macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 write formatter, selecting . . . . . . . . . . . . . . . . . . . . . 164–165
vector (pragma directive) . . . . . . . . . . . . . . . . . . . . . . 74, 354 __write_array, in stdio.h . . . . . . . . . . . . . . . . . . . . . . . . . . 384
cannot be used with ROPI . . . . . . . . . . . . . . . . . . . . . . . 80 __write_buffered (DLIB library function) . . . . . . . . . . . . 121
vector (STL header file) . . . . . . . . . . . . . . . . . . . . . . . . . . 382

IAR C/C++ Compiler User Guide

466 for MSP430

AFE1_AFE2-1:1
 Index

__constrange(), symbol used in library . . . . . . . . . . . . . . . 385

X __construction_by_bitwise_copy_allowed, symbol used
in library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
XLINK errors
range error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 __CORE__ (predefined symbol). . . . . . . . . . . . . . . . . . . . 370
segment too long . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 __COUNTER__ (predefined symbol). . . . . . . . . . . . . . . . 370
XLINK segment memory types . . . . . . . . . . . . . . . . . . . . . 86 __cplusplus (predefined symbol) . . . . . . . . . . . . . . . . . . . 370
XLINK. See linker __DATA_MODEL__ (predefined symbol) . . . . . . . . . . . 371
__data16 (extended keyword) . . . . . . . . . . . . . . . . . . 309, 322
__data16_read_addr (intrinsic function) . . . . . . . . . . . . . . 359
Symbols __data16_size_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
__data20 (extended keyword) . . . . . . . . . . . . . . . . . . 309, 323
_Exit (library function) . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
__data20_longjmp (intrinsic function) . . . . . . . . . . . . . . . 360
_exit (library function) . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
__data20_read_char (intrinsic function) . . . . . . . . . . . . . . 360
_formatted_write (library function) . . . . . . . . . . . . . . . . . 163
__data20_read_long (intrinsic function) . . . . . . . . . . . . . . 360
_large_write (library function) . . . . . . . . . . . . . . . . . . . . . 163
__data20_read_short (intrinsic function) . . . . . . . . . . . . . 360
_medium_write (library function) . . . . . . . . . . . . . . . . . . . 163
__data20_setjmp (intrinsic function). . . . . . . . . . . . . . . . . 360
_small_write (library function) . . . . . . . . . . . . . . . . . . . . . 164
__data20_write_char (intrinsic function) . . . . . . . . . . . . . 361
__ALIGNOF__ (operator) . . . . . . . . . . . . . . . . . . . . . . . . 200
__data20_write_long (intrinsic function) . . . . . . . . . . . . . 361
__asm (language extension) . . . . . . . . . . . . . . . . . . . . . . . 172
__data20_write_short (intrinsic function) . . . . . . . . . . . . . 361
__assignment_by_bitwise_copy_allowed, symbol used
__DATE__ (predefined symbol). . . . . . . . . . . . . . . . . . . . 371
in library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
__delay_cycles (intrinsic function) . . . . . . . . . . . . . . . . . . 361
__BASE_FILE__ (predefined symbol) . . . . . . . . . . . . . . . 370
__disable_interrupt (intrinsic function) . . . . . . . . . . . . . . . 361
__bcd_add_long (intrinsic function) . . . . . . . . . . . . . . . . . 357
__DLIB_FILE_DESCRIPTOR (configuration symbol) . . 149
__bcd_add_long_long (intrinsic function) . . . . . . . . . . . . 357
__embedded_cplusplus (predefined symbol) . . . . . . . . . . 371
__bcd_add_short (intrinsic function) . . . . . . . . . . . . . . . . 357
__enable_interrupt (intrinsic function) . . . . . . . . . . . . . . . 362
__bic_SR_register (intrinsic function) . . . . . . . . . . . . . . . 357
__even_in_range (intrinsic function) . . . . . . . . . . . . . 75, 362
__bic_SR_register_on_exit (intrinsic function) . . . . . . . . 358
__exit (library function) . . . . . . . . . . . . . . . . . . . . . . . . . . 137
__bis_GIE_interrupt_state (intrinsic function) . . . . . . . . . 358
__FILE__ (predefined symbol) . . . . . . . . . . . . . . . . . . . . . 371
__bis_SR_register (intrinsic function) . . . . . . . . . . . . . . . 358
__FUNCTION__ (predefined symbol) . . . . . . . . . . . 204, 372
__bis_SR_register_on_exit (intrinsic function). . . . . . . . . 358
__func__ (predefined symbol) . . . . . . . . . . . . . . . . . 204, 372
__BUILD_NUMBER__ (predefined symbol) . . . . . . . . . 370
__gets, in stdio.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
__cc_rom (extended keyword) . . . . . . . . . . . . . . . . . . . . . 321
__get_interrupt_state (intrinsic function) . . . . . . . . . . . . . 362
choosing calling convention. . . . . . . . . . . . . . . . . . . . . 183
__get_R4_register (intrinsic function) . . . . . . . . . . . . . . . 363
__cc_version1 (extended keyword) . . . . . . . . . . . . . . . . . 322
__get_R5_register (intrinsic function) . . . . . . . . . . . . . . . 363
choosing calling convention. . . . . . . . . . . . . . . . . . . . . 182
__get_SP_register (intrinsic function). . . . . . . . . . . . . . . . 363
__cc_version2 (extended keyword) . . . . . . . . . . . . . . . . . 322
__get_SR_register (intrinsic function) . . . . . . . . . . . . . . . 364
choosing calling convention. . . . . . . . . . . . . . . . . . . . . 182
__get_SR_register_on_exit (intrinsic function) . . . . . . . . 364
__code_distance (intrinsic function) . . . . . . . . . . . . . . . . . 358
__has_constructor, symbol used in library . . . . . . . . . . . . 385
__CODE_MODEL__ (predefined symbol). . . . . . . . . . . . 370
__has_destructor, symbol used in library . . . . . . . . . . . . . 385
__code, symbol used in library . . . . . . . . . . . . . . . . . . . . . 385
__iar_cos_accurate (library routine) . . . . . . . . . . . . . . . . . 134

467

AFE1_AFE2-1:1
 __iar_cos_accuratef (library routine) . . . . . . . . . . . . . . . . 134 __iar_Sin_small (library routine) . . . . . . . . . . . . . . . . . . . 133
__iar_cos_accuratel (library routine) . . . . . . . . . . . . . . . . 134 __iar_sin_small (library routine). . . . . . . . . . . . . . . . . . . . 133
__iar_cos_small (library routine) . . . . . . . . . . . . . . . . . . . 133 __iar_Sin_smallf (library routine) . . . . . . . . . . . . . . . . . . . 133
__iar_cos_smallf (library routine) . . . . . . . . . . . . . . . . . . . 133 __iar_sin_smallf (library routine) . . . . . . . . . . . . . . . . . . . 133
__iar_cos_smalll (library routine) . . . . . . . . . . . . . . . . . . . 133 __iar_Sin_smalll (library routine) . . . . . . . . . . . . . . . . . . . 133
__IAR_DLIB_PERTHREAD_INIT_SIZE (macro) . . . . . 158 __iar_sin_smalll (library routine) . . . . . . . . . . . . . . . . . . . 133
__IAR_DLIB_PERTHREAD_SIZE (macro) . . . . . . . . . . 158 __IAR_SYSTEMS_ICC__ (predefined symbol) . . . . . . . 372
__IAR_DLIB_PERTHREAD_SYMBOL_OFFSET __iar_tan_accurate (library routine) . . . . . . . . . . . . . . . . . 134
(symbolptr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 __iar_tan_accuratef (library routine). . . . . . . . . . . . . . . . . 134
__iar_exp_small (library routine) . . . . . . . . . . . . . . . . . . . 133 __iar_tan_accuratel (library routine) . . . . . . . . . . . . . . . . . 134
__iar_exp_smallf (library routine) . . . . . . . . . . . . . . . . . . 133 __iar_tan_small (library routine) . . . . . . . . . . . . . . . . . . . 133
__iar_exp_smalll (library routine) . . . . . . . . . . . . . . . . . . 133 __iar_tan_smallf (library routine) . . . . . . . . . . . . . . . . . . . 133
__iar_log_small (library routine) . . . . . . . . . . . . . . . . . . . 133 __iar_tan_smalll (library routine) . . . . . . . . . . . . . . . . . . . 133
__iar_log_smallf (library routine) . . . . . . . . . . . . . . . . . . . 133 __interrupt (extended keyword) . . . . . . . . . . . . . . . . . 74, 323
__iar_log_smalll (library routine) . . . . . . . . . . . . . . . . . . . 133 using in pragma directives . . . . . . . . . . . . . . . . . . . . . . 354
__iar_log10_small (library routine) . . . . . . . . . . . . . . . . . 133 __intrinsic (extended keyword). . . . . . . . . . . . . . . . . . . . . 324
__iar_log10_smallf (library routine) . . . . . . . . . . . . . . . . . 133 __LINE__ (predefined symbol) . . . . . . . . . . . . . . . . . . . . 372
__iar_log10_smalll (library routine) . . . . . . . . . . . . . . . . . 133 __low_level_init . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
__iar_Pow (library routine) . . . . . . . . . . . . . . . . . . . . . . . . 134 initialization phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
__iar_Powf (library routine) . . . . . . . . . . . . . . . . . . . . . . . 134 __low_level_init, customizing . . . . . . . . . . . . . . . . . . . . . 138
__iar_Powl (library routine) . . . . . . . . . . . . . . . . . . . . . . . 134 __low_power_mode_n (intrinsic function) . . . . . . . . . . . . 364
__iar_Pow_accurate (library routine) . . . . . . . . . . . . . . . . 134 __low_power_mode_off_on_exit (intrinsic function) . . . . 364
__iar_pow_accurate (library routine) . . . . . . . . . . . . . . . . 134 __memory_of
__iar_Pow_accuratef (library routine) . . . . . . . . . . . . . . . 134 operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
__iar_pow_accuratef (library routine). . . . . . . . . . . . . . . . 134 symbol used in library . . . . . . . . . . . . . . . . . . . . . . . . . 385
__iar_Pow_accuratel (library routine). . . . . . . . . . . . . . . . 134 __monitor (extended keyword) . . . . . . . . . . . . . . . . . . . . . 324
__iar_pow_accuratel (library routine) . . . . . . . . . . . . . . . . 134 __noreturn (extended keyword) . . . . . . . . . . . . . . . . . . . . 327
__iar_pow_small (library routine) . . . . . . . . . . . . . . . . . . 133 __no_alloc (extended keyword) . . . . . . . . . . . . . . . . . . . . 324
__iar_pow_smallf (library routine) . . . . . . . . . . . . . . . . . . 133 __no_alloc_str (operator) . . . . . . . . . . . . . . . . . . . . . . . . . 325
__iar_pow_smalll (library routine) . . . . . . . . . . . . . . . . . . 133 __no_alloc_str16 (operator) . . . . . . . . . . . . . . . . . . . . . . . 325
__iar_program_start (label). . . . . . . . . . . . . . . . . . . . . . . . 135 __no_alloc16 (extended keyword) . . . . . . . . . . . . . . . . . . 324
__iar_Sin (library routine) . . . . . . . . . . . . . . . . . . . . 133–134 __no_init (extended keyword) . . . . . . . . . . . . . . . . . 251, 326
__iar_Sinf (library routine) . . . . . . . . . . . . . . . . . . . . 133–134 __no_multiplier (extended keyword) . . . . . . . . . . . . . . . . 326
__iar_Sinl (library routine) . . . . . . . . . . . . . . . . . . . . 133–134 __no_operation (intrinsic function) . . . . . . . . . . . . . . . . . . 364
__iar_Sin_accurate (library routine) . . . . . . . . . . . . . . . . . 134 __no_pic (extended keyword) . . . . . . . . . . . . . . . . . . . . . . 326
__iar_sin_accurate (library routine) . . . . . . . . . . . . . . . . . 134 __op_code (intrinsic function) . . . . . . . . . . . . . . . . . . . . . 364
__iar_Sin_accuratef (library routine) . . . . . . . . . . . . . . . . 134 __persistent (extended keyword) . . . . . . . . . . . . . . . . . . . 327
__iar_sin_accuratef (library routine) . . . . . . . . . . . . . . . . . 134 cannot be used with ROPI . . . . . . . . . . . . . . . . . . . . . . . 80
__iar_Sin_accuratel (library routine) . . . . . . . . . . . . . . . . 134 __POSITION_INDEPENDENT_CODE__ (predefined
__iar_sin_accuratel (library routine) . . . . . . . . . . . . . . . . . 134 symbol) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372

IAR C/C++ Compiler User Guide

468 for MSP430

AFE1_AFE2-1:1
 Index

__PRETTY_FUNCTION__ (predefined symbol). . . . . . . 373 -I (compiler option). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

__printf_args (pragma directive). . . . . . . . . . . . . . . . . . . . 348 -l (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
__program_start (label) . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 for creating skeleton code . . . . . . . . . . . . . . . . . . . . . . 179
__ramfunc (extended keyword) . . . . . . . . . . . . . . . . . 79, 327 -O (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
cannot be used with ROPI . . . . . . . . . . . . . . . . . . . . . . . 80 -o (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
__raw (extended keyword) . . . . . . . . . . . . . . . . . . . . . . . . 328 -Q (linker option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
__REGISTER_MODEL__ (predefined symbol) . . . . . . . 373 -r (compiler option). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
__REGISTER_R4__ (predefined symbol) . . . . . . . . . . . . 373 --char_is_signed (compiler option) . . . . . . . . . . . . . . . . . . 270
__REGISTER_R5__ (predefined symbol) . . . . . . . . . . . . 373 --char_is_unsigned (compiler option) . . . . . . . . . . . . . . . . 270
__ReportAssert (library function) . . . . . . . . . . . . . . . . . . . 145 --clib (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
__root (extended keyword) . . . . . . . . . . . . . . . . . . . . . . . . 329 --code_model (compiler option) . . . . . . . . . . . . . . . . . . . . 270
__ROPI__ (predefined symbol) . . . . . . . . . . . . . . . . . . . . 373 --c89 (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
__ro_placement (extended keyword) . . . . . . . . . . . . . . . . 329 --data_model (compiler option) . . . . . . . . . . . . . . . . . . . . 272
__rt_version (runtime model attribute) . . . . . . . . . . . . . . . 113 --debug (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . 272
__saturated_add_signed_type (intrinsic function) . . . . . . . 365 --dependencies (compiler option) . . . . . . . . . . . . . . . . . . . 273
__saturated_add_unsigned_type (intrinsic function) . . . . . 365 --diagnostics_tables (compiler option) . . . . . . . . . . . . . . . 275
__saturated_sub_signed_type (intrinsic function) . . . . . . . 365 --diag_error (compiler option) . . . . . . . . . . . . . . . . . . . . . 274
__saturated_sub_unsigned_type (intrinsic function) . . . . . 365 --diag_remark (compiler option) . . . . . . . . . . . . . . . . . . . . 274
__scanf_args (pragma directive) . . . . . . . . . . . . . . . . . . . . 350 --diag_suppress (compiler option) . . . . . . . . . . . . . . . . . . 275
__segment_begin (extended operator) . . . . . . . . . . . . . . . 201 --diag_warning (compiler option) . . . . . . . . . . . . . . . . . . . 275
__segment_end (extended operator) . . . . . . . . . . . . . . . . . 201 --discard_unused_publics (compiler option) . . . . . . . . . . . 276
__segment_size (extended operator) . . . . . . . . . . . . . . . . . 201 --dlib (compiler option). . . . . . . . . . . . . . . . . . . . . . . . . . . 276
__set_interrupt_state (intrinsic function) . . . . . . . . . . . . . 366 --dlib_config (compiler option). . . . . . . . . . . . . . . . . . . . . 277
__set_R4_register (intrinsic function) . . . . . . . . . . . . . . . . 366 --double (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . 277
__set_R5_register (intrinsic function) . . . . . . . . . . . . . . . . 366 --ec++ (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . . 278
__set_SP_register (intrinsic function) . . . . . . . . . . . . . . . . 367 --eec++ (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . 279
__STDC_VERSION__ (predefined symbol) . . . . . . . . . . 374 --enable_multibytes (compiler option) . . . . . . . . . . . . . . . 279
__STDC__ (predefined symbol) . . . . . . . . . . . . . . . . . . . . 373 --enable_restrict (compiler option) . . . . . . . . . . . . . . . . . . 279
__swap_bytes (intrinsic function) . . . . . . . . . . . . . . . . . . . 367 --error_limit (compiler option) . . . . . . . . . . . . . . . . . . . . . 280
__task (extended keyword) . . . . . . . . . . . . . . . . . . . . . . . . 330 --guard_calls (compiler option). . . . . . . . . . . . . . . . . . . . . 280
__TIMESTAMP__ (predefined symbol) . . . . . . . . . . . . . 374 --header_context (compiler option) . . . . . . . . . . . . . . . . . . 281
__TIME__ (predefined symbol) . . . . . . . . . . . . . . . . . . . . 374 --hw_workaround (compiler option) . . . . . . . . . . . . . . . . . 281
__ungetchar, in stdio.h . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 --library_module (compiler option) . . . . . . . . . . . . . . . . . 283
__VA_ARGS__ (preprocessor extension) . . . . . . . . . . . . 197 --lock_r4 (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . 283
__write_array, in stdio.h . . . . . . . . . . . . . . . . . . . . . . . . . . 384 --lock_r5 (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . 283
__write_buffered (DLIB library function) . . . . . . . . . . . . 121 --macro_positions_in_diagnostics (compiler option) . . . . 284
-D (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 --mfc (compiler option). . . . . . . . . . . . . . . . . . . . . . . . . . . 284
-e (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 --migration_preprocessor_extensions (compiler option) . . 284
-f (compiler option). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 --misrac (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . 267

469

AFE1_AFE2-1:1
 --misrac_verbose (compiler option) . . . . . . . . . . . . . . . . . 267 --version (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . 300
--misrac1998 (compiler option) . . . . . . . . . . . . . . . . . . . . 267 --vla (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
--misrac2004 (compiler option) . . . . . . . . . . . . . . . . . . . . 267 --warnings_affect_exit_code (compiler option) . . . . 259, 301
--module_name (compiler option) . . . . . . . . . . . . . . . . . . 285 --warnings_are_errors (compiler option) . . . . . . . . . . . . . 301
--multiplier (compiler option) . . . . . . . . . . . . . . . . . . . . . . 285 --warn_about_c_style_casts (compiler option) . . . . . . . . . 301
--no_call_frame_info (compiler option) . . . . . . . . . . . . . . 286 ?C_EXIT (assembler label) . . . . . . . . . . . . . . . . . . . . . . . . 167
--no_code_motion (compiler option) . . . . . . . . . . . . . . . . 286 ?C_GETCHAR (assembler label) . . . . . . . . . . . . . . . . . . . 167
--no_cse (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . 286 ?C_PUTCHAR (assembler label) . . . . . . . . . . . . . . . . . . . 167
--no_inline (compiler option) . . . . . . . . . . . . . . . . . . . . . . 287 @ (operator)
--no_path_in_file_macros (compiler option). . . . . . . . . . . 287 placing at absolute address . . . . . . . . . . . . . . . . . . . . . . 237
--no_rw_dynamic_init (compiler option) . . . . . . . . . . . . . 287 placing in segments . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
--no_size_constraints (compiler option) . . . . . . . . . . . . . . 288 #include files, specifying . . . . . . . . . . . . . . . . . . . . . 256, 282
--no_static_destruction (compiler option) . . . . . . . . . . . . . 288 #warning message (preprocessor extension) . . . . . . . . . . . 375
--no_system_include (compiler option) . . . . . . . . . . . . . . 288 %Z replacement string, implementation-defined behavior 426
--no_typedefs_in_diagnostics (compiler option) . . . . . . . . 289
--no_ubrof_messages (compiler option) . . . . . . . . . . . . . . 290
--no_unroll (compiler option) . . . . . . . . . . . . . . . . . . . . . . 290 Numerics
--no_warnings (compiler option) . . . . . . . . . . . . . . . . . . . 290 32-bits (floating-point format) . . . . . . . . . . . . . . . . . . . . . 308
--no_wrap_diagnostics (compiler option) . . . . . . . . . . . . . 290 64-bit data types, avoiding . . . . . . . . . . . . . . . . . . . . . . . . 233
--omit_types (compiler option) . . . . . . . . . . . . . . . . . . . . . 291 64-bits (floating-point format) . . . . . . . . . . . . . . . . . . . . . 308
--only_stdout (compiler option) . . . . . . . . . . . . . . . . . . . . 292
--output (compiler option). . . . . . . . . . . . . . . . . . . . . . . . . 292
--pending_instantiations (compiler option) . . . . . . . . . . . . 292
--predef_macro (compiler option) . . . . . . . . . . . . . . . . . . . 293
--preinclude (compiler option) . . . . . . . . . . . . . . . . . . . . . 293
--preprocess (compiler option) . . . . . . . . . . . . . . . . . . . . . 293
--reduce_stack_usage (compiler option) . . . . . . . . . . . . . . 294
--regvar_r4 (compiler option) . . . . . . . . . . . . . . . . . . . . . . 294
--regvar_r5 (compiler option) . . . . . . . . . . . . . . . . . . . . . . 295
--relaxed_fp (compiler option) . . . . . . . . . . . . . . . . . . . . . 295
--remarks (compiler option) . . . . . . . . . . . . . . . . . . . . . . . 296
--require_prototypes (compiler option) . . . . . . . . . . . . . . . 296
--ropi (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . . 296
--save_reg20 (compiler option) . . . . . . . . . . . . . . . . . . . . . 297
--segment (compiler option) . . . . . . . . . . . . . . . . . . . . . . . 297
--silent (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . 299
--strict (compiler option) . . . . . . . . . . . . . . . . . . . . . . . . . . 299
--system_include_dir (compiler option) . . . . . . . . . . . . . . 299
--use_c++_inline (compiler option) . . . . . . . . . . . . . . . . . 300

IAR C/C++ Compiler User Guide

470 for MSP430

AFE1_AFE2-1:1