1MPI_Type_create_extent(3)           LAM/MPI          MPI_Type_create_extent(3)
2
3
4

NAME

6       MPI_Type_create_extent -  Create a resized datatype
7

SYNOPSIS

9       #include <mpi.h>
10       int
11       MPI_Type_create_resized(MPI_Datatype type, MPI_Aint lb,
12                             MPI_Aint extent, MPI_Datatype *newtype)
13

INPUT PARAMETERS

15       type   - Inpute datatype
16       lb     - New lower bound of the datatype
17       extent - New extent of the datatype
18
19

OUTPUT PARAMETER

21       newtype
22              - New resized type
23
24

NOTES FOR FORTRAN

26       All  MPI routines in Fortran (except for MPI_WTIME and MPI_WTICK ) have
27       an additional argument ierr at the end of the argument list.   ierr  is
28       an  integer and has the same meaning as the return value of the routine
29       in C.  In Fortran, MPI routines are subroutines, and are  invoked  with
30       the call statement.
31
32       All MPI objects (e.g., MPI_Datatype , MPI_Comm ) are of type INTEGER in
33       Fortran.
34
35

ERRORS

37       If an error occurs in an MPI function, the current MPI error handler is
38       called  to  handle  it.   By default, this error handler aborts the MPI
39       job.  The error handler may be changed with  MPI_Errhandler_set  ;  the
40       predefined  error  handler MPI_ERRORS_RETURN may be used to cause error
41       values to be returned (in C and Fortran; this  error  handler  is  less
42       useful  in  with  the  C++  MPI bindings.  The predefined error handler
43       MPI::ERRORS_THROW_EXCEPTIONS should be used in C++ if the  error  value
44       needs  to  be recovered).  Note that MPI does not guarantee that an MPI
45       program can continue past an error.
46
47       All MPI routines (except MPI_Wtime and  MPI_Wtick  )  return  an  error
48       value;  C routines as the value of the function and Fortran routines in
49       the last argument.  The C++ bindings for MPI do not return  error  val‐
50       ues;  instead,  error values are communicated by throwing exceptions of
51       type MPI::Exception (but not by default).  Exceptions are  only  thrown
52       if the error value is not MPI::SUCCESS .
53
54
55       Note  that  if  the MPI::ERRORS_RETURN handler is set in C++, while MPI
56       functions will return upon an error, there will be no  way  to  recover
57       what the actual error value was.
58       MPI_SUCCESS
59              - No error; MPI routine completed successfully.
60       MPI_ERR_TYPE
61              - Invalid datatype argument.  May be an uncommitted MPI_Datatype
62              (see MPI_Type_commit ).
63       MPI_ERR_OTHER
64              - Other error; use  MPI_Error_string  to  get  more  information
65              about this error code.
66       MPI_ERR_INTERN
67              -  An  internal error has been detected.  This is fatal.  Please
68              send a bug report to the LAM mailing list  (see  http://www.lam-
69              mpi.org/contact.php ).
70
71

SEE ALSO

73       MPI_Type_get_true_extent(3), MPI_Type_create_resized(3)
74
75

MORE INFORMATION

77       For more information, please see the official MPI Forum web site, which
78       contains the text of both the MPI-1 and MPI-2 standards.   These  docu‐
79       ments  contain  detailed  information  about each MPI function (most of
80       which is not duplicated in these man pages).
81
82       http://www.mpi-forum.org/
83

LOCATION

85       tresize.c
86
87
88
89LAM/MPI 7.1.2                      2/23/2006         MPI_Type_create_extent(3)
Impressum