April 2013 - devel - mailman3.cels.anl.gov

Re: [mpich-devel] Question about Fortran MPROBE tests
by Gropp, William D 30 Apr '13

30 Apr '13

Well, that's a bad choice - it means an unnecessary copy in the Fortran wrapper just in case. And it only has(marginal) value in some of the multiple completion cases. I'll update the wrapper generation to support this mistake (particularly for the single completion routines, where the value should *always* be undefined. Bill Sent from my iPad On Apr 30, 2013, at 4:23 PM, "Rajeev Thakur" <thakur(a)mcs.anl.gov> wrote: > For Mprobe, the standard says > > "The call matches the same message that would have been received by a call to MPI_RECV(..., source, tag, comm, status) executed at the same point in the program and returns in status the same value that would have been returned by MPI_RECV." > > For MPI_Recv, it says > > "In general, message-passing calls do not modify the value of the error code field of status variables. This field may be updated only by the functions in Section 3.7.5 which return multiple statuses. The field is updated if and only if such function returns with an error code of MPI_ERR_IN_STATUS." > > Rajeev > > On Apr 30, 2013, at 2:10 PM, William Gropp wrote: > >> I'm getting failures in the Fortran version of the MPROBE tests because the test assumes that STATUS is an INOUT argument, and it sets the ERROR field and then checks that the value is unchanged. I don't see the requirement that the value of the MPI_ERROR field be unchanged. Is this an error in the test or is there another part of the standard of which I've forgotten? >> >> Bill >> >> William Gropp >> Director, Parallel Computing Institute >> Deputy Director for Research >> Institute for Advanced Computing Applications and Technologies >> Thomas M. Siebel Chair in Computer Science >> University of Illinois Urbana-Champaign >> >> >> >> >

1 0

Re: [mpich-devel] Question about Fortran MPROBE tests
by Rajeev Thakur 30 Apr '13

30 Apr '13

For Mprobe, the standard says "The call matches the same message that would have been received by a call to MPI_RECV(..., source, tag, comm, status) executed at the same point in the program and returns in status the same value that would have been returned by MPI_RECV." For MPI_Recv, it says "In general, message-passing calls do not modify the value of the error code field of status variables. This field may be updated only by the functions in Section 3.7.5 which return multiple statuses. The field is updated if and only if such function returns with an error code of MPI_ERR_IN_STATUS." Rajeev On Apr 30, 2013, at 2:10 PM, William Gropp wrote: > I'm getting failures in the Fortran version of the MPROBE tests because the test assumes that STATUS is an INOUT argument, and it sets the ERROR field and then checks that the value is unchanged. I don't see the requirement that the value of the MPI_ERROR field be unchanged. Is this an error in the test or is there another part of the standard of which I've forgotten? > > Bill > > William Gropp > Director, Parallel Computing Institute > Deputy Director for Research > Institute for Advanced Computing Applications and Technologies > Thomas M. Siebel Chair in Computer Science > University of Illinois Urbana-Champaign > > > >

1 0

Re: [mpich-devel] Question about Fortran MPROBE tests
by Pavan Balaji 30 Apr '13

30 Apr '13

Bill, On 04/30/2013 02:10 PM US Central Time, William Gropp wrote: > I'm getting failures in the Fortran version of the MPROBE tests because > the test assumes that STATUS is an INOUT argument, and it sets the ERROR > field and then checks that the value is unchanged. I don't see the > requirement that the value of the MPI_ERROR field be unchanged. Is this > an error in the test or is there another part of the standard of which > I've forgotten? The C bindings say that status is an OUT parameter. The Fortran bindings don't set an INTENT; does that imply an INOUT parameter? If yes, shouldn't that be made consistent with C? AFAICT, the standard doesn't state that the status will be unchanged. If it's an OUT parameter, the input value makes no sense anyway. -- Pavan -- Pavan Balaji http://www.mcs.anl.gov/~balaji

1 0

Re: [mpich-devel] Access to git
by Pavan Balaji 30 Apr '13

30 Apr '13

Bill, The git setup requires your ssh public key to be loaded on the server. Are you using different matching private keys on MCS and your laptop? -- Pavan On 04/30/2013 01:25 PM US Central Time, William Gropp wrote: > I believe that the access setup for git requires something special be > done - I have no trouble using git on my Mac but not having a version > that I can push from on MCS means I have to move corrections back to my > home system. > > Bill > > William Gropp > Director, Parallel Computing Institute > Deputy Director for Research > Institute for Advanced Computing Applications and Technologies > Thomas M. Siebel Chair in Computer Science > University of Illinois Urbana-Champaign > > > > > On Apr 30, 2013, at 1:36 PM, Rajeev Thakur wrote: > >> It worked for me on /tmp on octopus just now. >> >> Rajeev >> >> On Apr 30, 2013, at 11:29 AM, William Gropp wrote: >> >>> I can't checkout mpich when I'm logged into MCS (e.g., from octopus). >>> The git page says to send this email when that happens :) >>> >>> Bill >>> >>> William Gropp >>> Director, Parallel Computing Institute >>> Deputy Director for Research >>> Institute for Advanced Computing Applications and Technologies >>> Thomas M. Siebel Chair in Computer Science >>> University of Illinois Urbana-Champaign >>> >>> >>> >>> >> > -- Pavan Balaji http://www.mcs.anl.gov/~balaji

