Shared_Memory - Analog Devices VisualDSP++ 3.5 Manual

Linker and utilities manual for 16-bit processors
Hide thumbs Also See for VisualDSP++ 3.5:
Table of Contents

Advertisement

LDF Commands
For
FIRST_FIT
OVERLAY_INPUT{}
output section's run-time memory segment, according to
First-In-First-Out (FIFO) order.
(
BEST_FIT
For
BEST_FIT
OVERLAY_INPUT{}
output section's run-time memory segment, but splits these over-
lays to optimize memory usage.
RESOLVE_LOCALLY()
controls whether the linker generates PLIT entries for function
calls that are resolved within the overlay.
The default
entries for locally resolved functions within the overlay.
RESOLVE_LOCALLY(FALSE)
regardless of whether they are locally resolved within the overlay.
SIZE()
occupied by an overlay.

SHARED_MEMORY{}

L
The only ADSP-218x/9x DSP that supports
the ADSP-2192 DSP. All Blackfin processors support this
function.
The linker can produce two types of executable output—
files. A
.SM
.DXE
Shared memory executable (
multiprocessor system. The
duce
files.
.SM
page 5-38.
3-48
, the linker splits the input sections listed in
into a set of overlays that can each overlay the
– Not currently available.
, the linker splits the input sections listed in
into a set of overlays that can each overlay the
– When applied to an overlay, this command
RESOLVE_LOCALLY(TRUE)
– Sets an upper limit to the size of the memory that may be
file runs in a single-processor system's address space.
) files reside in the shared memory of a
.SM
SHARED_MEMORY{}
For more information, see "SHARED_MEMORY{}" on
VisualDSP++ 3.5 Linker and Utilities Manual
does not generate PLIT
generates PLIT entries for all functions,
command is used to pro-
is
SHARED_MEMORY{}
files and
.DXE
for 16-Bit Processors

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the VisualDSP++ 3.5 and is the answer not in the manual?

Questions and answers

Related Products for Analog Devices VisualDSP++ 3.5

Table of Contents