Code Profiling Utilities Manual

Building the Application
HP Code Profiling Utilities Manual—542684-003
3-3
Build the Application
To create a new SPI file instead of adding to an existing one, you can:
•
Move, rename, or delete the old file.
•
Compile the application in a different directory or subvolume.
Build the Application
Compiling the Source Files
The compilers provided several options for use when compiling your application for
code profiling:
•
basename Option
•
codecov Option
•
profdir Option
•
profgen Option
For detailed syntax descriptions of these options, see the appropriate compiler manual.
basename Option
Information saved in the raw data files generated by running the instrumented object
files includes the names of the source files to be optimized. By default, these are fully
qualified source file names, following naming conventions for the respective host
environments (Guardian, OSS, or Windows). If the basename option is specified on the
compiler command line, then only the base part (the file name part) of the source files
name is included in the raw data file generated when the program is executed.
The basename option is summarized in Table 3-1.
The basename option makes it possible for source files compiled with the profuse
option to be in different locations than they were when compiled with the profgen
option. In particular, the source files can be in different environments (Guardian, OSS,
or Windows) for profgen and profuse compilations.
Note. The basename option is intended for use only with the profgen option; it should not be
used with the codecov option.
Table 3-1. basename Option
Option Name
Supported
Environment Compiler
BASENAME Guardian CCOMP, CPPCOMP,
EPTAL
-Wbasename OSS, Windows c89, c99
-basename Windows eptal