Analog Devices VisualDSP++ 3.5 Manual page 298

Linking for Overlay Memory
INPUT_SECTIONS(overlay1.doj( program))
// Tell the linker that all of the code in the overlay must
// fit into the "run" memory all at once. ALGORITHM(ALL_FIT)
// allows the linker to break the code into several
// overlays as necessary (in the event that not all
// of the code fits)
ALGORITHM( ALL_FIT )
SIZE(0x100)
} > mem_ovly
// This is the second overlay. Note that these
// OVERLAY_INPUT commands must be contiguous in the LDF
// to occupy the same "run-time" memory.
OVERLAY_INPUT {
OVERLAY_OUTPUT( overlay2.ovl )
INPUT_SECTIONS(overlay2.doj( program)))
ALGORITHM( ALL_FIT )
SIZE( 0x100)
} > mem_ovly
} > program
/* The instructions generated by the linker in the .plit
section must be placed in non-overlay memory. Here is
the sole specification telling the linker where to
place these instructions */
.plit {
} > MEM_PROGRAM
DXE_DATA1 {
INPUT_SECTIONS ( $OBJECTS(data1) $LIBRARIES(data1))
INPUT_SECTION_ALIGN(1)
INPUT_SECTIONS( $OBJECTS(constdata) $LIBRARIES(constdata))
INPUT_SECTION_ALIGN(1)
INPUT_SECTIONS( $OBJECTS(ctor) $LIBRARIES(ctor) )
} >MEM_PROGRAM
C-20
.
// linker insert instructions here
VisualDSP++ 3.5 Linker and Utilities Manual
for 16-Bit Processors