HP-MPI V2.3 for Linux Release Note

Interval timer functionality used by HP-MPI on HP XC systems can conflict with
gprof data collection phase requirements. Set the following two environment
variables to workaround this issue:
% export MPI_FLAGS=s0
% export GMON_OUT_PREFIX=/tmp/app_name
In the above example, setting MPI_FLAGS disables the HP-MPI conflicting use of
interval timers. See the mpienv(1) manpage for descriptions of MPI_FLAG settings.
Because this setting also disables message progression monitoring, use it with
well-behaved programs only.
In the above example, the second setting causes gprof data collection files to be
named /tmp/app_name.PID (where PID is the process ID number). The prefix
is set arbitrarily and makes the file unique in cases where the same PID is given
on different nodes.
The HP-MPI V2.3 library for Linux contains a dependency which requires
libpthread. The mpicc, mpif90, etc. compiler wrapper scripts automatically
add the necessary -lpthread, but manually linked applications must explicitly
add -lpthread.
Profiling routines built for C calls do not cause the corresponding Fortran calls to
be wrapped automatically. To profile Fortran routines, separate wrappers need
to be written for the Fortran calls.
HP-MPI complies with the MPI-1.2 standard, which defines bindings for Fortran
77 and C, but not Fortran 90 or C++. HP-MPI also complies with the C++ binding
definitions detailed in the MPI-2 standard. However, the C++ bindings are not
thread safe and should not be used with the HP-MPI threaded libraries (for
example, libmtmpi). HP-MPI does not provide bindings for Fortran 90. Some
features of Fortran 90 might interact with MPI non-blocking semantics to produce
unexpected results. Consult the HP-MPI User’s Guide for details.
When using the HP Caliper profiling tool with HP-MPI applications, it might be
necessary to specify the following environment variable setting in order to avoid
an application abort.
% setenv HPMPI_NOPROPAGATE_SUSP 1
or
$ export HPMPI_NOPROPAGATE_SUSP=1
To use the -tv option to mpirun, the TotalView binary must be in the users PATH,
or the TOTALVIEW environment variable must be set to the full path of the
TotalView binary.
% export TOTALVIEW=/usr/toolworks/totalview/bin/totalview
Extended collectives with intercommunicators are not profiled by the HP-MPI
lightweight instrumentation mode.
31