Vendor Update Form

Click here to see the form without HTML.

This is the update form for the MPI-2 implementation listing that can
be found at:

	http://www.lam-mpi.org/mpi/implementations/

There is no HTML form for updates; we would prefer that a
representative from each MPI implementation e-mail this completed form
to us at mpi dash list at lam dash mpi dot org.

==========================================================================

- Is this an update to an MPI implementation that we already have
  listed, or a new entry? (update or new)

- Is your implementation a commercial product?  (yes or no)

- If your implementation completely free of charge?  (yes or no)

- Is the source code available for your implementation?  (yes or no)

- What is the current version number of your implementation?

- What platforms (software/hardware, to include network interconnect
  devices) does your implementation support?

- Please provide a contact e-mail address and/or URL.

- Excluding MPI_CANCEL, does your implementation support all MPI-1.2
  functionality?  If not, please list what you do support.

- Does your MPI-1 implementation include full support for MPI_CANCEL?
  If you do not have full support for MPI_CANCEL, please describe what
  you do support.

- Since many MPI-2 features are unrelated from each other, many
  implementations are writing MPI-2 in a piecemeal fashion.  Please
  indicate how much support your implementation includes for the
  following MPI-2 sections by answering "none", "some", or "all"
  below.  If you indicate "none" or "some", please indicate your plans
  (tentative/non-committal plans are fine) for implementing that
  functionality below each line.


None, Some
 or All                  MPI-2 section number and name/topic
---------  ---------------------------------------------------------------
           Miscellany
           * 4.1 mpiexec
           * 4.2 MPI_INIT(NULL, NULL)
           * 4.4 MPI_TYPE_CREATE_INDEXED_BLOCK
           * 4.5 MPI_STATUS_IGNORE / MPI_STATUSES_IGNORE
           * 4.6 Invalid keyval error class
           * 4.7 Committing a committed datatype
           * 4.8 User functions at termination
           * 4.9 MPI_FINALIZED
           * 4.10 MPI_Info handling
           * 4.11 MPI memory handling
           * 4.12 Language interoperability
           * 4.13 Error handlers on communicators, windows, and datatypes
           * 4.14 New datatype manipulation functions
           * 4.15 New predefined datatypes
           * 4.16 Canonical MPI_PACK and MPI_UNPACK

           Process Creation and Management
           * 5.3 Process manager interface
           * 5.4 Establishing communication
           * 5.5 Other dynamic functionality

           One-Sided Communications
           * 6.2 Initialization
           * 6.3 Communication calls
           * 6.4 Synchronization calls
           * 6.6 Error handling

           Extended Collective Operations
           * 7.2 Intercommunucator constructors
           * 7.3 Extended collective operations

           External Interfaces
           * 8.2 Generalized requests
           * 8.3 Associating information with status
           * 8.4 Naming objects
           * 8.5 Error classes, codes, and handlers
           * 8.6 Decoding a datatype
           * 8.7 MPI and threads
           * 8.8 New attribute caching functions
           * 8.9 Duplicating a datatype

           I/O
           * 9.2 File manipulation
           * 9.3 File views
           * 9.4 Data access
           * 9.5 File interoperability
           * 9.6 Consistency and semantics
           * 9.7 I/O error handling
           * 9.8 I/O error classes

           Language Bindings
           * 10.1 C++ (for MPI 1.2 functions)
           * 10.1 C++ (for MPI 2 functions)
           * 10.2 Fortran support
---------  ---------------------------------------------------------------

- How much support for Interoperable MPI (IMPI) does your
  implementation include (none, some, all)?  If you indicate "none" or
  "some", please indicate your plans (tentative/non-committal plans
  are fine) for implementing that functionality.

- Please specify any other information that should be included about
  your MPI implementation.

==========================================================================

Please send this form to mpi-implementation-list at lam dash mpi dot
org.  You are under no obligation to do so, but your cooperation would
greatly enhance our ability to provide a more complete MPI resource to
the public.

Thank you for your time and consideration.