Input Section Directives In Assembly Code; Input Section Directives In C/C++ Source Files - Analog Devices VisualDSP++ 3.5 Manual

Compiling and Assembling
Each input section in the
the source code. Depending on whether the source is C, C++, or assembly,
different conventions are used to name an input section (see Chapter 3,
"Linker Description

Input Section Directives in Assembly Code

A directive defines a section in assembly source. This directive
.SECTION
must precede its code or data.
Example (for Blackfin processors)
.SECTION Library_Code_Space;
.global _abs;
_abs:
R0 = ABS R0;
RTS;
_abc.end
In this example, the assembler places the global symbol/label
code after the label into the input section
cesses this file into object code.

Input Section Directives in C/C++ Source Files

Typically, C/C++ code does not specify an input section name, so the
compiler uses a default name. By default, the input section names
(for code) and
are defined in
In C/C++ source files, you can use the optional
guage extension to define sections.
Example 1
While processing the following code, the compiler stores the
in the
ext_data
erated from
func1
1-4
file requires a unique name, as specified in
.LDF
File").
/* Take absolute value of input */
(for data) are used. Additional input section names
data1
files.
.LDF
input section of the .
in an input section named
VisualDSP++ 3.5 Linker and Utilities Manual
/* Section Directive
Library_Code_Space
section("name")
file and also stores the code gen-
DOJ
.
extern
for 16-Bit Processors
*/
and the
_abs
, as it pro-
program
C lan-
variable
temp