Before You Begin |
This manual describes the performance analysis tools that are available with the Sun Open Net Environment (Sun ONE) Studio Compiler Collection product.
This manual is intended for application developers with a working knowledge of Fortran, C, C++, or Java, the Solaris operating environment, and UNIX® operating system commands. Some knowledge of performance analysis is helpful but is not required to use the tools.
Chapter 1 introduces the performance analysis tools, briefly discussing what they do and when to use them.
Chapter 2 is a tutorial that demonstrates how to use the Collector and Performance Analyzer to assess the performance of five example programs.
Chapter 3 describes the data collected by the Collector and how the data is converted into metrics of performance.
Chapter 4 describes how to use the Collector to collect timing data, synchronization delay data, and hardware event data from your program.
Chapter 5 describes the features of the Performance Analyzer graphical user interface. Note: you must have a license to use the Performance Analyzer.
Chapter 6 describes how to use the er_print command line interface to analyze the data collected by the Collector.
Chapter 7 describes the process of converting the data collected by the Collector into performance metrics and how the metrics are related to program structure.
Chapter 8 presents information on the utilities that are provided for manipulating and converting performance experiments and viewing annotated source code and disassembly code without running an experiment.
Appendix A describes the UNIX profiling tools prof, gprof, and tcov. These tools provide timing information and execution frequency statistics.
The "pipe" or "bar" symbol separates arguments, only one of which may be chosen. |
|||
The colon, like the comma, is sometimes used to separate arguments. |
|||
The compiler collection components and man pages are not installed into the standard /usr/bin/ and /usr/share/man directories. To access the compilers and tools, you must have the compiler collection component directory in your PATH environment variable. To access the man pages, you must have the compiler collection man page directory in your MANPATH environment variable.
For more information about the PATH variable, see the csh(1), sh(1), and ksh(1) man pages. For more information about the MANPATH variable, see the man(1) man page. For more information about setting your PATH variable and MANPATH variables to access this release, see the installation guide or your system administrator.
Use the steps below to determine whether you need to change your PATH variable to access the compilers and tools.
To Determine Whether You Need to Set Your PATH Environment Variable |
1. Display the current value of the PATH variable by typing the following at a command prompt.
% echo $PATH |
2. Review the output to find a string of paths that contain /opt/SUNWspro/bin/.
If you find the path, your PATH variable is already set to access the compilers and tools. If you do not find the path, set your PATH environment variable by following the instructions in the next procedure.
To Set Your PATH Environment Variable to Enable Access to the Compilers and Tools |
1. If you are using the C shell, edit your home .cshrc file. If you are using the Bourne shell or Korn shell, edit your home .profile file.
2. Add the following to your PATH environment variable.
Use the following steps to determine whether you need to change your MANPATH variable to access the man pages.
To Determine Whether You Need to Set Your MANPATH Environment Variable |
1. Request the dbx man page by typing the following at a command prompt.
% man dbx |
If the dbx(1) man page cannot be found or if the man page displayed is not for the current version of the software installed, follow the instructions in the next procedure for setting your MANPATH environment variable.
To Set Your MANPATH Environment Variable to Enable Access to the Man Pages |
1. If you are using the C shell, edit your home .cshrc file. If you are using the Bourne shell or Korn shell, edit your home .profile file.
2. Add the following to your MANPATH environment variable.
You can access the documentation at the following locations:
The docs.sun.com web site (http://docs.sun.com) enables you to read, print, and buy Sun Microsystems manuals through the Internet. If you cannot find a manual, see the documentation index that is installed with the software on your local system or network.
The documentation is provided in accessible formats that are readable by assistive technologies for users with disabilities. You can find accessible versions of documentation as described in the following table. If your software is not installed in the /opt directory, ask your system administrator for the equivalent path on your system.
The following table describes related documentation that is available at file:/opt/SUNWspro/docs/index.html and http://docs.sun.com. If your software is not installed in the /opt directory, ask your system administrator for the equivalent path on your system.
The following table describes related documentation that is available through the docs.sun.com web site.
Visit http://www.sun.com/developers/studio and click the Compiler Collection link to find these frequently updated resources:
You can find additional resources for developers at http://www.sun.com/developers/.
If you have technical questions about this product that are not answered in this document, go to:
http://www.sun.com/service/contacting
Sun is interested in improving its documentation and welcomes your comments and suggestions. Email your comments to Sun at this address:
Please include the part number (817-0922-10) of your document in the subject line of your email.
Copyright © 2003, Sun Microsystems, Inc. All rights reserved.