These function attributes are supported by the MSP430 back end:
criticalnaked or reentrant attributes. They can have
the interrupt attribute.
interruptYou can provide an argument to the interrupt
attribute which specifies a name or number. If the argument is a
number it indicates the slot in the interrupt vector table (0 - 31) to
which this handler should be assigned. If the argument is a name it
is treated as a symbolic name for the vector slot. These names should
match up with appropriate entries in the linker script. By default
the names watchdog for vector 26, nmi for vector 30 and
reset for vector 31 are recognized.
nakedasm statements can safely be included in naked functions
(see Basic Asm). While using extended asm or a mixture of
basic asm and C code may appear to work, they cannot be
depended upon to work reliably and are not supported.
reentrantnaked
or critical attributes. They can have the interrupt
attribute.
wakeuploweruppereitherThe attributes work in conjunction with a linker script that has been
augmented to specify where to place sections with a .lower and
a .upper prefix. So, for example, as well as placing the
.data section, the script also specifies the placement of a
.lower.data and a .upper.data section. The intention
is that lower sections are placed into a small but easier to
access memory region and the upper sections are placed into a larger, but
slower to access, region.
The either attribute is special. It tells the linker to place
the object into the corresponding lower section if there is
room for it. If there is insufficient room then the object is placed
into the corresponding upper section instead. Note that the
placement algorithm is not very sophisticated. It does not attempt to
find an optimal packing of the lower sections. It just makes
one pass over the objects and does the best that it can. Using the
-ffunction-sections and -fdata-sections command-line
options can help the packing, however, since they produce smaller,
easier to pack regions.