原创 CodeWarrior代码分区存放Segmentation

 2008-6-7 15:04  3193 3 3 分类: MCU/ 嵌入式

Segmentation <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

The Linker supports the concept of segments in that the memory space may be partitioned into several segments. The Compiler allows attributing a certain segment name to certain global variables or functions which then will be allocated into that segment by the Linker. Where that segment actually lies is determined by an entry in the Linker parameter file.

The syntax of the segment specification pragma:

SegDef= "#pragma" SegmentType ({SegmentMod} SegmentName |

"DEFAULT").

SegmentType= "CODE_SEG" | "CODE_SECTION" |

"DATA_SEG"| "DATA_SECTION" |

"CONST_SEG"| "CONST_SECTION" |

"STRING_SEG"| "STRING_SECTION".

"Y_BASED" | "Z_BASED" | "DPAGE" | "PPAGE" |

"EPAGE" | "PIC".

Since there are two basic types of segments, code and data segments, there are also two pragmas to specify segments:

#pragma CODE_SEG <segment_name>

#pragma DATA_SEG <segment_name>

In addition there are pragmas for constant data and for strings:

#pragma CONST_SEG <segment_name>

#pragma STRING_SEG <segment_name>

All four pragmas are valid until the next pragma of the same kind is encountered.

In the HIWARE object file format, constants are put into the DATA_SEG if no CONST_SEG was specified. In the ELF Object file format, constants are always put into a constant segment.

Strings are put into the segment STRINGS until a pragma STRING_SEG is specified. After this pragma, all strings are allocated into this constant segment. The linker then treats this segment like any other constant segment.

If no segment is specified, the Compiler assumes two default segments named DEFAULT_ROM (the default code segment) and DEFAULT_RAM (the default data segment). Use the segment name DEFAULT to explicitly make these default segments the current segments:

#pragma CODE_SEG DEFAULT

#pragma DATA_SEG DEFAULT

#pragma CONST_SEG DEFAULT

#pragma STRING_SEG DEFAULT

Segments may also be declared as __SHORT_SEG by inserting the keyword __SHORT_SEG just before the segment name (with the exception of the predefined segment DEFAULT - this segment cannot be SHORT). This makes the Compiler use short (i.e. 8 bits or 16 bits, depending on the Back End) absolute addresses to access global objects, or to call functions. It is the programmer's responsibility to allocate SHORT segments in the proper memory area.

NOTE

The default code and data segments may not be declared SHORT.

The meaning of the other segment modifiers, such as NEAR and FAR, are backend specific. Modifiers that are not supported by the back end are ignored. Please refer to the backend chapter for data about which modifiers are supported.

The segment pragmas also have an effect on static local variables. Static local variables are local variables with the `static' flag set. They are in fact normal global variables but with scope only to the function in which they are defined:

#pragma DATA_SEG MySeg

static char foo(void) {

static char i = 0; /* place this variable into MySeg */

return i++;

}

#pragma DATA_SEG DEFAULT

NOTE

Using the ELF/DWARF object file format (option -F1 or -F2), all constants are placed into the section .rodata by default unless a #pragma CONST_SEG is used.

NOTE

There are aliases to satisfy the ELF naming convention for all segment names. Use CODE_SECTION instead of CODE_SEG. Use DATA_SECTION instead of DATA_SEG. Use CONST_SECTION instead of CONST_SEG. Use STRING_SECTION instead of STRING_SEG. These aliases behave exactly are the XXX_SEG name versions.

Example of Segmentation Without Compiler -Cc Option

/* Placed into Segment: */

static int a; /* DEFAULT_RAM(-1) */

static const int c0 = 10; /* DEFAULT_RAM(-1) */

#pragma DATA_SEG MyVarSeg

static int b; /* MyVarSeg(0) */

static const int c1 = 11; /* MyVarSeg(0) */

#pragma DATA_SEG DEFAULT

static int c; /* DEFAULT_RAM(-1) */

static const int c2 = 12; /* DEFAULT_RAM(-1) */

#pragma DATA_SEG MyVarSeg

#pragma CONST_SEG MyConstSeg