Specifications

CAVR-4

Part 1. Using the compiler

The DLIB runtime environment

Assert

If you have linked your application with support for runtime debugging, C-SPY will be

notified about failed asserts. If this is not the behavior you require, you must add the

source file xReportAssert.c to your application project. Alternatively, you can

rebuild the library. The

__ReportAssert function generates the assert notification.You

can find template code in the

avr\src directory. For further information, see Building

and using a customized library, page 62. To turn off assertions, you must define the

symbol

NDEBUG.

In the IAR Embedded Workbench, this 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.

Heaps

The runtime environment supports heaps in the following memory types:

See The heap, page 44 for information about how to set the size for each heap. To use a

specific heap, the prefix in the table is the extended keyword to use in front of

malloc,

free, calloc, and realloc. The default functions will use one of the specific heap

variants, depending on project settings such as memory model. For information about

how to use a specific heap in C++, see New and Delete operators, page 114.

Memory type Segment name Extended keyword

Used by default in

memory model

Tiny TINY_HEAP __tiny Tiny

Near NEAR_HEAP __near Small

Far FAR_HEAP __far Medium

Huge HUGE_HEAP __huge Large

Table 22: Heaps and memory types