i am going to generalize my test case to "forall tests involving datatypes: try to send 4+ GB datatype". that seems more useful than the one-off we have now. jeff ----- Original Message -----

From: "Jim Dinan" <[email protected]> To: [email protected] Sent: Friday, October 18, 2013 2:25:34 PM Subject: Re: [mpich-devel] when is MPICH going to be count-safe?

(Disclaimer: I haven't looked at the branch in question, so please ignore if redundant) It would be good to commit the test case too, if you haven't already added it.

On Tue, Oct 15, 2013 at 4:00 PM, Rob Latham < [email protected] > wrote:

On Mon, Oct 14, 2013 at 09:54:56PM -0500, Rob Latham wrote:

...

good news is that I think everything "important" is happening correctly. It's just that when the status object is updated it's picking up an overflowed integer. status.count is MPI_Count big, so that's not the source of the overflow. will look once more at my mountain of clang -Wshorten-64-to-32 related warnings in the morning.

Jeff found the casts to int and I've added his two patches to my branch in -review. Jeff and I now pass Jeff's testcase.

==rob

-- Rob Latham Mathematics and Computer Science Division Argonne National Lab, IL USA

-- Jeff Hammond Argonne Leadership Computing Facility University of Chicago Computation Institute [email protected] / (630) 252-5381 http://www.linkedin.com/in/jeffhammond https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond ALCF docs: http://www.alcf.anl.gov/user-guides