Support For Various Ti Coff Versions; And Win32 (Cygwin/Mingw) - Red Hat ENTERPRISE LINUX 3 - USING ID Using Instructions

Chapter 5. Machine Dependent Features
The linker will recognize some extra sections which are MSP430 specific:
.vectors
Defines a portion of ROM where interrupt vectors located.
.bootloader
Defines the bootloader portion of the ROM (if applicable). Any code in this section will be
uploaded to the MPU.
.infomem
Defines an information memory section (if applicable). Any code in this section will be uploaded
to the MPU.
.infomemnobits
This is the same as the
to the MPU.
.noinit
Denotes a portion of RAM located above
The last two sections are used by gcc.
5.7. 's Support for Various TI COFF Versions
ld
The switch allows selection of one of the various TI COFF versions. The latest of this
-format
writing is 2; versions 0 and 1 are also supported. The TI COFF versions also vary in header byte-order
format; will read any version or byte order, but the output header format depends on the default
ld
specified by the specific target.
5.8.

and WIN32 (cygwin/mingw)

ld
This section describes some of the win32 specific
for detailed decription of the command line options mentioned here.
import libraries
The standard Windows linker creates and uses so-called import libraries, which contains infor-
mation for linking to dll's. They are regular static archives and are handled as any other static
archive. The cygwin and mingw ports of
provided with the
exporting DLL symbols
The cygwin/mingw
using auto-export functionality
By default
following command line options:
-export-all-symbols [This is the default]
•
-exclude-symbols
•
section except that any code in this section will not be uploaded
.infomem
command line option.
-out-implib
has several ways to export symbols for dll's.
ld
exports symbols with the auto-export functionality, which is controlled by the
ld
section.
.bss
issues. See Section 3.1 Command Line Options
ld
have specific support for creating such libraries
ld
61