HP-MPI Version 1.1 for Windows Release Note
HP-MPI V1.1 for Windows Release Note
Known Problems and Workarounds
54
Known Problems and Workarounds
• The Fortran interface provided in HP-MPI assumes a style calling convention of C-by-
reference. That is, function names are not decorated as _function@bytes, arguments are
passed by reference, string length arguments are passed by value after the other
arguments, and the caller cleans the stack. This is not compatible with Compaq Visual
Fortran (CVF) or other compilers using the STDCALL calling convention for Fortran
routines (e.g. /iface:cvf in Intel Fortran). The STDCALL calling convention decorates the
function names, passes string lengths by value directly after the string, and has the callee
clean the stack.
• Current IB drivers (Voltaire 2.2.493.409) may suffer a loss of performance after sending
message sizes of 4065 bytes to 4128 bytes when using WSD. Any messages sent
afterwards may perform at about half the bandwidth that they performed at before the
4065-4128 byte message was sent. This does not affect IBAL protocol. Contact Voltaire for
the fix (which is unavailable at the time of this release).
• Commands submitted via the Windows Compute Cluster Pack scheduler are limited to
480 characters in length. It should be possible to 'wrap' longer commands inside a batch
file.
• On an HP-MPI CCS job, the user may receive the following error:
mpirun: ERROR: CCP resource environment variables are not in expected
format. Are you setting CCS standard environment variables for
application?
Most CCS jobs are given a default name. But it is possible to submit a job with no
'jobname'. HP-MPI attempts to read this jobname, and if it doesn’t exist, it incorrectly
believes it is not operating in a CCS job environment and will issue the error message
above.
The workaround is to always provide a CCS job name if one is not assigned by default.
This issue will be fixed in the next release.