Ok. I think most were fixed after you reported them last year, but a few new
MPI-3 functions were added after that, and they accidentally had "ierr" instead
of "ierror".
On Jun 3, 2014, at 11:47 AM, W Spector wrote:
> Jeff Squyres wrote:
> > Did you find any other places where we accidentall
Jeff Squyres wrote:
> Did you find any other places where we accidentally had ierr instead
of ierror?
I will have to check the trunk and see.
The only place I know of where the Standard wants IERR instead of IERROR
is with the user-defined subroutines for MPI_KEYVAL_CREATE - which is
depreca
I'm sorry it took so long -- I finally fixed this on the trunk and have
scheduled this for the v1.8 branch. There were a small number of functions in
the tkr interface that had ierr instead of ierror (some of the Dist_graph
functions), which were probably added after the fixes were applied a ye
you might try the nightly 1.8.2 build - there were some additional patches to
fix the darned tkr support. I'm afraid getting all the various compilers to
work correctly with it has been a major pain.
On May 15, 2014, at 5:01 PM, W Spector wrote:
> Hi Jeff and the list,
>
> A year ago, we had
Hi Jeff and the list,
A year ago, we had the discussion appended below. I just downloaded
v1.8.1 and the F90 module is still very broken. And once again I am
having to modify my local version. (+1 for open source!) Will it be
fixed in v1.8.2?
Configure is using the "use-mpi-tkr" version
I committed that part; thanks.
On Apr 26, 2013, at 5:51 PM, W Spector wrote:
> Hi Jeff,
>
> To take care of the ierr->ierror conversion, simply do the following:
>
> cd openmpi-1.7.1/ompi/mpi/fortran/use-mpi-tkr/scripts
> ls -1 *.sh | xargs -i -t ex -c ":1,\$s?ierr?ierror?" -c ":wq" {}
>
>
Hi Jeff,
To take care of the ierr->ierror conversion, simply do the following:
cd openmpi-1.7.1/ompi/mpi/fortran/use-mpi-tkr/scripts
ls -1 *.sh | xargs -i -t ex -c ":1,\$s?ierr?ierror?" -c ":wq" {}
Then go up a level to openmpi-1.7.1/ompi/mpi/fortran/use-mpi-tk and use:
cd ..
ls -1 for
On Apr 25, 2013, at 10:52 PM, W Spector wrote:
> I tried building 1.7.1 on my Ubuntu system. The default gfortran is v4.6.3,
> so configure won't enable the mpi_f08 module build. I also tried a three
> week old snapshot of the gfortran 4.9 trunk. This has Tobias's new TYPE(*)
> in it, but n
On Apr 25, 2013, at 9:50 AM, W Spector wrote:
> I just downloaded 1.7.1. The new files in the use-mpi-f08 look great!
>
> However the use-mpi-tkr and use-mpi-ignore-tkr directories don't fare so
> well. Literally all the interfaces are still 'ierr'.
Oy. I probably should have realized that
Jeff,
I tried building 1.7.1 on my Ubuntu system. The default gfortran is
v4.6.3, so configure won't enable the mpi_f08 module build. I also
tried a three week old snapshot of the gfortran 4.9 trunk. This has
Tobias's new TYPE(*) in it, but not his latest !GCC$ attributes
NO_ARG_CHECK stuf
Hi Jeff,
I just downloaded 1.7.1. The new files in the use-mpi-f08 look great!
However the use-mpi-tkr and use-mpi-ignore-tkr directories don't fare so
well. Literally all the interfaces are still 'ierr'.
While I realize that both the F90 mpi module and interface checking,
were optional pr
Can you try v1.7.1?
We did a major Fortran revamp in the 1.7.x series to bring it up to speed with
MPI-3 Fortran stuff (at least mostly). I mention MPI-3 because the name-based
parameter passing stuff wasn't guaranteed until MPI-3. I think 1.7.x should
have gotten all the name-based parameter
Hi,
The MPI Standard specifies to use 'ierror' for the final argument in
most Fortran MPI calls. However the Openmpi f90 module defines it as
being 'ierr'. This messes up those who want to use keyword=value syntax
in their calls.
I just checked the latest 1.6.4 release and it is still brok
13 matches
Mail list logo
