1MPI_Type_create_hvector(3) LAM/MPI MPI_Type_create_hvector(3)
2
3
4
6 MPI_Type_create_hvector - Create extended hvector derived datatype
7
9 #include <mpi.h>
10 int
11 MPI_Type_create_hvector(int count, int length, MPI_Aint stride,
12 MPI_Datatype oldtype, MPI_Datatype *newtype)
13
15 count - Number of blocks (nonnegative integer)
16 lengths
17 - Number of elements in each block (nonnegative integer)
18 stride - Number of bytes between start of each block (integer)
19 oldtype
20 - Old datatype (handle)
21
22
24 newtype
25 - New datatype (handle)
26
27
29 All MPI routines in Fortran (except for MPI_WTIME and MPI_WTICK ) have
30 an additional argument ierr at the end of the argument list. ierr is
31 an integer and has the same meaning as the return value of the routine
32 in C. In Fortran, MPI routines are subroutines, and are invoked with
33 the call statement.
34
35 All MPI objects (e.g., MPI_Datatype , MPI_Comm ) are of type INTEGER in
36 Fortran.
37
38
40 If an error occurs in an MPI function, the current MPI error handler is
41 called to handle it. By default, this error handler aborts the MPI
42 job. The error handler may be changed with MPI_Errhandler_set ; the
43 predefined error handler MPI_ERRORS_RETURN may be used to cause error
44 values to be returned (in C and Fortran; this error handler is less
45 useful in with the C++ MPI bindings. The predefined error handler
46 MPI::ERRORS_THROW_EXCEPTIONS should be used in C++ if the error value
47 needs to be recovered). Note that MPI does not guarantee that an MPI
48 program can continue past an error.
49
50 All MPI routines (except MPI_Wtime and MPI_Wtick ) return an error
51 value; C routines as the value of the function and Fortran routines in
52 the last argument. The C++ bindings for MPI do not return error val‐
53 ues; instead, error values are communicated by throwing exceptions of
54 type MPI::Exception (but not by default). Exceptions are only thrown
55 if the error value is not MPI::SUCCESS .
56
57
58 Note that if the MPI::ERRORS_RETURN handler is set in C++, while MPI
59 functions will return upon an error, there will be no way to recover
60 what the actual error value was.
61 MPI_SUCCESS
62 - No error; MPI routine completed successfully.
63 MPI_ERR_TYPE
64 - Invalid datatype argument. May be an uncommitted MPI_Datatype
65 (see MPI_Type_commit ).
66 MPI_ERR_COUNT
67 - Invalid count argument. Count arguments must be non-negative;
68 a count of zero is often valid.
69 MPI_ERR_ARG
70 - Invalid argument. Some argument is invalid and is not identi‐
71 fied by a specific error class. This is typically a NULL
72 pointer or other such error.
73 MPI_ERR_OTHER
74 - Other error; use MPI_Error_string to get more information
75 about this error code.
76
77
79 MPI_Type_create_hindexed(3), MPI_Type_create_struct(3),
80 MPI_Get_address(3)
81
82
84 For more information, please see the official MPI Forum web site, which
85 contains the text of both the MPI-1 and MPI-2 standards. These docu‐
86 ments contain detailed information about each MPI function (most of
87 which is not duplicated in these man pages).
88
89 http://www.mpi-forum.org/
90
92 tcreatehvector.c
93
94
95
96LAM/MPI 7.1.2 2/23/2006 MPI_Type_create_hvector(3)