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
Hi,
I have been doing a lot of testing/fixing lately on our code, using
valgrind to find problems. Unfortunately, OpenMPI causes a lot of
'false positives' in our testing due to memory leaks of its own.
It appears that MPI_Init allocates a lot of memory blocks that
MPI_Finalize never bother
Hi,
When running under valgrind, I get warnings from each MPI process at
MPI_Init time. The warnings come from function sec_basic.c at lines 70
and 71 (openmpi v1.8.1):
my_cred.credential = strdup("12345");
my_cred.size = strlen(my_cred.credential)+1; // include
the
t; version on my system. I can see
that the "use-mpi-f08" version is much better.
Walter
On 04/26/2013 03:14 PM, Jeff Squyres (jsquyres) wrote:
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,
Hi,
The mpi.mod file that is created from both the openmpi-1.7.4 and
openmpi-1.8rc1 tarballs does not seem to be generating interface blocks
for the Fortran API - whether the calls use choice buffers or not.
I initially tried the default gfortran on my system - 4.7.2. The
configure commands
On 06/04/2013 03:23 AM, Jeff Squyres (jsquyres) wrote:
On Jun 3, 2013, at 5:06 AM, Paul Kapinos wrote:
It is more or less well-known that MPI_THREAD_MULTIPLE disable the OpenFabric /
InfiniBand networking in Open MPI:
http://www.open-mpi.org/faq/?category=supported-systems#thread-support
htt
Dear OpenMPI group,
The following trivial program hangs on the mpi_barrier call with 1.7.1.
I am using gfortran/gcc 4.6.3 on Ubuntu linux. OpenMPI was built with
--enable-mpi-thread-multiple support and no other options (other than
--prefix).
Are there additional options we should be telli
I needed to use a few MPI_Type calls.
So fixed the few that I needed in the
openmpi-1.7.1/ompi/mpi/fortran/use-mpi-tkr/scripts directory. I didn't
exhaustively go through and verify every interface in the whole MPI library.
Walter
On 04/26/2013 11:53 AM, Jeff Squyres (jsquyres) wrote:
t;
MPI_Type_free: Again, "datatype" instead of "type"
There are more...
Walter
On 04/25/2013 06:50 AM, W Spector wrote:
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 far
ely that we'll be updating the Fortran support in
the 1.6.x series.
On Apr 24, 2013, at 8:52 PM, W Spector
wrote:
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 'ier
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
11 matches
Mail list logo