NAME

pixstats − analyze program execution

SYNOPSIS

pixstats program [ options ]

PARAMETERS

programName of the program executable to be instrumented.  This program should be compiled with the −g1, −g2, or −g3 flag to obtain more complete profiling information.  If the default symbol table level (−g0) has been used, line number information, static procedure names, and file names are unavailable to the profiling code. 

FLAGS

The pixstats command accepts the following options:

−cycle ns
Assume a ns cycle time when converting cycle counts to seconds. 

−clockAssume 1000/ns cycle time when converting counts to seconds. 

−disassemble
Disassemble and show the analyzed object code.

−dislimit f
Limit the disassembly to blocks with f% frequency. 

−nocounts
Use 1 for each basic block count.

DESCRIPTION

The pixstats program analyzes a program’s execution characteristics.  To use pixstats, first use pixie(1) to translate and instrument the executable object module for the program.  Next, execute the translation on an appropriate input.  This produces a .Counts file.  Finally, use pixstats to generate a detailed report on opcode frequencies, interlocks, a mini-profile, and more. 

RESTRICTIONS

The pixstats program models execution assuming a perfect memory system.  Memory system events such as cache misses will increase execution above the pixstats predictions. 

RELATED INFORMATION

pixie(1), prof(1)

Programmer’s Guide