Code Profiling Utilities Manual

Building the Application
HP Code Profiling Utilities Manual—542684-003
3-4
Compiling the Source Files
If you do not specify the basename option, then the source files used with profuse
compilations must be in the same locations (that is, they must have the same
pathnames) as when the same files were compiled with the profgen option.
For more information about using the basename option, see Section 6, Optimizing a
Program Using Profile-Guided Optimization.
codecov Option
This option directs the compiler to create an instrumented object file and to create or
add to an existing SPI file for use in generating a code coverage report. The codecov
option is summarized in Table 3-2 .
profdir Option
This option specifies where the instrumented process will create the raw data file. The
specified path name is used exactly as specified. If the application will run in the
Guardian environment, specify a Guardian subvolume. If the application will run in the
OSS environment, specify an OSS directory. Table 3-3 summarizes the profdir option.
If you omit the profdir option, the raw data file will be created in the current working
directory or default subvolume.
The profdir option is ignored unless the profgen or codecov option is also specified.
Table 3-2. codecov option
Option Name
Supported
Environment Compiler
CODECOV Guardian CCOMP
CPPCOMP
ECOBOL
EPTAL
-Wcodecov OSS, Windows c89, c99,
ecobol
-codecov Windows eptal
Table 3-3. profdir Option
Option Name
Supported
Environment Compiler
PROFDIR
" Guardian-filename "Guardian CCOMP
CPPCOMP
EPTAL
-Wprofdir=
pathname OSS, Windows c89, c99
-profdir=
pathname Windows eptal