On Nov 7, 2013, at 2:13 PM, "Andrus, Brian Contractor" wrote:
> Good to know. Thanks!
(sorry for the delay in replying; I was traveling last week, which always makes
a disaster of my INBOX)
> Seems really like MPI_ABORT should only be used within error traps after MPI
> functions have been st
s)
> Sent: Wednesday, November 06, 2013 11:30 AM
> To: Open MPI Users
> Subject: Re: [OMPI users] proper use of MPI_Abort
>
> I just checked the v1.7 series -- it looks like we have cleaned up this
> message a bit. With your code snipit:
>
> -
> ❯❯❯ mpicc ab
res (jsquyres)
>> Sent: Tuesday, November 05, 2013 5:11 AM
>> To: Open MPI Users
>> Subject: Re: [OMPI users] proper use of MPI_Abort
>>
>> You're correct -- you don't need to call MPI_Finalize after MPI_Abort.
>>
>> Can you cite what version of Open MPI
ent: Tuesday, November 05, 2013 5:11 AM
> To: Open MPI Users
> Subject: Re: [OMPI users] proper use of MPI_Abort
>
> You're correct -- you don't need to call MPI_Finalize after MPI_Abort.
>
> Can you cite what version of Open MPI you are using?
>
>
> On Nov 4, 2013
You're correct -- you don't need to call MPI_Finalize after MPI_Abort.
Can you cite what version of Open MPI you are using?
On Nov 4, 2013, at 9:01 AM, "Andrus, Brian Contractor" wrote:
> All,
>
> I have some sample code that has a syntax message and then an MPI_Abort call
> if the program
All,
I have some sample code that has a syntax message and then an MPI_Abort call if
the program is run without the required parameters.
--snip---
if (!rank) {
i = 1;
while ((i < argc) && strcmp("-input", *argv)) {
i++;
argv++;
