Chapter 1. Getting Started With ProMP
Prev   Next

Chapter 1. Getting Started With ProMP

This chapter describes how to run the ProDev WorkShop ProMP parallel analyzer. It contains the following sections:

Note: This product was formerly called WorkShop Pro MPF.

ProMP requires the following software versions (or later versions):

To determine what software is installed on your system, enter the following at the shell prompt:

% versions

The process of using the parallel analyzer involves two steps:

  1. Compiling a program with the necessary options. See “Compiling a Program for ProMP Use” for details.

  2. Reading the compiled files. See “Reading Files With the Parallel Analyzer View” for details.

For a more detailed introduction to the parallel analyzer view, follow one of the following tutorials:

Compiling a Program for ProMP Use

Before starting the parallel analyzer to analyze your source (in this case, Fortran source), run your compiler with the appropriate auto-parallelizing option. For the tutorials presented in subsequent chapters, makefiles are provided. You can adapt these to your specific source or enter one of the following commands:

% f90 -apo keep -O3 sourcefile.f
% f77 -apo keep -O3 sourcefile.f

The compiler generates its usual output files and an analysis file ( sourcefile.anl), which the parallel analyzer reads.

The command-line options have the following effects:

  • -apo keep: saves a .anl file, which has necessary information for the parallel analyzer view.

  • -O3: sets the compiler for aggressive optimization. The optimization focuses on maximizing code performance, even if that requires extending the compile time or relaxing language rules.

See the MIPSpro Fortran 77 Programmer's Guide, MIPSpro Fortran 90 Commands and Directives Reference Manual and the f90(1) or f77(1) man pages for more information.

: The cvpav command assumes that the -apo keep option was used on each of the Fortran source files named in a single executable or file specifying several executables. If this is not the case, a warning message is posted, and the unprocessed files are marked by an error icon within the parallel analyzer's subroutines and files view, see “Subroutines and Files View” in Chapter 6.

Generating Other Reports

While they are not part of the parallel analyzer view, other parallelization reports can be generated using the following command-line options:

  • -apo list: produces a .l file, a listing of those parts of the program that can run in parallel and those that cannot.

  • -mplist: generates the equivalent parallelized program in a .w2f.f file.

These reports are text files that can be used for analysis.

OpenMP and PCF Directive Support

The MIPSpro Fortran compilers support OpenMP directives, unless you are compiling with the -o32 option. If you put OpenMP directives in your o32 code, they are treated as comments rather than being interpreted. For more information on OpenMP directives, see the documentation for your compiler system, or the OpenMP Architecture Review Board web site at the following URL: http://www.openmp.org/.

Although using OpenMP directives is recommended, the compilers still support PCF directives.

Reading Files With the Parallel Analyzer View

You can run the parallel analyzer view on any of the following objects:

  • A source file

  • An executable

  • A list of files

To run the parallel analyzer view for one of these cases, enter one of the following commands:

% cvpav -f sourcefile.f   
% cvpav -e executable   
% cvpav -F fileset-file

The cvpav command reads information from all source files compiled into the application.

The parallel analyzer view has several other command line options, as well as several X Window System resources that you can set. See the cvpav(1) man page for more information.

Prev Table of Contents Next
About This Guide  Chapter 2. Tutorial: Examining Loops for FORTRAN 77