<html>
<head>
<base href="http://bugzilla.gdcproject.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:jens-bugzilla@gpio.dk" title="Jens Bauer <jens-bugzilla@gpio.dk>"> <span class="fn">Jens Bauer</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Missing "section" GCC attribute in GDC"
href="http://bugzilla.gdcproject.org/show_bug.cgi?id=168">bug 168</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>jens-bugzilla@gpio.dk
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Missing "section" GCC attribute in GDC"
href="http://bugzilla.gdcproject.org/show_bug.cgi?id=168#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Missing "section" GCC attribute in GDC"
href="http://bugzilla.gdcproject.org/show_bug.cgi?id=168">bug 168</a>
from <span class="vcard"><a class="email" href="mailto:jens-bugzilla@gpio.dk" title="Jens Bauer <jens-bugzilla@gpio.dk>"> <span class="fn">Jens Bauer</span></a>
</span></b>
<pre>Being able to select which section code, variables, arrays and other data will
go into is especially important when working with microcontrollers.
The following gives some insight of why this feature is useful on
microcontrollers:
For instance: Often the first N words of data is reserved for exception
vectors.
On ARM, for instance (any ARM architecture), the first 16 words which are
32-bit wide each, contain first an initial stack pointer value followed by core
vectors.
After those 16 vectors, the vendor may choose what interrupt vectors to add
(normally up to 256 vectors can be supported here).
In a linker-script, one would typically make a section called .isr_vectors and
then put an array of function-pointers in this section. Note: Such a section
may be read-only memory (eg. Flash memory or ROM), but in some cases it can be
RAM.
Other reasons for being able to specify sections include the ability to choose
which data goes into CCMRAM (CCM=Core Coupled Memory) on some devices,
NOR-Flash, NAND-Flash, Flash Bank 1, Flash Bank 2, SRAM1, SRAM2, SRAM3, SRAM4,
Local SRAM, SDRAM, External SRAM, ROM, and so forth; even SD/MMC card can be
written indirectly this way.
On some microcontrollers, it's very useful to have code (normally running in
the .text section) to be copied to SRAM for fast execution speed, as executing
code from the Flash memory might be up to 7 times slower than SRAM. Thus small
subroutines can often be placed in SRAM to improve speed greatly.
Since the D compiler already know about some sections, it would be convenient
having native support for it, which would not depend on the backend.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>