Attribute keys can be allocated in one language and freed in another. Similarly, attribute values can be set in one language and accessed in another. To achieve this, attribute keys will be allocated in an integer range that is valid all languages. The same holds true for system-defined attribute values (such as MPI_TAG_UB, MPI_WTIME_IS_GLOBAL, etc.).
Attribute keys declared in one language are associated with copy and delete functions in that language (the functions provided by the MPI_ XXX_CREATE_KEYVAL call). When a communicator is duplicated, for each attribute, the corresponding copy function is called, using the right calling convention for the language of that function; and similarly, for the delete callback function.
Advice
to implementors.
This requires that attributes be tagged either as
``C'' or ``Fortran''
and that the language tag be checked in order to use
the right calling convention for the callback function.
( End of advice to implementors.)
The attribute manipulation functions described in
Section Caching
defines
attributes arguments to be of type void* in C, and of type
INTEGER, in Fortran. On some systems,
INTEGERs will have 32 bits, while
C pointers will have
64 bits. This is a problem if communicator attributes are used to
move information from a Fortran caller to a
C callee, or
vice-versa.
MPI behaves as if it stores, internally, address sized attributes. If Fortran INTEGERs are smaller, then the (deprecated) Fortran function MPI_ATTR_GET will return the least significant part of the attribute word; the (deprecated) Fortran function MPI_ATTR_PUT will set the least significant part of the attribute word, which will be sign extended to the entire word. (These two functions may be invoked explicitly by user code, or implicitly, by attribute copying callback functions.)
As for addresses, new functions are provided that manipulate Fortran address sized attributes, and have the same functionality as the old functions in C. These functions are described in Section Caching. Users are encouraged to use these new functions.
MPI supports two types of attributes: address-valued (pointer) attributes, and integer-valued attributes. C attribute functions put and get address-valued attributes. Fortran attribute functions put and get integer-valued attributes. When an integer-valued attribute is accessed from C, then MPI_ XXX_get_attr will return the address of (a pointer to) the integer-valued attribute, which is a pointer to MPI_Aint if the attribute was stored with Fortran MPI_ XXX_SET_ATTR, and a pointer to int if it was stored with the deprecated Fortran MPI_ATTR_PUT. When an address-valued attribute is accessed from Fortran, then MPI_ XXX_GET_ATTR will convert the address into an integer and return the result of this conversion. This conversion is lossless if new style attribute functions are used, and an integer of kind MPI_ADDRESS_KIND is returned. The conversion may cause truncation if deprecated attribute functions are used. In C, the deprecated routines MPI_Attr_put and MPI_Attr_get behave identical to MPI_Comm_set_attr and MPI_Comm_get_attr.
Example
Setting an attribute in C and reading in C or Fortran.
A. Setting an attribute value in C
B. Reading the attribute value in C
C. Reading the attribute value with (deprecated) Fortran MPI-1 calls
D. Reading the attribute value with Fortran MPI-2 calls
Example
Setting an attribute in Fortran and reading in C or Fortran.
A. Setting an attribute value with the (deprecated) Fortran MPI-1 call
B. Reading the attribute value in C
C. Reading the attribute value with (deprecated) Fortran MPI-1 calls
D. Reading the attribute value with Fortran MPI-2 calls
Example
Setting an attribute in Fortran and reading in C or Fortran.
A. Setting an attribute value via a Fortran MPI-2 call
B. Reading the attribute value in C
C. Reading the attribute value with (deprecated) Fortran MPI-1 calls
D. Reading the attribute value with Fortran MPI-2 calls
The predefined MPI attributes can be integer valued or address-valued. Predefined integer valued attributes, such as MPI_TAG_UB, behave as if they were put by a call to the deprecated Fortran routine MPI_ATTR_PUT, i.e., in Fortran, MPI_COMM_GET_ATTR(MPI_COMM_WORLD, MPI_TAG_UB, val, flag, ierr) will return in val the upper bound for tag value; in C, MPI_Comm_get_attr(MPI_COMM_WORLD, MPI_TAG_UB, &p, &flag) will return in p a pointer to an int containing the upper bound for tag value.
Address-valued predefined attributes, such as MPI_WIN_BASE behave as if they were put by a C call, i.e., in Fortran, MPI_WIN_GET_ATTR(win, MPI_WIN_BASE, val, flag, ierror) will return in val the base address of the window, converted to an integer. In C, MPI_Win_get_attr(win, MPI_WIN_BASE, &p, &flag) will return in p a pointer to the window base, cast to (void *).
Rationale.
The design is consistent with the behavior
specified
for predefined
attributes, and ensures that no information is lost when attributes are
passed from language to language.
Because the language interoperability for
predefined attributes was defined based on MPI_ATTR_PUT,
this definition is kept for compatibility reasons although the
routine itself is now deprecated.
( End of rationale.)
Advice
to implementors.
Implementations should tag attributes either as
(1)
address attributes, (2) as
INTEGER(KIND=MPI_ADDRESS_KIND) attributes or (3) as
INTEGER attributes, according to whether they were set in
(1) C (with MPI_Attr_put or
MPI_ XXX_set_attr), (2) in Fortran with
MPI_ XXX_SET_ATTR or (3) with the deprecated Fortran
routine MPI_ATTR_PUT.
Thus, the right choice can be made when the attribute is retrieved.
( End of advice to implementors.)