The CC-RH controls allocation to memory or the access method by allocating functions or data to sections.

This section cannot be used by the PIC facility.

The sld or sst instruction which is even shorter can be used.

These sections can be used even by the PID facility.

These sections can be used even by the PID facility.

These sections can be used even by the PID facility.

This section cannot be used by the PIROD facility.

These sections cannot be used by the PIROD facility.

The sections to which the CC-RH allocates functions or data are the four sections .text, .data, .bss, and .const, by default.

The longer the relative distance at access is, the access is in a long instruction length and the code size is increased.

The CC-RH can allocate functions and data to desired sections using the extended facilities. This makes it possible to generate code using the relocation attribute characteristics of each section.

Describe the #pragma section directive in the following format.

#pragma section attribute-strings "user-defined-name"

#pragma section attribute-strings

#pragma section user-defined-name

#pragma section default

or

#pragma section

Section relocation attributes are specified using "attribute strings", and section names are specified using "user-defined names". The usable attribute strings vary depending on the specified options.

The relationship between specifiable attribute strings, corresponding section relocation attributes, and options that can be specified as conditions is shown in Table 4.19.

Attribute strings are case-sensitive.

The following characters are usable in user-defined names.

The allocation section of functions or data written after a #pragma section directive is determined in accordance with the following rules.

1. The relocation attribute is determined from the "attribute string".

(1) For data, *data* or *bss* is automatically selected depending on whether there is an initial value.

(2) A format with no attribute string has an effect on both functions and data, and the default relocation attribute of the compiler is used.

2. A string representing the relocation attribute is linked after the "user-defined name"Note.

(1) If the user-defined name starts with a number from 0 to 9, "_" is added to the beginning.

(2) If there is no user-defined name, the default section name is used without change.

3. When the format of #pragma section default or #pragma section is specified, it has an effect on both functions and data, and the default relocation attribute of the compiler and the default section name are used.

A #pragma section directive is valid from the position where it was written up to the position where the next #pragma section directive appears or up to the end of the source file.

#pragma section gp_disp16 "foo"

int a = 1;        /* foo.sdata */

int b;            /* foo.sbss */

#pragma section zconst23 "bar"

const int c = 2;  /* bar.zconst23 */

#pragma section text "123"

void func() {}    /* _123.text */

#pragma section baz

int d = 3;        /* baz.data */

int e;            /* baz.bss */

const int f = 4;  /* baz.const */

void func2() {}   /* baz.text */

#pragma section default

int g = 3;        /* .data */

int h;            /* .bss */

const int i = 4;  /* .const */

void func3() {}   /* .text */

The effect of a #pragma section directive differs between variables and functions.

If there are multiple declarations and definitions for a variable and a different #pragma section directive is specified for each, the #pragma section directive that appears first is valid.

int x = 1;    /* Variable x is allocated to foo.data */

int y = 2;    /* Variable y is allocated to bar.data */

#pragma section foo

extern int x;

#pragma section bar

extern int x;

extern int y;

When the -pic option is not specified, #pragma section is valid only for function definitions.

When the -pic option is specified, similar as to variables, #pragma section is valid for both declarations and definitions.