Copyright (C) 2000-2012 |
Whole document tree
4.4 Sub-Sections
Assembled bytes
conventionally
fall into two sections: text and data.
You may have separate groups of
data in named sections
text or data
that you want to end up near to each other in the object file, even though they
are not contiguous in the assembler source. Subsections are optional. If you do not use subsections, everything goes in subsection number zero.
Each subsection is zero-padded up to a multiple of four bytes.
(Subsections may be padded a different amount on different flavors
of
Subsections appear in your object file in numeric order, lowest numbered
to highest. (All this to be compatible with other people's assemblers.)
The object file contains no representation of subsections;
To specify which subsection you want subsequent statements assembled
into, use a numeric argument to specify it, in a `.text
expression' or a `.data expression' statement.
When generating COFF output, you
can also use an extra subsection
argument with arbitrary named sections: `.section name,
expression'.
Expression should be an absolute expression.
(See section 6. Expressions.) If you just say `.text' then `.text 0'
is assumed. Likewise `.data' means `.data 0'. Assembly
begins in
Each section has a location counter incremented by one for every byte
assembled into that section. Because subsections are merely a convenience
restricted to
This document was generated by root on January, 30 2002 using texi2html |