Am 05.02.2009 um 17:39 schrieb Jeff Squyres:
On Feb 4, 2009, at 10:17 AM, Christoph van Wüllen wrote:
I came across OpenMPI because it seems to be the only MPI
implementation
which supports 64-bit integers in FORTRAN, so I had a huge propensity
stepping into this bug.
Since I was the one
On Feb 4, 2009, at 10:17 AM, Christoph van Wüllen wrote:
I came across OpenMPI because it seems to be the only MPI
implementation
which supports 64-bit integers in FORTRAN, so I had a huge propensity
stepping into this bug.
Since I was the one that championed the whole "what if fortran
IN
Hello Mr. Wuellen,
thanks for the bug report!
On Wednesday 04 February 2009 09:21:38 am Christoph van Wüllen wrote:
> there is an error in the above mentioned file, in line 74:
>
> if (MPI_SUCCESS == OMPI_FINT_2_INT(*ierr)) {
> OMPI_ARRAY_INT_2_FINT(coords, OMPI_FINT_2_INT(*maxdims));
Am 04.02.2009 um 16:06 schrieb George Bosilca:
Christoph,
You're absolutely right. In addition to your comment about the
syntactically wrong line of code, even in the case when the fortran
and C integers have the same length, we modify the value pointer by
the fortran IN only argument.
Christoph,
You're absolutely right. In addition to your comment about the
syntactically wrong line of code, even in the case when the fortran
and C integers have the same length, we modify the value pointer by
the fortran IN only argument.
A patch is on the way.
Thanks,
george.
On
dear developers,
there is an error in the above mentioned file, in line 74:
if (MPI_SUCCESS == OMPI_FINT_2_INT(*ierr)) {
OMPI_ARRAY_INT_2_FINT(coords, OMPI_FINT_2_INT(*maxdims));
the OMPI_ARRAY_INT_2_FINT macro uses the second argument with
pre-decrement, such that it must be an lvalu
