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.
On 04/08/2013 04:08 PM, Thomas Jahns wrote:
> a colleague of mine has investigated a difficult problem we traced to OpenMPI
> giving incorrectly delivered data on some struct datatypes which use specific
> offsets (on the stack in our case but the problem can be reproduced when using
> specifically chosen slices of an array). Our library is used to aggregate
> several MPI communications in a generic and transparent manner and therefore we
> need to be able to handle any combination of properly aligned offsets and
> component types.
> The attached example program contains the necessary steps to reproduce the problem:
> 1. create the struct types in question
> 2. send/recv the data
> 3. compare to reference (said comparison works on several MPICH2 versions)
our IT service provider has applied the patch to openmpi 1.6.4 and the C
test-case I provided now works but the original code which uses a bigger number
of struct dataypes still fails.
Has anyone already discovered a potential problem with the fix provided in
r28319? I'm asking because developing the C test case is quite some amount of
work and is not easily reproducible with every Fortran compiler because it
depends on the stack layout.
DKRZ GmbH, Department: Application software
Email: Thomas Jahns <jahns_at_[hidden]>