diff options
Diffstat (limited to 'share/doc/gcc-linaro-aarch64-linux-gnu/html/gcc/Named-Address-Spaces.html')
| -rw-r--r-- | share/doc/gcc-linaro-aarch64-linux-gnu/html/gcc/Named-Address-Spaces.html | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/share/doc/gcc-linaro-aarch64-linux-gnu/html/gcc/Named-Address-Spaces.html b/share/doc/gcc-linaro-aarch64-linux-gnu/html/gcc/Named-Address-Spaces.html index c3e1079..c200847 100644 --- a/share/doc/gcc-linaro-aarch64-linux-gnu/html/gcc/Named-Address-Spaces.html +++ b/share/doc/gcc-linaro-aarch64-linux-gnu/html/gcc/Named-Address-Spaces.html @@ -56,7 +56,7 @@ Up: <a rel="up" accesskey="u" href="C-Extensions.html#C-Extensions">C Exten <h3 class="section">6.16 Named Address Spaces</h3> -<p><a name="index-Named-Address-Spaces-2436"></a> +<p><a name="index-Named-Address-Spaces-2438"></a> As an extension, the GNU C compiler supports named address spaces as defined in the N1275 draft of ISO/IEC DTR 18037. Support for named address spaces in GCC will evolve as the draft technical report @@ -84,17 +84,17 @@ needed to locate read-only data in flash memory without using (inline) assembler code. <dl> -<dt><code>__flash</code><dd><a name="index-g_t_0040code_007b_005f_005fflash_007d-AVR-Named-Address-Spaces-2437"></a>The <code>__flash</code> qualifier will locate data in the +<dt><code>__flash</code><dd><a name="index-g_t_0040code_007b_005f_005fflash_007d-AVR-Named-Address-Spaces-2439"></a>The <code>__flash</code> qualifier will locate data in the <code>.progmem.data</code> section. Data will be read using the <code>LPM</code> instruction. Pointers to this address space are 16 bits wide. - <br><dt><code>__flash1</code><br><dt><code>__flash2</code><br><dt><code>__flash3</code><br><dt><code>__flash4</code><br><dt><code>__flash5</code><dd><a name="index-g_t_0040code_007b_005f_005fflash1_007d-AVR-Named-Address-Spaces-2438"></a><a name="index-g_t_0040code_007b_005f_005fflash2_007d-AVR-Named-Address-Spaces-2439"></a><a name="index-g_t_0040code_007b_005f_005fflash3_007d-AVR-Named-Address-Spaces-2440"></a><a name="index-g_t_0040code_007b_005f_005fflash4_007d-AVR-Named-Address-Spaces-2441"></a><a name="index-g_t_0040code_007b_005f_005fflash5_007d-AVR-Named-Address-Spaces-2442"></a>These are 16-bit address spaces locating data in section + <br><dt><code>__flash1</code><br><dt><code>__flash2</code><br><dt><code>__flash3</code><br><dt><code>__flash4</code><br><dt><code>__flash5</code><dd><a name="index-g_t_0040code_007b_005f_005fflash1_007d-AVR-Named-Address-Spaces-2440"></a><a name="index-g_t_0040code_007b_005f_005fflash2_007d-AVR-Named-Address-Spaces-2441"></a><a name="index-g_t_0040code_007b_005f_005fflash3_007d-AVR-Named-Address-Spaces-2442"></a><a name="index-g_t_0040code_007b_005f_005fflash4_007d-AVR-Named-Address-Spaces-2443"></a><a name="index-g_t_0040code_007b_005f_005fflash5_007d-AVR-Named-Address-Spaces-2444"></a>These are 16-bit address spaces locating data in section <code>.progmem</code><var>N</var><code>.data</code> where <var>N</var> refers to address space <code>__flash</code><var>N</var>. The compiler will set the <code>RAMPZ</code> segment register approptiately before reading data by means of the <code>ELPM</code> instruction. - <br><dt><code>__memx</code><dd><a name="index-g_t_0040code_007b_005f_005fmemx_007d-AVR-Named-Address-Spaces-2443"></a>This is a 24-bit address space that linearizes flash and RAM: + <br><dt><code>__memx</code><dd><a name="index-g_t_0040code_007b_005f_005fmemx_007d-AVR-Named-Address-Spaces-2445"></a>This is a 24-bit address space that linearizes flash and RAM: If the high bit of the address is set, data is read from RAM using the lower two bytes as RAM address. If the high bit of the address is clear, data is read from flash @@ -194,7 +194,7 @@ initialization will be as if <code>foo</code> was located in the first <h4 class="subsection">6.16.2 M32C Named Address Spaces</h4> -<p><a name="index-g_t_0040code_007b_005f_005ffar_007d-M32C-Named-Address-Spaces-2444"></a> +<p><a name="index-g_t_0040code_007b_005f_005ffar_007d-M32C-Named-Address-Spaces-2446"></a> On the M32C target, with the R8C and M16C cpu variants, variables qualified with <code>__far</code> are accessed using 32-bit addresses in order to access memory beyond the first 64 Ki bytes. If @@ -203,7 +203,7 @@ effect. <h4 class="subsection">6.16.3 RL78 Named Address Spaces</h4> -<p><a name="index-g_t_0040code_007b_005f_005ffar_007d-RL78-Named-Address-Spaces-2445"></a> +<p><a name="index-g_t_0040code_007b_005f_005ffar_007d-RL78-Named-Address-Spaces-2447"></a> On the RL78 target, variables qualified with <code>__far</code> are accessed with 32-bit pointers (20-bit addresses) rather than the default 16-bit addresses. Non-far variables are assumed to appear in the topmost @@ -211,7 +211,7 @@ addresses. Non-far variables are assumed to appear in the topmost <h4 class="subsection">6.16.4 SPU Named Address Spaces</h4> -<p><a name="index-g_t_0040code_007b_005f_005fea_007d-SPU-Named-Address-Spaces-2446"></a> +<p><a name="index-g_t_0040code_007b_005f_005fea_007d-SPU-Named-Address-Spaces-2448"></a> On the SPU target variables may be declared as belonging to another address space by qualifying the type with the <code>__ea</code> address space identifier: |