Table of Contents
Advertisement
Program-wide Analysis and Optimization
The PDB can be specified by setting the environment variable
(gcc960 driver) or
I960PDB
can also specify the PDB at compiler invocation time with the
(gcc960) or
(ic960) option, as shown in the examples below.
Yd, dir
gcc960
-Zmypdb
foo.o
ic960
-Yd,mypdb
Compiling for Program-wide Optimization with the
fdb Option
All modules subject to program-wide optimization must be initially
compiled with the
fdb
Chapter 3, ic960 Driver). Using this option causes the insertion of
program database information in the object modules, and it implies a
minimum module-local optimization level of
local optimization levels are allowed).
Compiling with the
fdb
for the object modules in any way; this option simply makes information
collected during the initial compilation of the modules available to the
global decision making and optimization step.
Global Decision Making and Optimization Using the
gcdm Option
The tool that performs the global decision making and optimization step is
called gcdm960. gcdm960 is invoked from within the linker when the
option is used. You can also use the
gcdm
driver (gcc960 or ic960) to pass this option to the linker. Using the
option causes gcdm960 to:
•
automatically build and manage optimized object modules in the PDB
•
arrange with the linker for optimized object modules from the PDB to
be automatically substituted for some or all of the original object
modules in the final program.
(ic960 driver) to the correct location. You
foo.o
option (described in Chapter 2, gcc960 Driver and
O1
option does not change the code or data generated
gcdm
G960PDB
Z dir
(although higher module-
option in the compiler
gcdm
4
4-3
Advertisement
Table of Contents