1 0

Question about Fortran MPROBE tests
by William Gropp 30 Apr '13

30 Apr '13

I'm getting failures in the Fortran version of the MPROBE tests because the test assumes that STATUS is an INOUT argument, and it sets the ERROR field and then checks that the value is unchanged. I don't see the requirement that the value of the MPI_ERROR field be unchanged. Is this an error in the test or is there another part of the standard of which I've forgotten? Bill William Gropp Director, Parallel Computing Institute Deputy Director for Research Institute for Advanced Computing Applications and Technologies Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign

1 0

Re: [mpich-devel] Access to git
by William Gropp 30 Apr '13

30 Apr '13

I believe that the access setup for git requires something special be done - I have no trouble using git on my Mac but not having a version that I can push from on MCS means I have to move corrections back to my home system. Bill William Gropp Director, Parallel Computing Institute Deputy Director for Research Institute for Advanced Computing Applications and Technologies Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign On Apr 30, 2013, at 1:36 PM, Rajeev Thakur wrote: > It worked for me on /tmp on octopus just now. > > Rajeev > > On Apr 30, 2013, at 11:29 AM, William Gropp wrote: > >> I can't checkout mpich when I'm logged into MCS (e.g., from octopus). The git page says to send this email when that happens :) >> >> Bill >> >> William Gropp >> Director, Parallel Computing Institute >> Deputy Director for Research >> Institute for Advanced Computing Applications and Technologies >> Thomas M. Siebel Chair in Computer Science >> University of Illinois Urbana-Champaign >> >> >> >> >

1 0

Re: [mpich-devel] Access to git
by Jeff Hammond 30 Apr '13

30 Apr '13

The latest version of Git is written in C99; it appears that C99 is finally getting its revenge against Bill for refusing to let it into MPICH. <100% trolling - nothing about this message is true> Jeff On Tue, Apr 30, 2013 at 12:36 PM, Rajeev Thakur <thakur(a)mcs.anl.gov> wrote: > It worked for me on /tmp on octopus just now. > > Rajeev > > On Apr 30, 2013, at 11:29 AM, William Gropp wrote: > >> I can't checkout mpich when I'm logged into MCS (e.g., from octopus). The git page says to send this email when that happens :) >> >> Bill >> >> William Gropp >> Director, Parallel Computing Institute >> Deputy Director for Research >> Institute for Advanced Computing Applications and Technologies >> Thomas M. Siebel Chair in Computer Science >> University of Illinois Urbana-Champaign >> >> >> >> > -- Jeff Hammond Argonne Leadership Computing Facility University of Chicago Computation Institute jhammond(a)alcf.anl.gov / (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

1 0

Re: [mpich-devel] Access to git
by Rajeev Thakur 30 Apr '13

30 Apr '13

It worked for me on /tmp on octopus just now. Rajeev On Apr 30, 2013, at 11:29 AM, William Gropp wrote: > I can't checkout mpich when I'm logged into MCS (e.g., from octopus). The git page says to send this email when that happens :) > > Bill > > William Gropp > Director, Parallel Computing Institute > Deputy Director for Research > Institute for Advanced Computing Applications and Technologies > Thomas M. Siebel Chair in Computer Science > University of Illinois Urbana-Champaign > > > >

1 0

Access to git
by William Gropp 30 Apr '13

30 Apr '13

I can't checkout mpich when I'm logged into MCS (e.g., from octopus). The git page says to send this email when that happens :) Bill William Gropp Director, Parallel Computing Institute Deputy Director for Research Institute for Advanced Computing Applications and Technologies Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign

1 0

Fortran errors in nightlies
by William Gropp 30 Apr '13

30 Apr '13

These are probably due to my recent fixes for the MPI_Status alignment issue. They did work on my test system (my Mac). I'll look into them, but it may take a few days. Bill William Gropp Director, Parallel Computing Institute Deputy Director for Research Institute for Advanced Computing Applications and Technologies Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign

1 0