This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
Edgar Gabriel wrote:
> well, to contradict my own position from previously, this function was
> part of the MPI-2 specification, and the only interfaces published for
> this function were C, C++ and F90. Not sure what this means for f90
> applications however.
I assume you meant "Not sure what this means for f77 applications".
This is why I didn't attempt a patch - the solution to this was
not immediately obvious to me due to the Fortran 77 compatibility
The functions that have the MPI_Fint casts are C functions, so
at the very least, if MPI_Offset is a 64 bit int, then these functions
should not be casting them to 32-bit ints, otherwise we have
two broken interfaces (F77 and F90) instead of one (F77).
> On 12/20/2010 3:59 PM, N.M. Maclaren wrote:
>> On Dec 20 2010, George Bosilca wrote:
>>> There is a hint for F77 users at the bottom of the page. It suggests
>>> to use INTEGER*MPI_OFFSET_KIND as type for the SIZE. I guess if we
>>> cast it correctly, and the users follow the MPI specification, this
>>> should work.
>> Please tell me you are joking?
>> No, that will NOT work, in general. Firstly, the xxx in INTEGER*xxx was
>> introduced in Fortran IV as a digit string and not a constant, and all
>> of the compilers I know of still do that. Secondly, it is NOT always
>> aligned with the KIND values, and there is no implication in any document
>> I know of that it should be.
>> Nick Maclaren.
>> devel mailing list