ID Number: Q44928
4.06
MS-DOS
docerr
Summary:
Documentation for the /PADDATA and /PADCODE switches is not included
in the online help for the LINK utility version 4.06 or in the
documentation for the Microsoft QuickC Compiler version 2.0. The
documentation is included with QuickC version 2.5.
More Information:
The /PADC[ODE]:padsize option causes LINK to add filler bytes to the
end of each code module. The option is followed by a colon and the
number of bytes to add. (Decimal radix is assumed; however, you can
specify special octal or hexadecimal numbers by using a C-language
prefix.) Thus, the following adds an additional 256 bytes to each code
module:
/PADCODE:256
The default size for code-module padding is 0 bytes.
The /PADD[ATA]:padsize option performs a function similar to /PADCODE,
except that it specifies padding for data segments (or data modules if
the program uses small or medium-memory model). Thus, the following
adds an additional 32 bytes to each data module:
/PADDATA:32
The default size for data-segment padding is 16 bytes. Note that if
you specify too large a value for padsize, you may exceed the 64K
limitation on the size of the default data segment.
These two options are useful in conjunction with QuickC version 2.0's
incremental linking option; using them correctly increases the
incremental linking speed of a program.
These two options are documented on page 64 in the update section of
the Microsoft C Optimizing Compiler version 5.1 "CodeView and
Utilities, Microsoft Editor, Mixed-Language Programming Guide" manual
and in the online help for C version 6.0.
Additional reference words: 6.00 5.10 2.00 2.50